Affected device families:R-Car RH

When multiple bare-metal debug sessions are connected the Download button may send the program to the wrong connected session.

Affected device families:RX RL RH

After importing CS+ project to e2 studio 2024-04, be sure to reconfigure your device settings for Build according to the steps below.

Because your project device settings for Build will be empty when importing CS+ project to e2 studio 2024-04.

Affected device families:RX

When using Segger J-Link for RX devices, Renesas Debug Virtual Console view will not work.

Affected device families:RX

OFS definition for ROM code protection is missing in GCC linker script files of RX66T/RX72T.

Affected device families:RX

In certain situations the Save Build Settings report does not work correctly when using the CC-RX toolchain.

An error is thrown:

"Cannot invoke "String.toLowerCase()" because "fileSpecText" is null"

A possible workaround could be to set "Check the source code by MISRA-C" option to "No".

Affected device families:RL

Build error occurs and .x file for FAA core is not generated when using CC-RL and FAA Assembler for FAA equipped RL78 devices.

ex)

CreateProcess failed (2).

To generate .x file, specify command line to execute renesas_cc_converter with its path to post-build steps in Build Steps tab of "C/C++ Build → Settings" in the project properties. makefile contains command line of renesas_cc_converter.

ex)

Add the path to the command line above and specify it to "Post-build steps".

You can get the path of renesas_cc_converter.exe by going to "Support Folders" tab in "e2 studio Installation Details" opened from "Installation Details" button on "About e2 studio", click link for "e2 studio support area:", and find renesas_cc_converter.exe in \Utilities\ccrl folder.

example of command line specified in post-build steps:

C:\Users\username\.eclipse\com.renesas.platform_1195273088\Utilities\ccrl\renesas_cc_converter faa_sample.abs faa_sample.x -dsp_section=FAACODE,FAADATA

The above workaround will still show a failure, but renesas_cc_converter is executed after that and generates .x file correctly.

Affected device families:RL

When using hotplug connection for debugging, please set the option "Set breakpoint at:" enabled on the debug configuration, although the breakpoint will not be set.

Affected device families:RA RISC-V MCU

When debugging ARM devices with J-Link, execution address event on Eventpoint view is not supported.

Affected device families:RA

Currently support for the Trace Start\Stop feature when using the JLink emulator is not functioning for ARMv8-A based cores.

Affected device families:RA

RTOS threads may not correctly show call stacks when stepped after being Paused. Linux only.

Affected device families:RISC-V MCU

When using RISC-V MCU with J-Link, please do not select 'Auto' or 'Adaptive' for the interface speed in the debug configuration. Please strictly use cJTAG interface type only for connection.

Affected device families:All

Installation for all users and running e2 studio from installer can cause problems with access to support files and workspace locations.

This issue occurs when a local administration user installs e2 studio and runs for the first time. If this user also creates a workspace subsequent different users with lower privileges may experience problems when trying to open that workspace.

Depending on installation configuration you may see an error like "Error extracting synergy support files".

To avoid this issue subsequent users should create a new workspace.

Affected device families:All

When using e2 studio or RASC with Ubuntu 22.04 documents that are opened from the application in an external web browser cannot be viewed.

This appears to be a bug in Ubuntu. In Ubuntu 22.04, the sandboxed "Snap" version of Firefox is installed by default. However the default sandbox permissions for this version of Firefox are broken for fresh Ubuntu 22.04 installations and it cannot access any files on the local file system.

This is reported and documented in the Ubuntu bug tracker: https://bugs.launchpad.net/snapd/+bug/1972762 All applications that require the system web browser are affected

Affected device families:All

In Visual Expression view, char / unsigned char variables are not recognized and shown as "Incompatible expression value"

Workaround: Cast can be workaround such as (int)var instead of var.

Affected device families:All

If copying a project with it’s build output directory been Windows & Linux, or moving it to a new location, you need to do a clean and rebuild to avoid build errors.

If storing a project under version control avoid including the build output directories. At a minimum exclude the *.d files which may contain system specific paths.

Affected device families:All

When using the debugger with the eventpoints view in some situation you may notice that the "External Trigger" is invisible, but the tooltip is still shown when hovering over it.

This feature is only avaialble when debugging with the E2 emulator.

Affected device families:All

When building on macOS you may see "fcntl(): Bad file descriptor" appear in the build console.

You can avoid these errors by going to "C/C++ Build → Behavior" in the project properties, selecting "Use custom build arguments" and setting the build arguments to "-r -jN" where "N" is the number of parallel build processes to use. This may however result in false build errors and warnings to show in the problems view & at the end of the build console.

Affected device families:All

The toolchain manual feature accessible from Help→View Installed Toolchains will not open the toolchain manual directory on Linux host OS.

Affected device families:All

When using the Integration Server to debug a NEW project, it is disconnected automatically (debugging with e2 studio works normally).

Workaround: Open Debug Configuration and select the project launch to resolve the issue.

Affected device families:All

To fix BadAlloc Vulnerability issue reported on the newlib in "Japan Vulnerability Notes",

need to update GCC/libgen version for Arm to the fixed version including newlib V4 or later. Could you please consider the updates in coming 2022-10 version?

If GCC Arm Embedded is used for Renesas Arm (RA, Synergy, RZ, RE and R-Car),

use or install:

GCC ARM Embedded Toolchains v1.2022.05 or later which has newlib 4.1.0 or later.

Libgen Update for GCC ARM Embedded Toolchains v1.2022.05 or later.

Affected device families:All

On some Windows systems a component of e2 studio is flagged by Windows Defender has suspicious.

This is due to the clangd component we are using within the product.

If this occurs you will need to workaround this within the Windows Defender tool.

Useful link: [https://answers.microsoft.com/en-us/windows/forum/all/windows-defender-flagged-my-c-program-as-trojan/bfad521c-7129-4f63-8c84-98a16f0a50e2]

Affected device families:Synergy

When installing the IAR eclipse plugins into e2 studio for IAR EWSYN, the installation process can generate a warning about unsigned software being installed.

This is normal behavior for the IAR plugins and the warning can be disregarded.

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

Debugging on Linux with RZT_FSP v1.2.0 for RZ/T2M or RZ/T2L is not supported.

Affected device families:RZ

Debug connection may fail due to time out when downloading a large program.

In this case, please reconfigure the time out setting of GDB in [Preferences] dialog.

Please follow below steps to reconfigure the time out setting of GDB

Affected device families:RZ

For the RZ/T2M device e2 studio does not support semihosting with the E2 emulator

Affected device families:RZ

When debugging, if a variable which can’t be accessed on reset is added to Expressions view, the next connection or resume may fail. In this case, please disable the variable on the Exressions view before connection or reset.

For example, the variable is located at external memory area and the area is disabled on reset and if the memory access for the disabled area causes an exception in the device, this issue will happen.

Affected device families:RZ

When debugging RZ devices, PC will not stop at an address of reset vector on reset. Program will run in a short time after reset, and then, the program will be halted.

If the program is built for RAM debugging (without using boot loader), the program will not run after reset correctly. In this case, please re-download the program (please don’t forget to set "Reset after reload" option to 'No' on Debug Configuration) after reset, or disconnect the debugging and re-connect.

Affected device families:RZ

The debug launch for RZ/A3UL may fail with read memory errors at initial launch. Add the command "set breakpoint enable-memread 0" to the Debug Configurations → Startup → Initialization Commands field to resolve this.

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

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

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

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

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

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

Affected device families:RX

When debugging RX devices, the performance analysis result which is measured by the timer start/stop events may not be displayed. In this case, please re-set the event after the connection.

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 doing the debugging with the project contains anonymous union variable in source code, some debugging features become unavailable, such as:

Affected device families:RL

In case of using RL78, hardware breakpoint is realized by execution address after PC. This will cause several issues:

Affected device families:RL

The addresses for source lines may not be shown when debugging for projects imported from CS+.

To avoid this ensure the project is imported using the same name as its directory.

Affected device families:RL

Workaround: If user using monitor point with Current Consumption, Chart will be displayed normally when the user press and hold the mouse on the horizontal scroll of the range of time.

Affected device families:RL

The Code generator support for RL78 on MacOS is not installed by default. You can add this later using the "Help→Install New IDE Features…​" feature.

Affected device families:RH

It is not possible to perform a step return operation when using the CC-RH toolchain while debugging assembly source.

Affected device families:RH

If you are debugging RH850 with the E2 emulator with an IAR project you must ensure that the IAR RH850 plugins are also installed. Otherwise it is not possible to set breakpoints.

Affected device families:RH

When opening the debug configuration for E2 (RH850) or IE850A (RH850), the value of OCD ID may be displayed on the invalid location. In this case, please expand 'Flash' node on Connection Settings.

Affected device families:RH

Stepping code can jump to address without code if compiler CCRH compiles the code that contains floating point numbers.

Affected device families:RH

When a multi-core debugger is connected, an error dialog will be displayed if you execute Disconnect with the top of the debug session tree selected on the Debug view.

The disconnection process will be performed normally, so please ignore the error.

Affected device families:RH

When debugging with the RH850 using the E1 emulator Performance Analysis data is not displayed in that view when eventpoints are also configured.

For example when there is a configured Timer Start/Stop event the Performance Analysis view data is empty even when switched on.

Affected device families:RE

When using the IAR toolchain with e2 studio and you try to create a RE family project. The project generation will fail.

A message "Project cannot be created" is displayed along with the text "Failed to set option".

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

The Linux installer for e2 studio cannot be run as root by default, including using "sudo". If you wish to run it as root then you need to add "--appimage-extract-and-run" as the 1st argument.

e.g. "sudo ./e2studio_installer-2021-07.AppImage --appimage-extract-and-run"

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

When using RA devices with TrustZone via J-Link and FSP 5.4 or later is installed, a reset command may be ignored if the DLM of the device is for non secure debugging. In this case, please change the setting "System Reset Request Accessibility" for the secure project on FSP to "Both Secure and Non-Secure State".

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 changing the toolchain version of an FSP project using the ARM-6 toolchain, some options may not be converted correctly and some will be completely removed from the project. This will result in build failure. In this case, you will need to reapply any missing toolchain options.

Instead, it is recommended to create a new project using the destination ARM toolchain version, and then to copy across the source code and any user-added options from the original project.

Affected device families:RA

In Renesas Device Partition Manager (RDPM), when connecting to EK-RA6M4 using J-Link OB, the connection will potentially fail if connection is attempted quickly in succession. Please wait a few seconds in between each connection to minimize the occurrence of the issue.

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 using ARM Cortex-M4 devices with J-Link, Trace Start/Stop events can be set on Eventpoint view. But the events will not trigger start/stop of the trace.

Affected device families:RA

When using ARM Cortex-M23 devices with J-Link, Eventpoint view enables to input the address mask value. Please don’t specify the address mask, as the mask setting will not work.

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

It is not possible to connect to a running device (hot-plug connection) with Segger J-link for RA and DA in e2 studio. This is due to a problem in this area and it will be solved in the near future.

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

Disconnect an RA board with the "Continue" option (allowing the user code to execute after disconnecting from JLink) does not work when using semihosting.

To work around this make sure you have conditional code for when the debugger is not connected, e.g.

semihosting_printf( …​ )

{

}

#if semihosting

#else

#endif

Additionally, the use of an updated hard-fault handler to catch this situation would also help.

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

If a property from the constraint link in a module tooltip is selected before the Properties view is initialised the property is not selected in the Properties view

This only occurs after the FSP Configuration has first been opened and no module has been selected

A workaround is to select a module in the Stacks view before selecting a link from one of the module tooltips so that the Properties view is initialised

Affected device families:DA

After importing a DA Indium SDK CMake project into e2 Studio, the following warning appears in the Problems view:

This does not cause any harmful effect.

A quick fix is available on the warning which does remove the problem.

Affected device families:DA

On Linux host, after using the new import wizard, "DA CMake Project (experimental)", to import a Dialog SDK CMake source project, attempting to build the project fails with the following console message:

There is no workaround.

Affected device families:DA

On Linux host, after using the new import wizard, "DA CMake Project (experimental)", to import a Dialog SDK CMake source project, attempting to build the project fails with the following console message:

There is no workaround.

Affected device families:DA

Under certain conditions when using the DA14592device the debugger has to be started twice after a new compilation.

In order to program the eFlash after (re)compilation the debugger has to be started. A pop-up window is showing that the eFlash is erased and programmed, then the GDB debugger is started but does not halt atmain(), and keeps running.

If the debugger is reset and started again it is possible to control the debugger as normal.