Read about the latest features, new device support, and program corrections in the release notes.
Support for the C11 language standard
The compiler and libraries adds support for the latest C language standard ISO/IEC 9899:2011.
Note: the new C library binary object interface is incompatible with earlier EWARM versions, see the compiler release notes for more details.
Support for the C++14 language standard
The compiler and libraries now supports the latest C++ standard ISO/IEC 14882:2014.
Note: the new C++ library binary object interface is incompatible with earlier EWARM versions, see the compiler release notes for more details.
Updated IDE look and feel
With new artwork, enhancements to window management and docking, revised Information Center and new tutorials.
General support for Unicode
The whole toolchain now support Unicode including compiler, IDE, editor and debugger.
CMSIS-Pack support
The project manager have been extended to read and operate with ARM CMSIS-Pack software components.
Trace filtering and navigation features
Navigation in large trace data acquisitions is considerable easier with possibility to navigate forward/backward on loop, function, interrupt and statement boundaries.
New device support
| AmbiqMicro | APOLLO2_1024 |
|---|---|
| Atmel | ATSAMC20J17AU ATSAMC20J18AU ATSAMC20N17A ATSAMC20N18A ATSAMC21J17AU ATSAMC21J18AU ATSAMC21N17A ATSAMC21N18A ATSAMD51G18A ATSAMD51G19A ATSAMD51J18A ATSAMD51J19A ATSAMD51J20A ATSAMD51N19A ATSAMD51N20A ATSAMD51P19A ATSAMD51P20A ATSAMDA1E14B ATSAMDA1E15B ATSAMDA1E16B ATSAMDA1G14B ATSAMDA1G15B ATSAMDA1G16B ATSAMDA1J14B ATSAMDA1J15B ATSAMDA1J16B ATSAME51J18A ATSAME51J19A ATSAME51N19A ATSAME51N20A ATSAME53J18A ATSAME53J19A ATSAME53J20A ATSAME53N19A ATSAME53N20A ATSAME54N19A ATSAME54N20A ATSAME54P19A ATSAME54P20A ATSAMV70J19B ATSAMV70J20B ATSAMV70N19B ATSAMV70N20B ATSAMV70Q19B ATSAMV70Q20B ATSAMV71J19B ATSAMV71J20B ATSAMV71J21B ATSAMV71N19B ATSAMV71N20B ATSAMV71N21B ATSAMV71Q19B ATSAMV71Q20B ATSAMV71Q21B |
| Cypress | S6J327CK S6J327CKxC S6J327CKxE S6J327CL S6J327CLxC S6J327CLxE S6J328CK S6J328CKxC S6J328CKxE S6J328CL S6J328CLxC S6J328CLxE S6J32AAK S6J32AAL S6J32BAK S6J32BAL S6J32CAK S6J32CAL S6J32DAK S6J32DAL S6J32EEK S6J32EEL S6J32FEK S6J32FEL S6J32GEK S6J32GEL S6J32GEM |
| Mediatek | MT2523D MT2523G MT7687F MT7697 MT7697D |
| NordicSemiconductor | nRF52832-xxAB |
| NXP | MCIMX7D2 S32K142 S32K148 |
| STMicroelectronics | STM32F722ZE |
| TexasInstruments | CC3220 PGA970 |
Device support
Example projects
Over 9000 example projects for various evaluation boards, are included in the product installation, see the Information Center.
To avoid any problems, do not install this release in a directory where you have previously installed any older version of IAR Embedded Workbench. It is recommended that you either uninstall an earlier product, or install this release in a separate directory. As before, however, it is possible to install different products, all using the same version of the main application, in the same root directory.
The upgrade to this version might require a license renewal. This is performed by starting the IAR License Manager and selecting License>Check for License Renewal.
Note, if you have a network license, this must be performed on the license server.
Microsoft SCC-compatible version control systems are no longer supported by IAR Embedded Workbench.
Windows Vista and newer operating systems have a security mechanism called UAC (User Access Control). Disabling UAC will automatically grant you permission when a task requires administrative rights but this is not recommended because it will reduce the security of the computer. It is not necessary to run the IAR Embedded Workbench IDE as an administrator. However, if you are not, modifications to the installed product tree in C:\Program Files\IAR Systems might not work as intended and could give unexpected results. One example is opening and building projects directly from the installed product tree. The build will succeed, but the resulting files (object, list, …) will not appear where expected. Instead all output files will be redirected by the OS to C:\Users\<user name>\AppData\Local\VirtualStore\Program Files\IAR Systems. To avoid this, the preferred way is to copy the examples to a location outside Program Files, either manually or automatically by opening them via the IAR Information Center.
For network licenses, this version of the IAR Embedded Workbench requires IAR License Server Tools version 2.15.4 or later, for more information see technical note TN21842. The latest IAR License Server Tools are backwards compatible with previous IAR Embedded Workbench versions.
The debugger flash loader mechanism was changed in version 5.40. If your project uses a default flash loader with no extra parameters, no migration work is needed.
If the debugger detects that your project uses a non-default flash loader or that it uses extra parameters, it will revert to the default flash loader for your device. In addition a .board file will be created in the project directory. If necessary the .board file can be edited and used by manually overriding the default flash loader with this project-specific .board file.
If you are migrating from version 4.x to this version, we recommend that you read the ARM IAR Embedded Workbench Migration Guide.
The compiler, assembler, linker and debugger object format is based on the ARM ABI ELF/DWARF standard version 2.08. For the standard definition, see the ARM Application Binary Interface.
IAR, IAR Systems, IAR Embedded Workbench, C-SPY, C-RUN, C-STAT, IAR Visual State, Focus on Your Code, IAR KickStart Kit, IAR Experiment!, I-jet, I-jet Trace, I-scope, IAR Academy, and the logotype of IAR Systems are trademarks or registered trademarks owned by IAR Systems
Microsoft and Windows are registered trademarks of Microsoft Corporation. Adobe and Acrobat Reader are registered trademarks of Adobe Systems Incorporated. CodeWright is a registered trademark of Starbase Corporation. All other product names are trademarks or registered trademarks of their respective owners.