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:RX

When connecting to RX26T with emulator, an endian mismatch warning may be displayed if the debug configuration is configured as the dual mode and the big endian. The warning can be ignored.

Affected device families:RX

Information regarding bit symbols may not be displayed for RX device’s Smart Manual.

Information concerning bit symbols is contained within the register information. Please check the register information.

Affected device families:RX RL

Using Optimization Assistant Time measurement with GCC RX may cause the measurement unable to finish. The end address of function build from GCC RX may be different with the one in Disassembly view so Optimization Assistant cannot reach the end of function. If the measurement is too long to finish or unable to finish, just press "Cancel" to stop measurement.

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:RX

When using RX simulator with the setting of big endian, writing the value for 64bit DPFPU register from Registers View will not work correctly.

Affected device families:RX

When debugging RA or RX devices, the stack trace for the interrupt frame will not be displayed separately in Debug View. The feature is disabled for the version.

Affected device families:RX

When debugging with the RX device family and the FreeRTOS operating system it is possible for the debug view to show incorrect numbers of threads.

Affected device families:RX

When debugging the project generated as big endian by GCC, the breakpoint may not work while debugging, if the optimization option is '-Og'. In this case, please change the option to '-O0'.

Affected device families:RX

Timer events have not been supported on RX devices when debugging with J-Link. Although they can be set, they do not work.

Affected device families:RX

If you connect a debugger with an endianness that differs from the endianness written in the RX14T, the following error may be displayed.

"Error while detecting device endianess"

In this case, close the debugger connection and reconnect it.

Affected device families:RX RL RH

All toolchain projects:

Build error occurs when executing Build with a new Build configuration you added.

At that case, please specify the toolchain and device to your project.

After opening the project, this can be achieved via the Project Explorer, project context menu.

On this menu access the "Renesas C/C++ Project Settings" and use the "Change Device" and "Change Toolchain Version" features.

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:RX

When selecting the DSP core on Debug view, modifying the value of IO register on the IO Registers view will not take effective.

Workaround: Select CPU on Debug view and modify the DSP IO register correspondingly

Affected device families:RX

When doing the debugging with the project contains anonymous union variable in source code, some debugging features become unavailable, such as:

Affected device families:RX

Some RX devices such as RX72M supports double precision FPU registers. But when debugging it with J-Link, the registers is displayed as 0 in Registers View and writing a value to the register will be ignored.

Affected device families:RX

When using J-Link for RX devices, adding a regular breakpoint from breakpoint view may fail and changing the breakpoint type may cause a break, even if the breakpoint is removed. Please set the breakpoint from source view.

Affected device families:RX

In certain situations the errors that are displayed after a build will overlap the source line in the editor window. If this occurs scrolling the editor view up or down seems to resolve this.

If this becomes a common occurrence it is possible to stop this happening by switching off the code mining option.

This is available in the Window→Preferences page. In the section General→Editors→Text Editors. The option to switch off is named Show code minings for problem annotations. Change this setting to None.

Affected device families:RX

When using the Renesas CCRX project conversion to Renesas GCC RX errors can occur when converting a rpoject from CC-RX to 3.07 to GCC 14.2.0.202505.

Errors relating to these can be seen:

Affected device families:RX

C++ static data members are shown as <optimized out>, when using CC-RX toolchain.

Affected device families:RX

When using RTOS integration in Debug View with the RX family, interrupts or exceptions may cause the thread call stack to be displayed incorrectly.

Affected device families:RX

When using J-Link RX with RXv3 core devices, Trace view can’t show the disassembly for the area from the branch destination to the next branch source if RXv3 instruction is included in the area.