IAR Embedded Workbench for Eclipse (EWMSP430 version 6.50)
Known issues
- 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)
- The General > Tracing preference page might be missing when installing our plugins in the Eclipse CDT distribution. (ECL-2668)
- Using source file or source folder names containing spaces is not supported by the Gnu Makefile builder and will result a linker error. See http://savannah.gnu.org/bugs/?712 (ECL-2664)
- Excluding / including a source file from the project will cause recompilation of all files because of a known Eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=193286 . Also note that object files for the excluded sources will not be automatically removed from the build output folder. (ECL-2625)
- There is no support the CMSIS-DAP debugger probe. (ECL-2503)
- 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)
- When the "@" placement operator is used in a declaration, the CDT Indexer will also report a dummy char * @ variable declaration after it. (ECL-1193)
Resolved issues
- 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)
- Fixed an issue where a default device would not be configured properly when using CDT's "Empty project" template to create a project. (ECL-2995, resolved 2020-08-11)
- Fixed an issue where some toolchain integrations could be disabled when installed together with EWARM 8.50.x plugins (ECL-2975, resolved 2020-05-04)
- The checksum initial value field now accepts both decimal and hex numbers. (ECL-2953, resolved 2020-03-02)
- 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)
- The IAR Plugin Manager now supports Eclipse Photon. (ECL-2730, resolved 2018-08-01)
- The generated makefiles when building using the Gnu Makefile Builder will now be generated in a suitable format if Cygwin is detected in the system PATH environment variable. (ECL-2671, resolved 2018-06-14)
- Fixed a syntax error in the makefiles generated by the Gnu Makefile Builder which would be detected when running them in Cygwin make. Please note though that the IAR Eclipse plugins are only tested using MinGW make utility version 3.81, so compatibility with Cygwin cannot be guaranteed. (ECL-2699, resolved 2018-06-04)
- 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)
- When building using the Gnu Makefile Builder, the generated makefiles will now use a .xcl input file to read linker arguments in order to avoid command line length issues (ECL-2632, resolved 2018-04-06)
- 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)
- Fixed an issue with the IAR Plugin Manager which caused the installation path to the Embedded Workbench for ARM 8.x installation to not being setup when Eclipse started. When installing in Renesas e2studio, please ensure that the IAR Plugin Manager is updated to its latest version available at http://eclipse-update.iar.com/plugin-manager/1.0 (ECL-2613, resolved 2018-02-27)
- Using the --preprocess option no longer causes an exception when collecting the compiler's built-in include paths. (ECL-2601, resolved 2018-01-30)
- Fixed a compatibility issue with certain versions of Renesas e2studio which could cause an exception to be repeatedly thrown when updating project options. (ECL-2579, resolved 2017-12-20)
- Fixed an issue which could in some cases cause a workspace rule exception to be thrown when modifying linker options. (ECL-2559, resolved 2017-11-23)
- Fixed an issue where some build options were updated correctly after using the "Select Device" dialog. (ECL-2278, resolved 2017-10-20)
- 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)
- Release notes are now being generated for all IAR build integration plugins. (ECL-2513, resolved 2017-10-04)
- The plugins now use a Language Settings Provider to make built-in include paths and symbols visible to the code indexer. Additional settings can be found in Project > Properties > C/C++ General > Preprocessor Include Paths, Macros, etc.. (ECL-1325, resolved 2017-10-03)
- Source file extensions can now be customized. (ECL-521, resolved 2017-10-03)
- Fixed an issue where the Optimization options GUI would not be updated correctly. (ECL-2498, resolved 2017-09-26)
- Fixed an issue which could cause projects to always be rebuilt even if no changes where present. (ECL-2423, resolved 2017-08-08)
- Fixed a bug which prevented in some cases the error reporter dialog from appearing. (ECL-2400, resolved 2017-04-28)
- Fixed an issue where a project option update could in some cases not trigger an update its dependent options. (ECL-2254, resolved 2017-02-02)
- The toolchain restart dialog in the IAR Embedded Workbench preference page will now use the Eclipse product name. (ECL-2212, resolved 2016-09-29)
- Fixed a bug which caused some options to appear as uninitialized if the project was built directly after Eclipse was restarted. (ECL-2205, resolved 2016-09-20)
- The IAR Embedded Workbench preference page now supports Eclipse variables like eclipse_loc or workspace_loc when specifying installation paths. (ECL-2176, resolved 2016-07-27)
- Source indexing is now disabled while importing Embedded Workbench projects, and re-enabled when import is complete. (ECL-2133, resolved 2016-05-09)
- Fixed an issue where an empty file path in an option might erroneously be converted to a path to the imported project's folder. (ECL-2061, resolved 2015-12-21)
- Fixed an issue where Eclipse would not start if the installation of Embedded Workbench being used was removed. (ECL-2058, resolved 2015-11-13)
- Fixed an issue which would cause an exception to be thrown when right-clicking on a project right after Eclipse startup. (ECL-2027, resolved 2015-09-14)
- The Function Profiler view is now available in Eclipse when running against Embedded Workbench for ARM 7.40.4 or newer. (ECL-536, resolved 2015-09-01)
- Fixed an issue which caused an exception to be thrown during device initialization when building in headless mode. (ECL-2015, resolved 2015-08-31)
- Errors on source files outside of the worspace will no longer cause the creation of a linked resource in the workspace. Note that in order to navigate to the corresponding source file, the error marker must be right-clicked, choosing "Open external location". (ECL-1991, resolved 2015-07-22)
- The _BASE_FILE_ macro is now correctly parsed by the Eclipse CDT code indexer. (ECL-1981, resolved 2015-07-06)
- Fixed an issue which could cause Eclipse to deadlock on startup. (ECL-1956, resolved 2015-05-21)
- Using the IAR plugins in a headless build no longer clutters the build output with Eclipse exceptions. (ECL-1576, resolved 2015-05-21)
- The IAR plugins now require Java 1.7 or newer. (ECL-1930, resolved 2015-03-30)