Affected device families:All

When debugging a project in a new workspace using the first instance of e2 studio opened, the GDB Server’s console is split into two different consoles instead of a single one. Some of the GDB Server console messages are duplicated and printed twice. Please try relaunching the project and continuing the debug session; subsequent debug launches seem to work fine.

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

If a download is invoked while the program is running, the download may fail due the the state of the CPU. Please don’t invoke the download while CPU is running.

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

When debugging RL78 G24 device with FAA core using launch configuration created manually, resuming FAA core may not work after stepping.

In this case, please add "-uSyncMode= async" as additional gdb server argument before debugging.

Affected device families:RH

While debugging for RH850 devices, the loading trace record operation for Trace View may fail. Please record it as a text and see the result in some editor application.

Affected device families:RH

The unit of Execution Time in the RH850 profile view is the number of CPU clocks. You can obtain the actual time by dividing it by the CPU clock frequency.

Affected device families:RH

The Profile view does not support multi-core execution.

When using Profile view, please execute only one core.

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

The RTOS Resources view does not update correctly when switching between multiple debug sessions.

Workaround: The view is still connected to the first context. If you suspend the first project then the correct information is displayed.

Affected device families:All

While debugging, Image rendering on Memory view may not be able to show the loaded image on Linux.

Affected device families:All

In the Smart Browser , the genre table should contain one or more of the following items:

Special Offers

Solutions Category

Products Category

Documents Category

Part Name Category

These are currently not displayed correctly.

Affected device families:All

When using the Real-time Refresh feature in the RTOS Resource view, the functionality does not behave reliably.

On extended usage you may experience the following issues:

Occasionally, there will be some duplicate information about the state of threads as illustrated.

Sometimes, the state value is displayed in rows that do not correspond to any task.

Affected device families:All

The "Real-time Refresh" feature may occasionally display incorrect information, such as missing or duplicate rows. If this occurs, please manually refresh the "RTOS Resources View" by clicking the "Update Information" button.

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

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

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

Error messages reported by the Expressions view may contain invalid characters when viewed on a Linux OS.

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

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

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

While debugging, when an timer start/stop event is set on Eventpoint view and the event is removed from Editor view, the event may not be removed on Eventpoint view. In this case, please remove the event on Eventpoint view manually.

Affected device families:All

In the Debug Configuration dialog, settings can only be reverted once each time the dialog is opened. Any changes made after the initial revert cannot be undone until the dialog is closed and reopened.

Affected device families:All

The number of used event points displayed in the Eventpoints view may be incorrect.

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

Importing older RZ/A FSP projects from 2024-10 can cause build errors following import:

Error messages can be seen friom the build such as:

Assembler messages:

Error: selected processor does not support `crc32cb w0,w0,w3' {code}

To fix:

Configure Enable to Feature crc on the Target Processor field.

Add -mcpu=cortex-a55 to Other target flags.

Affected device families:RZ

When using Eventpoint view for RZ devices, the timer start/stop events or the trace start/stop events would not be supported.

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

RZA3UL with FreeRTOS requires a breakpoint at main() in order to be able to debug threads.

It is necessary to stop at main() for the debugger to detect that the RTOS symbols are accessible.

Affected device families:RZ

While debugging, if the reset or restart operation is invoked while the program is running, the debug connection may be disconnected. Please push the reset or the restart button while the program is suspended.

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

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

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 CR52_1 on RZ/T2H, the debug connection may fail with the default lauch settings. In this case, please specify "Prevent Releasing the Reset of the CM3 core" to 'Yes'.

Affected device families:RZ

On Ubuntu 22.04 and 24.04 the RZ/G1E via TCF connection will not start. The issue is a dependency on python 2.7 which is not present on these systems. Check this link for an update http://security.ubuntu.com/ubuntu/pool/universe/p/python2.7

Affected device families:RZ

For RZ/T FSP multicore projects that utilize linked projects, it’s crucial to maintain consistent FSP versions across all linked projects. Inconsistencies can cause unexpected problems. Currently, e studio does not notify you if the FSP version of a linked project doesn’t match the FSP version of its smart bundle’s parent project.

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

The RTOS integration in Debug View feature is not supported on RZ/T2H devices.

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

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.

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

When debugging project using RL78/G24 CPU with FAA, if "Terminate" button on the toobar is pushed, all debug sessions of both CPU and FAA cores are expected to be terminated.

But actually only the selected session is terminated, the remained session falls in waiting "time out".

If you want to terminate all debug sessions, please push "Terminate all" button on the toolbar instead of "Terminate"

Affected device families:RL RISC-V MCU

When debugging, Editor view does not show the source code for the address, if PC is on 0x0. As the start address is 0x0 for debugging FAA on RL78/G24 or debugging RISC-V MCU, it will happen on debugging.

In case of RL78 FAA, please try followings:

to see the source code updated on the Editor view.

In case of RISC-V MCU, please resume the program to main.

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

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

When importing old project for RL78 (which is created with e2 studio version earlier than 2025-12) of the device which does not support changing boot cluster size setting (such as RL78/G22), the Debug Configuration for RL78 Simulator will show 16 for "Change boot cluster size for BTBLS on connection [KB]".

Even the value shown for the boot cluster size setting, it does not impact to operation of the simulator debugging. Please just ignore it.

Affected device families:RL

The default projects generated using Smart Configurator version v1.16 for RL78/F2x devices have the default value for Flash serial programming security ID 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE not same as default security ID (0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF) of the device. This mismatch causes failing to authenticate when flashing to device. As a result, we cannot debug with it. To able to debug with it:

Affected device families:RL

When reopening and debugging a RL78 Simulator project that was closed with SMS Debug enabled, the SMS Debug button appears ON, but internally the SMS Debug state is OFF. This will lead to the issue that we cannot debug SMS program.

Please push "Turn SMS On/Off" switch to OFF, then Push "Turn SMS On/Off" switch to ON again to able to debug SMS program.

Affected device families:RL

When debugging RL78 project with Simulator, the debug session may be terminated when both RL78 SMS Command List and Trace view are opened at the same time.

Please turn off the Trace view when you intend to debug SMS project.

Affected device families:RL

When debugging RL78 SMS project with Simulator using Renesas RL78 Command List view, some specific SMS instructions execution can invoke CPU running synchronously. But if the CPU is located at a breakpoint, after executing these specific SMS instructions, the CPU PC is not changed as expectation.

To avoid the issue, please delete the breakpoint at CPU PC location when stepping SMS.

Affected device families:RL

When debugging RL78 SMS project with Simulator using RL78 SMS Command List view, in case the Trace/Timer/Coverage is ON, if SMS start break occurred during previous CPU execution, then subsequent SMS stepping may not work properly. In this case, after executing the SMS, the SMS PC and CPU PC may locate to the unexpected locations.

To avoid above issue, please turn Trace/Timer/Coverage OFF when debugging SMS.

Affected device families:RL

When debugging RL78 SMS project with Simulator using RL78 SMS Command List view, in case the Run-break Timer/Coverage is ON, and CPU program breaks on a breakpoint, if SMS steps on a WAIT command, SMS cannot break and keep on running.

To avoid above issue, please turn Timer/Coverage OFF when debugging SMS.

Affected device families:RL

When debugging RL78 project with Simulator using RL78 SMS Command List view, the CPU state maybe in running even if it is suspended actually. The issue happens when the Trace view is turned on or Start/Stop timer events are used.

Please turn off the Trace view or not use Start/Stop timer events when you intend to debug SMS project.

Affected device families:RL

When the RL78 device is changed in the Debug Configuration, the option "Connection Settings > Change BTBLS to use 'bank swap' on connection" keeps the value from the previously selected device.

Affected device families:RH

When using RH850 and GHS the step return button can become disabled. This is a known issue and will be fixed in a future version

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

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

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

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

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:

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.