IAR Embedded Workbench for Eclipse (EWV850 version 4.1)

Known issues

• Canceling the I-jet Probe Selection dialog on debugger startup has no effect (ECL-3130)
• Running a C-STAT analysis on a project where header files which are not part of the project itself will produce "Missing Resources" errors when the analysis is performed the first time. (ECL-3119)
• Installing the IAR plugins in Eclipse 2020-06 requires the user to run Java 11 or untick the "Verify provisioning operation is compatible with currently running JRE" option in Windows>Preferences>Install\Update or the installation will fail. See https://wiki.eclipse.org/CDT/User/NewIn911 for further details. (ECL-2991)
• Using the "@" placement operator in a function declaration will result in a syntax error being reported by the CDT indexer. The workaround is to use a #pragma location instead. (ECL-1801)
• In projects which use many/long include paths, the compiler command line might exceed system limits, which in turn might cause the Eclipse CDT Internal Builder to truncate it. A workaround is to build the project using make, via Project > Properties > C/C++ Build > Tool Chain Editor > Current builder, by setting it to Gnu Make Builder. For further information about Eclipse CDT and command line length, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=72965 . (ECL-1794)
• The Debugger settings tabs do not support Eclipse build variables syntax (e.g. ${ProjName}). However, EW variables are supported ($TOOLKIT_DIR$, etc). (ECL-1650)

Resolved issues

• The Gnu Make Builder will now use a relative path to the linker command file (.xcl). (ECL-3047, resolved 2021-03-15)
• The dependencies on Eclipse EMF have been reduced to the ecore and databinding features. (ECL-3019, resolved 2020-11-09)
• Fixed an issue where the Gnu Make Builder would not be correctly detected if a project was originally created with a different toolchain than IAR, resulting in build errors. (ECL-3002, resolved 2020-11-05)
• Improved compatibility with MSYS64 make when building using makefiles on Windows. The following Java system properties can be set to enforce Windows cmd or Bash syntax when generating linker makefile scripts for ilink: com.iar.ilink.make.useBash or com.iar.ilink.make.useCmd (ECL-2750, resolved 2020-03-24)
• Fixed an issue where attempting to read the compiler and/or C-STAT version information would cause an UnsatisfiedLinkError if Java 9 or later was used. (ECL-2931, resolved 2019-10-22)
• The plugins will now try to recover from errors occurring when reading Windows versions of tools, instead of causing a fatal failure when building / importing. It is recommended that Eclipse is run with administrator rights if such failures should occur. (ECL-2887, resolved 2019-08-22)
• Fixed an issue where the common features of the plugins would erroneously be updated from an older branch, causing the Eclipse installation to be corrupted. (ECL-2733, resolved 2018-09-01)
• The IAR Plugin Manager now supports Eclipse Photon. (ECL-2730, resolved 2018-08-01)
• Added support for the CMSIS-DAP debugger probe. (ECL-2503, resolved 2018-05-28)
• Support for generating debug traces for IAR Eclipse Plugins. The format is compatible with the Chrome Trace Format. It is enabled by setting the Eclipse debug option com.iar.ide.common/debug/chrometrace to true in the .options file, or by selecting it in Window → Preferences → General → Tracing → Enable tracing → IAR Toolchain and Debugger Tracing. (ECL-2670, resolved 2018-04-17)
• The file importer.properties can now contain relative paths (relative to the Eclipse project), and any existing values in the files are not overwritten when updating projects. (ECL-2445, resolved 2018-03-21)
• The IAR Plugin Manager now shows the compatible versions of Embedded Workbench for each target in the target name. (ECL-2526, resolved 2017-10-13)