Affected device families:RX

When using the Performance Analysis view. After Timer1 has data from the Timer Start-Stop, it does not clear old data for the next resume-suspend.

Affected device families:RX RA

When working with an RTOS project, it is essential that all threads are executed at least once after creation. Attempting to step into a thread that has not yet been run can terminate the debug session.

Affected device families:RX

When creating a GCC RX project using Free RTOS. After building, the debugger fails to successfully download the application. This causes the debug connection to fail.

Affected device families:RX

When debugging RX devices ( RX140, RX260, RX261) with Segger J-link even if the HOCO operating frequency is set to 24MHz or 48MHz in the OFS1 register, the OFS1 setting after download will be 32MHz.

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

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 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.

Affected device families:RX

For the RX devices, when the program is suspended before the interrupt is enabled, a thread with an unusual stack trace may appear. This thread can be safely ignored.

Affected device families:RX

When using Smart Configurator project with GCC RX toolchain, the --gc-sections setting is unchecked when generating code.

If you wish to enable --gc-sections setting, please check this article https://llvm-gcc-renesas.com/wiki/index.php?title=RX_automatic_interrupt_vector_entry_usage to make sure it does not remove interrupt service routines.

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: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 RL RA

While debugging, if hardware breakpoints are set over the limited number of the breakpoints, the next resume operation will not start the progarm on the device and it can’t be suspended on e2 studio. Please remove or disable the breakpoint which can’t be set before using resume operation.

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

When creating a project for RX110, RX111, RX113, RX130, RX210, RX21A, RX220 using the RX GCC toolchain the default build options are set up incorrectly.

The CPU Type is set to "Default" but should be instead "RX100".

This causes invalid instructions to be generated and can cause the debugger to free run and not stop at breakpoints. Please set the CPU type in the GCC project build settings to RX100 if you experience this issue and rebuild the project.

Affected device families:RX

If the option "RTOS Integration in Debug View" is set to 'Yes' on the debug configuration for RX, the debugging session may be terminated if a step is invoked when the active debug context is not main thread. Please use the option as 'No'.