11. Quick Start for Renesas RA

11.1. Supported Environments

Operating System

Windows: Windows 10 / Windows 11

Linux: Ubuntu 22.04 / Ubuntu 24.04

macOS: macOS 14 Sonoma (Apple silicon) / macOS 15 Sequoia (Apple silicon)

VS Code version

1.102.0 (minimum)

VS Code can be downloaded and installed from this page https://code.visualstudio.com/.

11.2. Installation

Please choose your operating system for operating system dependent installation steps.

Renesas Platform, provides a complete installation wizard to start developing for Renesas RA Family. To set up your environment:

  1. Open VS Code.

  2. Navigate to the “Renesas” tab in VS Code. Then, click “Renesas Quick Install” in the “Environment” view.

    _images/renesas-quick-install.png

  3. Click the “Install” button for the “Renesas RA” device family. The Renesas Platform will now check the dependencies required by the Renesas RA Device Family. The Renesas Platform extension will check the local environment and CMake, Ninja Build, Python 3.10, ARM GNU Toolchain, SEGGER J-Link, Support Files for RA Family and the Renesas RA Smart Configurator installations, then create an installation plan for them if necessary.

    _images/ra-install.png

  4. The installation plan automatically includes all the prerequisites. Moreover, you can also select additional tools or toolchain versions by checking the “Build Tools”, “Debug Tools”, “Device Support” and the “Smart Configurators” tabs.

    _images/ra-install-additional.png

  5. When your selection is ready, click the “Start Installations” button. The download and installation process will start automatically.

    _images/ra-start-installation.png

Most of the installations will be performed automatically, some installations may require manual interaction.

  • During the SEGGER J-Link installation, the setup wizard will appear for manual installation, please follow the steps to complete the SEGGER J-Link installation.

    _images/ra-installation-attention.png

Installing Additional Emulator Drivers

For some debug emulators, you may need to download and install additional USB drivers for establishing a connection with the emulators and devices.

Using Renesas E2/E2Lite Emulators:

If you are using Renesas Emulators, please install the latest drivers before starting your debug session. Use the following links to download the drivers suitable for your operating system and device:

Renesas Platform, provides a complete installation wizard to start developing for Renesas RA Family. To set up your environment:

  1. Open VS Code.

  2. Navigate to the “Renesas” tab in VS Code. Then, click “Renesas Quick Install” in the “Environment” view.

    _images/renesas-quick-install.png

  3. Click the “Install” button for the “Renesas RA” device family. The Renesas Platform will now check the dependencies required by the Renesas RA Device Family. The Renesas Platform extension will check the local environment and CMake, Ninja Build, Python 3.10, ARM GNU Toolchain, SEGGER J-Link, Support Files for RA Family and the Renesas RA Smart Configurator installations, then create an installation plan for them if necessary.

    _images/ra-install.png

  4. The installation plan automatically includes all the prerequisites. Moreover, you can also select additional tools or toolchain versions by checking the “Build Tools”, “Debug Tools”, “Device Support” and the “Smart Configurators” tabs.

    _images/ra-install-additional.png

  5. When your selection is ready, click the “Start Installations” button. The download and installation process will start automatically.

    _images/ra-start-installation.png

Most of the installations will be performed automatically, some installations may require manual interaction.

  • During the “Python 3.10” and the “Renesas RA Smart Configurator” installations, the terminal wizard will appear for manual interaction. The terminal will show the execution plan and ask for confirmation before continuing. During the installation, it may require administrative rights to execute the installation, thus a password could be needed during the installation. Please make sure that the current user has “sudo” permissions and enter the password.

    _images/ra-installation-terminal-attention.png

Installing Additional Emulator Drivers

For some debug emulators, you may need to download and install additional USB drivers for establishing a connection with the emulators and devices.

Using Renesas E2/E2Lite Emulators:

If you are using Renesas Emulators, please install the latest drivers before starting your debug session. Use the following links to download the drivers suitable for your operating system and device:

Renesas Platform, provides a complete installation wizard to start developing for Renesas RA Family. To set up your environment:

  1. Open VS Code.

  2. Navigate to the “Renesas” tab in VS Code. Then, click “Renesas Quick Install” in the “Environment” view.

    _images/renesas-quick-install.png

  3. Click the “Install” button for the “Renesas RA” device family. The Renesas Platform will now check the dependencies required by the Renesas RA Device Family. The Renesas Platform extension will check the local environment and CMake, Ninja Build, Python 3.10, ARM GNU Toolchain, SEGGER J-Link, Support Files for RA Family and the Renesas RA Smart Configurator installations, then create an installation plan for them if necessary.

    _images/ra-install.png

  4. The installation plan automatically includes all the prerequisites. Moreover, you can also select additional tools or toolchain versions by checking the “Build Tools”, “Debug Tools”, “Device Support” and the “Smart Configurators” tabs.

    _images/ra-install-additional.png

  5. When your selection is ready, click the “Start Installations” button. The download and installation process will start automatically.

    _images/ra-start-installation.png

Most of the installations will be performed automatically, some installations may require manual interaction.

  • During the “Python 3.10” and the “Renesas RA Smart Configurator” installations, the terminal wizard will appear for manual interaction. The terminal will show the execution plan and ask for confirmation before continuing. During the installation, it may require administrative rights to execute the installation, thus a password could be needed during the installation. Please make sure that the current user has “sudo” permissions and enter the password.

    _images/ra-installation-terminal-attention.png

Installing Additional Emulator Drivers

For some debug emulators, you may need to download and install additional USB drivers for establishing a connection with the emulators and devices.

Using Renesas E2/E2Lite Emulators:

If you are using Renesas Emulators, please install the latest drivers before starting your debug session. Use the following links to download the drivers suitable for your operating system and device:

To utilise the Renesas extensions on macOS, it’s necessary to install:

  • Homebrew

  • XZ Archive Utilities

First, install Homebrew (brew), which is an open-source software package management system that manages the installation of software for macOS. For installation and more information about Homebrew, please refer to https://brew.sh/.

After installing the Homebrew, install the “XZ Archive Utilities” by using brew install xz command.

$ brew install xz

Renesas Platform, provides a complete installation wizard to start developing for Renesas RA Family. To set up your environment:

  1. Open VS Code.

  2. Navigate to the “Renesas” tab in VS Code. Then, click “Renesas Quick Install” in the “Environment” view.

    _images/renesas-quick-install.png

  3. Click the “Install” button for the “Renesas RA” device family. The Renesas Platform will now check the dependencies required by the Renesas RA Device Family. The Renesas Platform extension will check the local environment and CMake, Ninja Build, Python 3.10, ARM GNU Toolchain, SEGGER J-Link, Support Files for RA Family and the Renesas RA Smart Configurator installations, then create an installation plan for them if necessary.

    _images/ra-install.png

  4. The installation plan automatically includes all the prerequisites. Moreover, you can also select additional tools or toolchain versions by checking the “Build Tools”, “Debug Tools”, “Device Support” and the “Smart Configurators” tabs.

    _images/ra-install-additional.png

  5. When your selection is ready, click the “Start Installations” button. The download and installation process will start automatically.

    _images/ra-start-installation.png

Most of the installations will be performed automatically, some installations may require manual interaction.

  • During the “Python 3.10” and the “Renesas RA Smart Configurator” installations, the terminal wizard will appear for manual interaction. The terminal will show the execution plan and ask for confirmation before continuing. During the installation, it may require administrative rights to execute the installation, thus a password could be needed during the installation. Please make sure that the current user has “sudo” permissions and enter the password.

    _images/ra-installation-terminal-attention.png

11.3. Creating a Project

For RA device family projects, it is recommended to use RA Smart Configurator to create a project for VS Code. Smart Configurator can be accessed via the “Create Project” view in the “Renesas” tab. Please use the following instructions to create and build a project for RA device family.

  1. Navigate to “Renesas” and click [Create Renesas RA project] from the commands.

    _images/ra-create-project.png

  2. VSCode will show installed [RA Smart Configurator] list, select a [Smart Configurator] from the list.

    _images/ra-sc-pick.png

  3. Select a [Folder] to create the project.

    _images/ra-folder-pick.png

  4. Keep the [Project name] and click [Next].

    _images/ra-sc-step1.png

  5. Configure your board, device type and preferred toolchain from the toolchains list, then click [Next].

    _images/ra-sc-step2.png

  6. Choose the “Smart Bundle” configuration and continue by clicking [Next] (Skip choosing the Smart Bundle selection for the sample project).

    _images/ra-sc-step3.png

  7. Choose the “RTOS” configuration and continue by clicking [Next] (Continue with “No RTOS” for the sample project).

    _images/ra-sc-step4.png

  8. Choose one of the project templates then click [Finish] to complete the project creation steps.

    _images/ra-sc-step5.png

  9. Close [RA Smart Configurator] after generation of the project files completed.

    _images/ra-sc-step6.png

11.4. Building the Project

For building a project, which has been created with RA Smart Configurator, please follow the steps below:

  1. When the project is opened for the first time, CMake configure and the CMake Kit selection operations must be performed. In order to do these operations, open the “Command Palette” in VSCode and select “CMake: Configure” from the commands.

    _images/ra-build-step1.png

  2. Then, a kit selection menu will be shown. Select “Renesas Platform: Arm GNU Toolchain …” from the menu if the project is generated for GCC toolchain, or, select “Renesas Platform: Arm LLVM Toolchain …” from the menu if the project is generated for LLVM toolchain. It is important to use the “Renesas Platform: …” kits since they contain Renesas-specific configuration parameters for Renesas projects.

    _images/ra-build-step2.png

    Note

    Missing the selection of the CMake Kit or wrong selection can cause build problems. If you missed the CMake Kit selection or selected a wrong kit, you can re-select the CMake Kit by running “CMake: Select a kit” command from the VSCode Command Palette.

    _images/rasc-cmake-select-a-kit.png

  3. Now, go to and click “Terminal” => “Run Build Task” from the menu.

    _images/ra-build-step3.png

  4. Build options will be shown, select the “Build Project” option.

    _images/ra-build-step4.png

    Note

    Alternatively, you can directly use the “Build” button to start the build operation via the VS Code toolbar.

    _images/ra-build-step5.png

  5. After the build operation, you will see the progress completed successfully. By default, build output (<project name>.elf) can be found in “build/<Build Type>/CMakeFiles/<project name>.elf.dir/” folder.

    _images/ra-build-step6.png

11.5. Editing/Re-configuring the Project

To edit a project, which has been created with RA Smart Configurator, please follow the steps below:

  1. Right click the “configuration.xml” file at the project root, and select the “Open with RA Smart Configurator” option in the context menu.

    _images/ra-edit-step1.png

  2. VSCode will show installed [RA Smart Configurator] list, select a [Smart Configurator] from the list to open the project.

    _images/ra-edit-step2.png

  3. VSCode will open the project in the selected RA Smart Configurator, now you can edit your project configuration in the RA Smart Configurator. Once the changes completed, click the “Generate Project Content” button to re-generate the project content.

    _images/ra-edit-step3.png

TIP: For more information about RA Smart Configurator, click here to visit RA Smart Configurator page.

11.6. Debugging the Project

A debug session can be started by selecting the created configuration and clicking the [Start Debugging] button in the [Run and Debug] tab, or pressing [F5] from the keyboard.

_images/vscode-debug-start5.png

When VS Code starts the debug session, common debug control flow functions like resume, suspend, step into, step over, step out, restart, terminate debug session can be performed via the debug flow control buttons. Also, the [Debug Console] view will contain useful messages during the debug session.

_images/vscode-debug-start6.png

During the debug session, details about the local variables, device registers, call stack, watched variables, states of the peripherals can be accessed at the primary sidebar of VS Code in the [Run and Debug] tab.

_images/vscode-debug-start7.png

11.7. GDB Server launch parameters for RA devices

Reference for common parameters: All common server parameters, including default settings and options applicable to Renesas device families, are documented in the GDB Server Parameters section. The specific parameters of the RA devices are described below.

11.7.1. Connection Settings

11.7.1.2. Clock

Option

Details

-uClockSrc=
Description: Specify the Main Clock Source.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: Internal, 1: External
Example: "serverParameters": { "-uClockSrc=": 0 }

-uInputClock=
Description: Specify External frequency in MHz when using External Clock source.
Default Values: None
Emulator: E2, E2Lite
Available Values: Between 0.001 to 99.999
Example: "serverParameters": { "-uInputClock=": 16.00 }

-uAllowClockSourceInternal=
Description: Specify whether or not to allow manipulation of the main clock source by debugger when internal flash memory is rewritten.
Default Values: 1
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uAllowClockSourceInternal=": 0 }

-uCPUFrequency=
Description: Specify the operating frequency (ICLK) in Hz. It is used to calculate the timestamp of SWO trace.
Default Values: None
Emulator: E2, E2Lite
Available Values: The frequency in Hz in range 1000 - 999999000
Example: "serverParameters": { "-uCPUFrequency=": 120000000 }

11.7.1.3. Emulator

Option

Details

-sn=
Description: Specify the emulator serial number to be connected.
Default Values: Auto (Emulator will be selected automatically.)
Emulator: E2, E2Lite
Available Values: Emulator information with format: <emulator type>:<serial number>
Example: "serverParameters": { "-sn=": "e2:_9es002310c" }

11.7.1.4. Interface

Option

Details

-uInteface=
Description: Specify the connection type to be used by the emulator when communicating with the CPU on target system.
Default Values: JTAG
Emulator: E2, E2Lite, J-Link
Available Values: SWD: Type SWD, JTAG: Type JTAG
Example: "serverParameters": { "-uInteface=": "SWD" }

-uIfSpeed=
Description: Specify the interface speed in kHz.
Default Values: auto
Emulator: E2, E2Lite, J-Link
Available Values: auto (Selects the appropriate JTAG speed handled by the emulator), adaptive (If the target provides the RTCK signal, select the adaptive clocking function to synchronize the clock to the processor clock outside the core), From 1 to 100000 (Specify value for interface speed in kHz)
Example: "serverParameters": { "-uIfSpeed=": 4000 }
Note: “adaptive” option is just available for J-Link

11.7.1.5. Power

Option

Details

-w
Description: Specify the power source.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0, 1, 2
Example: "serverParameters": { "-w": 1 }
Note: Value 2 is just supported for E2 emulator.

-z
Description: Specify the power voltage supplied to the target board.
Default Values: 33
Emulator: E2, E2Lite
Available Values: 0: 3.3 V, 1: 5.0 V, From 18 to 50: From 1.8 V to 5.0 V
Example: "serverParameters": { "-z": 0 }: using for 3.3 V, "serverParameters": { "-z": 1 }: using for 5.0 V, "serverParameters": { "-z": 18 }: using for 1.8 V
Note: E2Lite emulator is just supported 3.3 V. Just E2 emulator allows to specify a arbitrary value from 1.8 V to 5.0 V

11.7.1.6. JTAG Scan Chain

Option

Details

-uscIrPre=
Description: Specify the number of IR-bits of all devices which are closer to TDO than the one we want to communicate with.
Default Values: 0
Emulator: J-Link
Available Values: Valid integer number of IR-bits
Example: "serverParameters": { "-uscIrPre=": 0 }

-uscDrPre=
Description: Specify the number of devices which are closer to TDO than the one we want to communicate with.
Default Values: 0
Emulator: J-Link
Available Values: Valid integer number
Example: "serverParameters": { "-uscDrPre=": 0 }

11.7.1.7. Connection

Option

Details

-uResetCon=
Description: Specify whether to hold reset during the connection progress.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uResetCon=": 1 }

-uResetBeginConnection=
Description: Specify whether the CPU should be reset at the beginning of connection.
Default Values: 1
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uResetBeginConnection=": 1 }

-uNoReset=
Description: Specify whether the CPU should not be reset at the end of connection.
Default Values: 1
Emulator: E2, E2Lite, J-Link
Available Values: 0: Reset, 1: No Reset
Example: "serverParameters": { "-uNoReset=": 1 }

-uIdCodeBytes=
Description: Specify the ID code to unlock the device (if one has been set previously to protect connection).
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: 32 hex digits
Example: "serverParameters": { "-uIdCodeBytes=": "FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF" }

-uLowPower=
Description: Specify if the program uses low power consumption mode or not.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uLowPower=": 0 }

-uInitRegisters=
Description: Specify if registers should be initialized on connection.
Default Values: 0
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uInitRegisters=": 0 }

-uResetPreRun=
Description: Specify if an additional reset should be applied before the downloaded module is run.
Default Values: 0
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uResetPreRun=": 0 }

-uResetBefDownload=
Description: Specify if an additional reset should be applied before the module is downloaded.
Default Values: 0
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uResetBefDownload=": 0 }

-uSetArmModeAfterDownload=
Description: Specify if CPSR(5 bit) should be set to ARM mode after the module is downloaded.
Default Values: 0
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uSetArmModeAfterDownload=": 0 }

-uReleaseCM3=
Description: Specify whether prevent run away at launching a debug session for Cortex-M3 core.
Default Values: 1
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uReleaseCM3=": 0 }

-uSecureVectorAddress=
Description: Specify the Secure Vector address.
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: The valid hex address.
Example: "serverParameters": { "-uSecureVectorAddress=": "0x10010110" }

-uNonSecureVectorAddress=
Description: Specify the Non Secure Vector address.
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: The valid hex address.
Example: "serverParameters": { "-uNonSecureVectorAddress=": "0x10010110" }

-uHotPlug=
Description: Specify if connecting to an already running target system.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: Disabled, 1: Enabled
Example: "serverParameters": { "-uHotPlug=": 1 }

-uDisconnectionMode=
Description: Specify the disconnection mode to control the target state after disconnecting.
Default Values: 2
Emulator: E2, E2Lite, J-Link
Available Values: 0: No change mode, 1: Stop mode, 2: Continue mode
Example: "serverParameters": { "-uDisconnectionMode=": 1 }

11.7.1.8. SWV

Option

Details

-uSWOcoreClock=
Description: Specify the core clock speed in Hz.
Default Values: 0
Emulator: J-Link
Available Values: Valid frequency value in Hz
Example: With 8 MHz: "serverParameters": { "-uSWOcoreClock=": 8000000 }

-uSWOclockDiv=
Description: Specify SWO frequency by division value. The SWO frequency is decided by dividing Clock Src of ICLK with this value.
Default Values: 4
Emulator: E2
Available Values: 0 (1), 1 (2), 2 (4), 3 (8), 4 (16), 5 (32), 6 (64), 7 (128), 8 (256), 9 (512), 10 (1024)
Example: Set the SWO frequency to 256: "serverParameters": { "-uSWOclockDiv=": 8 }
Note: SWO will be supported only for type SWD

11.7.1.9. TrustZone

Option

Details

-uEnableSciBoot=
Description: Specify whether the boundaries of memory regions need to be set to separate each memory region when a debugging connection is initiated.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: Disabled, 1: Enabled
Example: "serverParameters": { "-uEnableSciBoot=": 1 }

-uMemRegion=
Description: Specify the memory region.
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: The values use the format: <start address>:<size>:<memory type>:<memory security attribute>
Example: "serverParameters": { "-uMemRegion=": "0x20000000:0x800:RAM:s" }

-uTz=
Description: Specify the debugging type of TrustZone.
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: SSD: Secure Software Development, NSECSD: Non Secure Software Development
Example: "serverParameters": { "-uTz=": "NSECSD" }

-uAuthLevel=
Description: Specify the authentication level.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0 (AL0: Ignores the key and connect without authentication), 1 (AL1: Authenticate device with key to AL1), 3 (AL2: Authenticate device with key to AL2), 255 (ALERASE: Initialize device back to AL2)
Example: "serverParameters": { "-uAuthLevel=": 3 }
Note: Use this parameter only with TrustZone devices that support Authentication Level

-uAuthKey=
Description: Specify the Authentication Key.
Default Values: None
Emulator: E2, E2Lite, J-Link
Available Values: Key for Authentication
Example: "serverParameters": { "-uAuthKey=": "ACD6B31BF68FE9AE07AEF6B3C3870730" }
Note: Use this parameter only with TrustZone devices that support Authentication Level

Note

The set of values uses the format: <start address>:<size>:<memory type>:<memory security attribute>

Memory type: - FLASH - DATA_FLASH - RAM - FLASH_NS - DATA_FLASH_NS - RAM_NS - Other types are accepted.

Memory security attribute:

Argument

Actual

n

Non-Secure

c

Non-Secure Callable

e

Exempted

s

Secure

11.7.1.10. Start/Stop Function Setting

Option

Details

-uhookEnableStart=
Description: Specify if a function should be executed before running user program.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uhookEnableStart=": 0 }

-uhookStartFunc=
Description: Specify the address of the start function.
Default Values: 0
Emulator: E2, E2Lite
Available Values: Any valid hex address.
Example: "serverParameters": { "-uhookStartFunc=": "&R_BSP_ChangeToUserMode" }
Note: This parameter is just sent when allow to execute function before running user program

-uhookEnableStop=
Description: Specify if a function should be executed after stopping user program.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uhookEnableStop=": 0 }

-uhookStopFunc=
Description: Specify the address of the stop function.
Default Values: None
Emulator: E2, E2Lite
Available Values: Any valid hex address.
Example: "serverParameters": { "-uhookStopFunc=": "&R_BSP_InterruptRead" }
Note: This parameter is just sent when allow to execute function after stopping user program

-uhookWorkRamAddr=
Description: Specify the first address of the working RAM area for start/stop function.
Default Values: 0
Emulator: E2, E2Lite
Available Values: The address needs to be in internal RAM area and it must be divisible by 0x1000.
Example: "serverParameters": { "-uhookWorkRamAddr=": "0x20001000" }

11.7.2. Debug Tool Settings

11.7.2.1. Break

Option

Details

-uFlashBp=
Description: Specify whether to use software breakpoints to flash memory or not.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uFlashBp=": 0 }
Note: This parameter does not need to be specified if -uProgReWriteIRom or -uProgReWriteDFlash is sent with value 1.

-uSimulation=
Description: Specify if Instruction Set simulation will be used or not.
Default Values: 0
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uSimulation=": 0 }
Note: This parameter does not need to be specified if -uProgReWriteIRom or -uProgReWriteDFlash is sent with value 1.

11.7.2.2. Flash

Option

Details

-ueraseRomOnDownload=
Description: Specify whether or not to erase the flash ROM (program ROM) before a download.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-ueraseRomOnDownload=": 0 }

-ueraseDataRomOnDownload=
Description: Specify whether or not to erase the data flash ROM before a download.
Default Values: 0
Emulator: E2, E2Lite, J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-ueraseDataRomOnDownload=": 0 }

-ucfiFlashWorkStart=
Description: Specify the start address of the Working RAM area which is used by JLink during flash programming.
Default Values: 0
Emulator: J-Link
Available Values: Valid address
Example: "serverParameters": { "-ucfiFlashWorkStart=": "0x20001000" }
Note: Start address and end address of Working RAM area have to be set together and start address have to be smaller than end address.

-ucfiFlashWorkEnd=
Description: Specify the end address of the Working RAM area which is used by JLink during flash programming.
Default Values: None
Emulator: J-Link
Available Values: Valid address
Example: "serverParameters": { "-ucfiFlashWorkEnd=": "0x20004000" }
Note: Start address and end address of Working RAM area have to be set together and end address have to be bigger than start address

-ucfiFlashStart=
Description: Specify the start address of CFI Flash Area.
Default Values: 0
Emulator: J-Link
Available Values: Any valid hex address.
Example: "serverParameters": { "-ucfiFlashStart=": "&DebugMon_Handler" }
Note: Start address and end address of CFI flash have to be set together and start address have to be smaller than end address.
The CFI flash address will not be set in Renesas GDB server if Work RAM address is not set before.

-ucfiFlashEnd=
Description: Specify the end address of CFI Flash Area.
Default Values: 0
Emulator: J-Link
Available Values: Any valid hex address.
Example: "serverParameters": { "-ucfiFlashEnd=": "&PendSV_Handler" }
Note: Start address and end address of CFI flash have to be set together and end address have to be bigger than start address. The CFI flash address will not be set in Renesas GDB server if Work RAM address is not set before.

-uExcludeFlashCacheRange=
Description: Specify whether enable and exclude the Flash Cache for a address range.
Default Values: If this parameter is not sent, this feature will be disabled.
Emulator: J-Link
Available Values: Set of address value with below formats: <Start address>,<End address> or <Start address>-<End address>
Example: "serverParameters": { "-uExcludeFlashCacheRange=": "0x10000000,0x100FFFFF" } or "serverParameters": { "-uExcludeFlashCacheRange=": "0x10000000-0x100FFFFF" }

-uflashMemoryType=
Description: Specify the Flash Memory type.
Default Values: None
Emulator: J-Link
Available Values: SerialFlash, HyperFlash, or OctaFlash
Example: "serverParameters": { "-uflashMemoryType=": "SerialFlash" }

-uflashBusType=
Description: Specify the Flash Bus type.
Default Values: None
Emulator: J-Link
Available Values: SPIBSC, HyperBus, or OctaBus
Example: "serverParameters": { "-uflashBusType=": "SPIBSC" }

11.7.2.3. Trace

Option

Details

-uTraceMTB=
Description: Specify whether or not to use MTB trace.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uTraceMTB=": 0 }

-uTraceSizeMTB=
Description: Specify the size of MTB trace (byte).
Default Values: 0
Emulator: E2, E2Lite
Available Values: Size in byte: 256, 512, 1024, 2048, 4096, 8192, 16384, 32768
Example: "serverParameters": { "-uTraceSizeMTB=": 1024 }

-uTraceCache=
Description: Specify the start address and size for Trace cache.
Default Values: None
Emulator: J-Link
Available Values: <start address>|<size>
Example: "serverParameters": { "-uTraceCache=": "0x00000000|0x10000" }

11.7.2.4. System

Option

Details

-uProgReWriteIRom=
Description: Specify whether or not the program being debugged rewrites the internal program ROM.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uProgReWriteIRom=": 0 }

-uProgReWriteDFlash=
Description: Specify whether or not to debug a program that involves rewriting the internal data flash.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uProgReWriteDFlash=": 0 }

-uAllowCachingFlash=
Description: Specify whether the flash contents are cached by J-Link or not.
Default Values: 0
Emulator: J-Link
Available Values: 0: Yes, 1: No
Example: "serverParameters": { "-uAllowCachingFlash=": 0 }
Note: "-uAllowCachingFlash=": 0: Enable caching for the flash contents, "-uAllowCachingFlash=": 1: Disable caching for the flash contents

11.7.2.5. Time Measurement

Option

Details

-uCECycle=
Description: For Renesas RZ targets, this will set the value for bit[3] of the PMCR register to 0.
Default Values: 1
Emulator: J-Link
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uCECycle=": 1 }

-uDWTEnable=
Description: The time is measured by the cycle count feature of the device.
Default Values: 0
Emulator: E2, E2Lite
Available Values: 0: No, 1: Yes
Example: "serverParameters": { "-uDWTEnable=": 1 }

11.7.2.6. Reset Behaviour

Option

Details

-uResetBehavior=
Description: Specify the behaviour for the reset command.
Default Values: Reset
Emulator: J-Link
Available Values: Reset, ChangePC
Example: "serverParameters": { "-uResetBehavior=": "Reset" }

-uPcOnReset=
Description: Specify the value which is set to PC.
Default Values: None
Emulator: J-Link
Available Values: Any valid address or symbol
Example: "serverParameters": { "-uPcOnReset=": "&main" }
Note: If PC value is not specified, it will be set to the entry point value.

-uSetCpsrOnReset=
Description: Specify the value which is set to CPSR.
Default Values: None
Emulator: J-Link
Available Values: Any valid address
Example: "serverParameters": { "-uSetCpsrOnReset=": 0x1da }
Note: If CPSR value is not specified, it will keep the original value.