Renesas Release Information

Open issues for DA devices

Released: 22nd July 2024

Version: e2 studio 2024-07

List generated on 18 July, 2024 16:24

Device Specific Issue Lists

Fixed Issues

Open Issues

IDE-76485 DA SDK Importer - Project 'xxx' has no explicit encoding set - warning (DA SDK Support)

Affected device families:DA

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

Project <project name> has no explicit encoding set

This does not cause any harmful effect.

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

IDE-79115 Add python 3.x interpreter in e2s CMake execution path on Linux causes build to fail (DA SDK Support)

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:

CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

There is no workaround.

IDE-79140 Retest BLOCKED DA CMake tickets on Linux host (DA SDK Support)

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:

CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

There is no workaround.

IDE-73750 e2Studio debugger needs to be started twice for DA14592 (Debugging DA)

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.