This service pack has been made to add support for the following new devices:
MSP430G2444, MSP430G2544
MSP430G2744, MSP430G2755
MSP430G2855, MSP430G2955
MSP430TCH5E

This service pack has been made to address the following:

• The compiler now inserts a NOP instruction between two instructions which might enable and disable interrupts, respectively, as required by the architecture on devices based on the MSP430X core.

• The assembler now detects and issues a warning when a NOP instruction is needed between two instructions which might enable and disable interrupts, respectively, as required by the architecture on devices based on the MSP430X core.

• Software breakpoints are now disabled in combination with LPMx.5 debugging

The following issues in the debugger have been corrected:

• EW23658: It is now possible to debug images with a size up to 16 Kbytes when using the Baseline edition.

• EW23650: The Debug Log window no longer warns about a missing read-only memory area when a FRAM device is used.

• State Storage is now only enabled if the device supports it, and it was explicitly enabled before closing the previous debug session.

• Emulated software breakpoints are now always enabled.

This service pack has been made to address the following:

• The assembler will now detect and issue a warning when a NOP instruction is needed between an EINT and a DINT instruction as required by the architecture on devices based on the CPUxv2 core. This change will automatically be enabled when the IDE is used, see the release notes on how to enable it on the command line.

• EW23601: It is now possible to debug images with a size up to 8 Kbytes when using a 430X device with the Kickstart edition.

• The file MSP430F67451.menu is now included in the product.

This service pack includes:

• EW23588: The CSTACK segment is now always placed in data16 memory (below 0xFFFF) also on devices with a RAM area above 0xFFFF.

• The compiler now adds a NOP instruction between a EINT and a DINT instruction as required by the architecture on devices based on the CPUxv2 core. This change will automatically be enabled when the IDE is used, see the release notes on how to enable it on the command line.

IAR Embedded Workbench for MSP430 version 5.51.1

The new version introduces a new License Management System (LMS). The new LMS includes new features like commuter licenses, automatic license activation and support for virtual servers. It is easier to administrate and a single installer concept enables easy transfer between all variants of IAR Embedded Workbench for a certain product by a license upgrade.

Important information
A new license key must be issued in order for you to be able to use the software. The process of issuing the new key is done automatically when the new version is installed, providing that your current license has a valid Support and Update Agreement associated with it in our license database.
The installation and licensing quick reference guide included with the product contains all the information you will need to convert your existing license key to work with the new license management system.

Important information for network licenses
This version of IAR Embedded Workbench uses version 2 of the IAR License Management System (LMS2), which requires an updated version of the IAR License Server (version 2.1x). The new license server cannot run on the same computer as the previous server (version 1.4x). In order to use network licenses for both an LMS1 version and an LMS2 version of your IAR Embedded Workbench product you must use different PCs as license servers, unless virtual servers are used.
If your LMS1 license server is using a dongle, you have a choice for your LMS2 server to either order an additional dongle (without additional cost) or to lock the license to the server PC. In this case, you must inform IAR Systems about which locking criteria you want to use. Send an e-mail to CustomerCare.SE@iar.com and let us know if you want to order an additional dongle or lock you network license to the server PC. This is mandatory and must be done before the network license can be activated on the LMS2 server.