Release notes
for IAR Embedded Workbench for MSP430 version 7.12.1
Read about the latest features, new device support, and program corrections in the release notes.
- Highlights
- Important information
- Release notes for individual components
- Product packages
- Installation and license activation
Highlights
Version 7.12.1
Support for new devices
Support for MSP430FR2355, MSP430FR2353, MSP430FR2155, and MSP430FR2153 has been added.
FRAM Write Protection
Configurable FRAM Write Protection settings have been added to the IDE for the new devices.
Updated files
Updated device support files, new version 1.205 of the device support and new version 3.13.0.1 of themsp430.dll.
Debug communication logging
It is now possible to log the debug communication towardsmsp430.dll
.
Custom JTAG lock key
For MSP430F5xx/6xx devices, you can now set a custom password.
The following sections are added as complement to the user guides.
FRAM Write Protection
The devices that support FRAM write protection are currently MSP430FR2355, MSP430FR2353, MSP430FR2155 and MSP430FR2153. The configuration settings can be reached from the Project>Options>General Options>MPU/IPE/FRWP tab.
Select the Support FRWP box to enable manual configuration. Then you can use the two subsequent options to select DFWP Data FRAM Write Protection (protection of the information memory) and PFWP Program FRAM Write Protection (protection of the program memory) respectively.
New C-SPY command line options added
Syntax: --erase_exclude_all
For use with: The C-SPY FET Debugger driver.
Description: Use this option to exclude the whole FRAM from erase before downloading.
To set this option, use Project>Options>Debugger>Extra Options.
Syntax: --mspdlogfile
For use with: The C-SPY FET Debugger driver.
Description: Use this option to log the debug communication towards msp430.dll
during the current debug session. The logged information will be written to the file mspdcom.log
.
To set this option, use Project>Options>Debugger>Extra Options.
Custom JTAG lock key
For MSP430F5xx/6xx devices, you can set a custom password. To enable this functionality in the IDE, add the tag lockjtag in the menu file corresponding to your device.
The menu files can be found in the directory C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\430\config\devices
Example: <lockjtag>1</lockjtag>
When this tag is set in the menu file, the password can be set under Project>Options>Debugger>FET Debugger>Download
Important information
- Upgrade information
- Before you install
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.
- License renewal
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 interface no longer supported
Microsoft SCC-compatible version control systems are no longer supported by IAR Embedded Workbench.
- Microsoft Windows
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.
- Using Windows 10 version 1803 and USB dongle licenses can need a workaround. For more information see technical note TN180502
- For network licenses, this version of the IAR Embedded Workbench requires IAR License Server Tools version 2.16.1 or later, for more information see technical note TN21842. The latest IAR License Server Tools are backwards compatible with previous IAR Embedded Workbench versions.
- It will be possible to use a Kickstart project without modifications in the full or Baseline version of IAR Embedded Workbench for MSP430.
- The IAR XLINK Linker, IAR XLIB Librarian and IAR XAR Library
Builder have been moved from the
common\bin
directory to the430\bin
directory. Related documentation files and code examples have been moved to430\doc
and430\src\xlink
respectively. - The CLIB library is deprecated. It will no longer be supported in some future version of the IAR Embedded Workbench for MSP430. Use the DLIB library instead.
Updating to Windows 10 version 1803 can cause a problem with USB dongle licenses
Network licenses
Upgrade from Kickstart to the full version
File locations
CLIB deprecated
Trademarks
IAR Systems, IAR Embedded Workbench, IAR Connect, C-SPY, C-RUN, C-STAT, IAR Visual State, visualSTATE, IAR KickStart Kit, I-jet, I-jet Trace, I-scope, IAR Academy, IAR, and the logotype of IAR Systems are trademarks or registered trademarks owned by IAR Systems AB.
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.
Copyright © 1996-2018 IAR Systems AB.