Affected device families:Synergy RZ RX RL RE RA

When debugging RZ, RA, RE, Synergy, RX, or RL78 and when the option "RTOS integration in debug view" is enabled, the debug connection may be disconnected when a thread is deleted while debugging. Please don’t enable the option "RTOS integration in debug view".

Affected device families:RA

For RA8x2 multicore debugging using J-Link, if Trace View for the CPU1 debug session is enabled before CPU1 is activated by CPU0, reading registers will return garbage data. As a consequence, the program counter (PC) will be located at an incorrect address as well.

Affected device families:RA

It is not possible to modify the output format on an ARM LLVM project.

Affected device families:RA

When using ETM trace with RA8 multicore devices and E2 emulator/E2 emulator Lite, depending on the number of branches and the optimization level when compiling the program, the trace data may take few minutes to return. While waiting for the trace data to return, all debug related operations may become unresponsive and time out.

To workaround this, please increase the command timeout from Window > Preferences > C/C++ > Debug > GDB > Command timeout (ms), as well as the remote timeout by entering "set remotetimeout 90" for example in the Debugger Console after connection is established.

Affected device families:Synergy RZ RX RA DA

When a project contrains identically named static functions the Stack Analysis view does not distinguish between them. This can be seen with the GCC toolchain.

Affected device families:Synergy RA

When the content of the trace data is changed, the user is asked to refresh the updated data. After the update, the trace data editor is closed. The user needs to open the editor again to see the updated trace data.

Affected device families:RZ RA

In the Pin function page, a redundant "*" character may be displayed in the "Input/Output" section of the GPIO pin configuration panel after a DTSi configuration file is imported.

Affected device families:RZ RA

In the case where a solution pin setting is overwritten in downstream project, and if the user modifies the same pin again in a further downstream project, the pin assignment may not be generated into pin_data.c

To avoid this issue, please do not override a solution pin setting more than 1 time.

Affected device families:RZ RA

The lock function of the Pins page may not work correctly if the locked pin assignment is changed manually from the pin number page or FSP Visualization view.

Affected device families:RX RL RH RE RA

Debug configuration for E2 or E2LITE emulator will have the selection of serial No. of the emulator and it can be selected from the list of emulators which are connected to the PC. But this feature will work only on Windows. In case of Linux, please connect only 1 emulator to the PC to use the emulator with e2 studio.

Affected device families:RA

When debugging an RA TrustZone program using E2/E2 emulator Lite, after entering the non-secure reset handler from the secure program, delays occur during each break and suspension, or when step operations are executed. To workaround the slowness, please add the GDB command "set arm unwind-secure-frames off" to "Debug Configurations > Startup > Initialization Commands".

Affected device families:RA

When debugging an RA device using E2/E2 emulator Lite, enabling DWT for time measurement and SWO trace through Live Trace Console at the same time will result in inaccurate run-break time measurement. The time measurement type may change from DWT to System Time as well in the subsequent run-break. Please refrain from using DWT for time measurement when SWO trace is enabled.

Affected device families:RA

When debugging the ARM device which has multiple cores with one debug session, if a breakpoint is set before all cores are activated, the subsequent execution after the breakpoint is hit may not work and debugging may need to be disconnected. Please set the breakpoint at the address where all cores have been activated.

Affected device families:RA

For RA multicore debugging with J-Link, there is a limitation where SWO trace will only be enabled for CPU0.

Affected device families:RA

When debugging multiple debug session for one J-Link-OB-RA4M2, connection to the device will be failed if the other J-Link connection is active at the same time.

Affected device families:RA

When debugging multicore devices with E2/E2LITE emulator, 'Restart' button on the toolbar will be disabled.

Affected device families:RA

When the "RTOS Integration in Debug View" feature is enabled, the values of registers R4R12 may be displayed incorrectly for RTOS threads.

Affected device families:RA

The Debug button of the CMake Tools is not starting the debug session the workaround is to use the main toolbar button instead

Affected device families:RA

The feature "RTOS Integration in Debug View" will not work with TrustZone. If the project is created with TrustZone enabled, please set the option "RTOS Integration in Debug View" to No.

Affected device families:RA

When debugging a program with multiple threads, be careful not to switch to a different stack frame of the main thread in the [Debug] view after hitting a breakpoint. Doing this might cause the program to stop unexpectedly.

Affected device families:RA

The feature for creating an Application to use an FSP Library currently does not support ARM TrustZone (and hence no Smart Bundle is created).

Affected device families:RA

When using RA6M4 with J-Link, data access events with values do not seem to work for some cases.

The variable is allocated to an odd address. When the variable is allocated to odd address, the event with data doesn’t hit with the specified value.

When the access size is WORD, the event with data doesn’t hit with the specified value.

Affected device families:RA

When debugging with J-Link ARM at NSECSD state, data flash can’t be erased and first byte of data flash can’t be read.

Affected device families:RA

J-Link Compact will not be displayed in the list of "J-Link Serial" on the debug configuration. Please use it as 'Auto' for the J-Link Compact.

Affected device families:RA

When installing the platform installer for RA on Windows you may experience issues with GCC toolchain compilation if e2 studio is installed in a long path. Examples problems include not being able to find system include header files.

The workaround for this issue is to install e2 studio in shorter directory structure.

e.g.

c:\users\username\appdata\local\programs\renesas\e2_studio\toolchains\gcc_arm\arm-gnu-toolchain-12.2.mpacbti-rel1-mingw-w64-i686-arm-none-eabi

to

c:\renesas\e2_studio\toolchains\gcc_arm\arm-gnu-toolchain-12.2.mpacbti-rel1-mingw-w64-i686-arm-none-eabi

Affected device families:RA

When Start/Stop function is specified for RA devices with E2/E2 Lite emulator debugging, the stack frame displayed in Debug View doesn’t show the correct information.

Affected device families:RA

When upgrading an existing FSP project and upgrading during import to a new FSP version the clock settings are reset to default.

This can then cause issues with the clock setup and cause project build issues following this.

When importing the project if the correct FSP version is present this does not occur.

Affected device families:RA

The Live Trace Console view can only use with a single debug session.

If you are debugging with 2 sessions, the first session is automatically selected by the Live Trace Console view.

Affected device families:RA

When performing multicore debugging with RA8x2 using Segger J-Link, while the secondary core (CPU1 by default) is inactive, putting the primary core (CPU0 by default) into reset will potentially cause unexpected disconnection.

Affected device families:RA

When using Live Trace Console view, the acquisition of the trace may not be started, if the setting of ITM Trace Setting is changed. In this case, please disable the Live Trace Console and re-enable it.

Affected device families:RA

When using E2/E2LITE emulator for RA multicore devices, the feature "RTOS integration in debug view" will not work. For the environment, please use the option "RTOS integration in debug view" as 'No'.

Affected device families:RA

For Linux environment with E2/E2LITE emulator, the version number of shared object will not be displayed in console while connection.

Affected device families:RA

The register value for msplim and psplim will be displayed as 0 in Registers View, when using Cortex-M devices which support TrustZone via E2/E2LITE emulator.

Please refer to the value value of msplim_s/msplim_ns or psplim_s/psplim_ns insterd.

Affected device families:RA

Currently, E2/E2LITE emulator supports to download the external flash on Renesas EK boards for RA8 devices.

But if the target device is multicore device of RA8, the download will fail if the flash library file is not specified.

In this case, please add the board name such as EK-RA8M2 as the additional argument in Debug Configurations at Additional GDB Server Arguments.

Example:

-uExtFlashBoardName= EK-RA8M2

Affected device families:RA

When using the "RTOS Integration in Debug view" feature with TrustZone projects, the stack frame is displayed incorrectly.

Affected device families:RA

When using ETM trace with RA8 multicore devices and E2 emulator/E2 emulator Lite, depending on the number of branches and the optimization level when compiling the program, the trace data may take minutes to return, E2 emulator Lite especially taking longer time due to lower speed. While waiting for the trace data to return, all debug related operations may become unresponsive and time out.

To workaround this, try increasing the optimization level, as well as increasing the command timeout from Window > Preferences > C/C++ > Debug > GDB > Command timeout (ms), and the remote timeout by entering "set remotetimeout 90" for example in the Debugger Console after connection is established.

Affected device families:RA

Performing Step Return from an inactive thread in an RTOS project may trigger an error dialog. This operation is not supported; step operations should be performed only on the active thread.

Affected device families:RA

On devices with an ARM CortexM4 core, enabling the RTOS Integration in Debug View feature may cause the debugger to hang or terminate unexpectedly. Please do not enable this feature for these devices.

Affected device families:RA

Eventpoints View can only set eventpoints for the currently selected core in Debug View for multicore debugging using E2/E2 Lite. Please do not switch between cores in the Debug View when setting or deleting eventpoints. Additionally, eventpoints can only be set for one core at a time, please remove all existing eventpoints before setting eventpoints for a different core.

Affected device families:RA

This issue can occur if the user selects the "Use Renesas Partition file" checkbox and does not specify a value for the Renesas Partition file in the field underneath the checkbox. The dialog should show an error message when the user does this but does not do so in all cases (E.g. if no action is selected). If the user closes the dialog in this state and attempts to reopen it a NullpointerException is thrown because no Renesas Partition file is specified. The workaround is to delete the dpmsettings.xml file from <WORKSPACE_LOCATION>\.metadata\.plugins\com.renesas.cdt.ddsc.dpm.ui

Affected device families:RA

When using the Integration Service with RA devices, register values cannot be retrieved correctly for registers that include bitfields.