Skip to main content

Configurator

Working with the configurator using R8C as an example​

R8C has no signatures that allow automatically determining the subfamily, memory sizes, and memory segmentation. Therefore, choosing the correct MCU is the user’s responsibility.

There are many targets, and each target has its own memory map (different memory regions — more details below). For this, we made a configurator so you can add the required MCU yourself.

How to add an R8C MCU to MultiProg using the configurator?​

Open Target Selector, select the R8C family, and click the configurator icon. Configurator R8C

Configurator selector​

info

You can delete and modify only the targets you created (Source->user). System targets (Source->system) can only be copied.

Configurator Selector

Modify - modify fields.

Delete - delete a target.

Add new - add a new target (fields are filled in arbitrarily).

Copy - copy a target.

Configurator window​

Configurator window

Target Name - target name. Must not duplicate an existing name in the database. Does not affect technical parameters. The program will throw an error if you try to create a target with a name that is already taken.

Memory Regions - memory regions.​

Each region has:

  1. Name Region name, displayed in the buffer.
  2. Address (hex) Start address (in hex, i.e. with the 0x prefix).
  3. Size size and units (Bytes, KB, MB).
info

The size must be divisible by 64 with no remainder. For KB/MB, conversion uses 1024. The program will throw an error if you try to set an invalid size.

  1. Cell size memory cell size, default is 0x1 since in 99% of MCUs one address = one byte. But, for example, on DSC MC56F one address corresponds to 2 bytes.
info

Cell size usually does not need to be edited.

Advanced​

These are advanced settings.

  1. Block size block size in bytes.
  2. Sub- block size sub-block size. A block consists of 4 sub-blocks.
  3. Arguments arguments passed when connecting with TGSN. This is custom tuning for the task.
info

For normal R8C operation — an empty Arguments field or MODE 3.
Usually, arguments are used for specific tasks/operating modes; in the case of “open” R8C, arguments are not required.

Example: creating R5F21368S in the configurator​

  1. Select any target, preferably from the 213x series, click Copy.
  2. Rename our new target to R5F21368S.
  3. Open the documentation, find the section with the memory map:

Configurator R5F21368S

  1. We see that the controller has 64 KB of Flash memory. Start: 0x8000.

  2. Internal ROM (data flash) (EEPROM section) is located in the range 0x7000–0x7FFF. Start: 0x7000. Configurator 2 R5F21368S

  3. Calculate the EEPROM size:

(0x7FFF - 0x7000 + 1) / 1024 = 4 KB It comes out to 4 KB (4096 bytes).

  1. Save our configuration, select the target, and work.