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 the project is debugged with the setting of 'Symbol only' in the debug configuration, the warning "warning: No executable has been specified and target does not support\ndetermining executable automatically. Try using the "file" command." may be displayed in the gdb traces console. It will not affect debugging.

Affected device families:All

The "Save build log to file" option in the build console may not save the full contents for some projects

Affected device families:Synergy RZ RA DA

When debugging with the Segger J-link with ARM devices such as RA, when you set "Reset before download" to Yes, the reset operation does not take place.

Affected device families:RZ

When debugging RZ devices, if a reset is invoked, when PC is on a breakpoint which is on the external memory where can’t be accessed on the reset state, the further debugging may fail. In this case, reset the program after removing the breakpoint, or use Restart instead of Reset with the command "set breakpoint enable-memread 0" (Please specify the command at "Initialization Commands" on Startup of the debug configuration).

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

-dsp_section option of FAA Assembler tool in Properties→C/C Build->Settings->Tool Settings does not work; this option is visible when the option Enable FAA Assembler in Properties->C/C Build→Settings→→Toolchain is enabled. Please do not use the Enable FAA Assembler option.

Affected device families:RH

When creating a new U2A project on e2studio, the following compiler option is by default enabled:

Generate XFU instructions -Xfxu

This is wrong because there is no FXU on U2A and this causes an unexpected UCPOP exception which stalls the program.

Affected device families:RA

Hotplug debugging of ThreadX RTOS only shows a single thread.

Affected device families:RA

When debugging RA devices with E2 or E2LITE emulator, the debug connection will fail if the option "Reset at beginning of connection" in the debug configuration is set to "Yes". In this case, please specify "No" for "Reset at beginning of connection".

Affected device families:RA

To show RA project (LLVM for ARM compiler) with Stack Analysis View on e2 studio 2024-10, please do the followng procedure:

Affected device families:DA

Building a Dialog SDK project will fail if there are special characters in the SDK path. Please make sure the path only contains alphanumeric characters before importing

Affected device families:DA

On first boot a debugging session may not reach main() due to a missing option. Subsequent debugging sessions (without repowering the board) work correctly. To fix this, set the option 'Reset after download' to Yes in the Launch Configuration options, on the Debugger tab under Connection Settings.

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

If you experience issues installing e2 studio on a very newly installed Windows image.

You will see an error "Unable to connect to Renesas website. Installation may continue but some functions may not be available."

Items such as toolchain download during installation cannot be accessed.

Please try this:

Run this command as admin resolve the issue:

CertUtil -VerifyCTL AuthRoot

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

When debugging Synergy with J-Link, trace information until 'main' may not be displayed. Please get the trace data after the program is suspended at 'main'.

Affected device families:Synergy RE RA

When using Cortex-M devices with J-Link, the operation to save trace information in a file may fail, if trace view uses the display mode for disassemble or source display moded. Please set the disassemble/source mode to off when using the save operation.

Affected device families:RZ

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

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

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

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 Expressions 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, if debug view shows data which is located on the area where is not readable on reset, the next resume/step operation may cause a disconnection of the debugging. Please close the view until the area is readable.

When the program need to be reset, please use 'Break at' for the address where the area is readable on the startup tab, and use 'restart' instead of reset to run the program to enable the debugger to read the memory.

Affected device families:RZ

The resource information display for programs using Azure RTOS in the RTOS resource view only supports AArc32.

The correct resource information is not displayed for AArc64.

Affected device families:RZ

The run break time measurement which is shown in the status bar does not display values for the RZ/A3UL.

Affected device families:RZ

When using Cortex-A/R devices with J-Link, if the device supports ETF as trace buffer, trace view doesn’t show the data.

Affected device families:RZ

The following help content will not be displayed in the English version of e2 studio.

-[e2 studio User Guide]/[Debugging Projects]/[RA,RE,RZ,Synergy Debugging]/[ARM Semihosting(Printf debug etc.)]/[RZ/A1]

-[e2 studio User Guide]/[Debugging Projects]/[RA,RE,RZ,Synergy Debugging]/[ARM Semihosting(Printf debug etc.)]/[RZ/A2]

-[e2 studio User Guide]/[Debugging Projects]/[RA,RE,RZ,Synergy Debugging]/[ARM Semihosting(Printf debug etc.)]/[RZ/T1]

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

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

Optimization Assistant supports only DWARF4 debug format.

If a debug format other than this (such as DWARF5) is selected, the correct values cannot be displayed.

To explicitly use the DWARF4 debug format,

select dwarf-4 in the build settings.

(Properties→ C/C++ Build→Tool Settings → Debug)

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

Project build may fail for LLVM and FAA Assembler for FAA equipped RL78 devices. This is because dwarf-5 debug format is not yet supported by renesas_cc_converter.

Please change Debug format in "C/C++ Build → Settings → Tool Settings tab → Debug" to any value other than "Default" or "dwarf-5".

Affected device families:RL

To use other section name, 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)

Affected device families:RL

When performing a custom installation on Linux Ubuntu an error is displayed regarding the Microsoft .net runtime. This should not be selected for installation on Linux.

If you uncheck 'Renesas RL78 Family Support (requiring .Net Framework)' item in 'Customise Feartures' page then the installation will be successful.

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

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

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

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

If you reload the user program after connecting to the RH850 multi-core debugger, the Debug view will not update correctly.

Either reopen the Debug view, or select each core and perform a reset on each core.

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 debugging RH850 device with multiple core, the multiple core debugging will not work correctly for this version. Please enable only one in the debug configuration for the debug session.

Affected device families:RE RA

When using RA/RE devices with E2/E2LITE emulator, debug configuration will show 'Trace' tab. It will not show any settings.

Affected device families:RE RA

When using the IO Register view and the Selected Register tab for RA or RE device, the selected registers are not restored correctly when the debugger connection is started again.

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

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

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

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

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 building a flat/secure/non-secure project with the IAR build tool on Linux the generated project contains references to Windows batch files. This causes an error. It will be fixed in a future version.

Affected device families:RA

When debugging RA devices, the RTOS threads may not be displayed in Debug View, if the debugging is started withoug opening the debug configuration dialog and the setting is not saved on the latest e2 studio. In this case, please open the debug configuration dialog and start debugging from the dialog.

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

Debugging sometimes jumps to an incorrect address when debugging with RA. This is caused by a toolchain bug that happens when using -gcc-sections . This option is removing the functions with unused code but cannot remove the associated debug information. This can then cause strange debugging where the code appears to jump to address 0.

This is because due to the toolchain issue the debug information for removed functions will look like they are placed at address 0. It happens on devices where the ROM starts at 0x0. This occurs for both GCC and LLVM.

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

mkimage host builds fail for DA14695 and similar devices. Use the pre-built version of the mkimage host application instead.

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.

Affected device families:DA

The Memory Usage view can be shown for DA project with LLVM toolchain but there is a problem:

No device map file → Device Memory Region Usage cannot be shown

Affected device families:DA

When using the "DA CMake Project (experimental)" import wizard, the wizard prompts to "Select root directory" of the SDK.

The correct location is in fact a couple of directories down into the SDK at Software/Source/, for example: