Slaa 304 V

Release Notes
SLAA304V June 2006 Revised April 2012
IAR Embedded Workbench KickStart
Current Version: IAR 5.40.6 / WIN, FET 6.11 / WIN

Literature # Executable file name HIL.dll version MSP430.dll version slac050ah.zip FET_R611exe 1.2.6.0 3.2.3.15
1.1
Known Limitations
EEM State Storage IAR State Storage

Description Workaround
Not implemented yet, work in progress. None IAR Sequencer Not implemented yet, work in progress. None
EEM Sequencer
UIF Firmware Update Major version update with UIF hardware revision 1.3
Description
When updating an UIF with hardware revision 1.3, a manual reconnect is necessary to continue the update process (IAR informs the user when the additional update step is required). None
Workaround
SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Copyright 20062012, Texas Instruments Incorporated
Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN
www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050ag.zip FET_R610exe 1.2.6.0 3.2.3.2
2.1
Known Limitations

Not implemented yet, work in progress. None IAR Sequencer Not implemented yet, work in progress. None Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Attach to running target The "Attach to running target" feature is not working if Timer_A Clock Control is enabled. None
EEM Sequencer
JTAG2
Description
Workaround
CSPY Attach

www.ti.com
CSPY2
Description
Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases, it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.).
Workaround

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050af.zip FET_R609.exe 1.2.6.0 3.2.2.0
3.1
Known Limitations

Not implemented yet, work in progress. None IAR Sequencer Not implemented yet, work in progress. None Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases, it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.).
EEM Sequencer
JTAG2
Description
Workaround
CSPY2
Description
Workaround

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050ae.zip FET_R608.exe 1.2.6.0 3.2.2.0
4.1
Known Limitations

Not implemented yet, work in progress. None IAR Sequencer Not implemented yet, work in progress. None Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Major version update with UIF hardware revision 1.3 When updating a UIF with hardware revision 1.3, a manual reconnect is necessary to continue the update process. IAR informs the user when the additional update step is required. If the user confirms the reconnect dialog before the UIF has been enumerated successfully, the update fails.
EEM Sequencer
JTAG2
Description
Workaround
UIF Update
Description
Workaround
Wait until CDC drivers are installed and UIF is enumerated.

www.ti.com
CSPY2
Description
Workaround
Description
Use of multiple MSP-FET430UIF interfaces on one PC: There may be connection issues if multiple USB interfaces are connected to the same USB hub. Connect interfaces to different hubs or use only one interface. It is not possible to reset the device using the Reset button on the toolbar while the application is running. Stop application execution before using the Reset button.
Workaround Description
Workaround

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050ab.zip FET_R604.exe 1.2.6.0 2.4.8.2
5.1
Known Limitations
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None
JTAG2
Description
Workaround
EEM7
Description
Workaround

www.ti.com
CSPY2
Description
Workaround
Description
Use of multiple MSP-FET430UIF interfaces on one PC: There may be connection issues if multiple USB interfaces are connected to the same USB hub. Connect interfaces to different hubs or use only one interface. It is not possible to reset the device using the Reset button on the toolbar while the application is running. Stop application execution before using the Reset button.
Workaround

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050z.zip (6 December 2010) FET_R603.exe 1.2.6.0 2.4.7.1
6.1
Known Limitations
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases, it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.).
JTAG2
Description
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround
Description
Usage of multiple MSP-FET430UIF interfaces on one PC: There may be connection issues if multiple USB interfaces are connected to the same USB hub. Connect interfaces to different hubs or use only one interface.
Workaround

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050z.zip (15 September 2010) FET_R602.exe 1.2.6.0 2.4.6.1
7.1
Known Limitations
JTAG2
Description
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround
Description
Usage of multiple MSP-FET430UIF interfaces on one PC: There may be connection issues if multiple USB interfaces are connected to the same USB hub. Connect interfaces to different hubs or use only one interface. Single stepping stability issue: If 0x40 is moved to any CPU register the program counter will be corrupted and single stepping will fail (device may reset itself). Do not single step this instruction. Use instead the free run.
Workaround
10

www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050y.zip FET_R601.exe 1.2.6.0 2.4.5.3
8.1
Known Limitations
JTAG2
Description
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround

11
www.ti.com

Literature # Executable file name HIL.dll version MSP430.dll version slac050x.zip FET_R600.exe 1.2.6.0 2.4.4.0
9.1
Known Limitations
JTAG2
Description
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround
12

www.ti.com
Prior Version: IAR 4.21. / WIN, FET 5.21 / WIN
10

Literature # Executable file name HIL.dll version MSP430.dll version slac050w.zip FET_R522.exe 1.2.6.0 2.4.2.0
10.1 Known Limitations JTAG2

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.).
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround

13
www.ti.com
11

Literature # Executable file name HIL.dll version MSP430.dll version slac050v.zip FET_R521.exe 1.2.6.0 2.4.1.4

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.).
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround
NOTE
MSP430F5527 and MSP430F5418A are not supported by the current IAR version 4.2.1.
14

www.ti.com
12

Literature # Executable file name HIL.dll version MSP430.dll version slac050u.zip FET_R520.exe 1.2.5.2 2.4.0.2

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases it is possible to manually restore the CPU state to continue with a correct program execution flow (for example manually set the PC to the next instruction, put the correct return address on the stack, etc.) .
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround

15
Prior Version: IAR 4.11C / WIN, FET 5.13 / WIN
www.ti.com
13
Prior Version: IAR 4.11C / WIN, FET 5.13 / WIN

Literature # Executable file name HIL.dll version MSP430.dll version slac050t.zip FET_R513.exe 1.2.5.0 2.3.5.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases it is possible to manually restore the CPU state to continue with a correct program execution flow (for example manually set the PC to the next instruction, put the correct return address on the stack, etc.) .
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround
16

www.ti.com
Prior Version: IAR 4.11A / WIN, FET 5.12 / WIN
14

Literature # Executable file name HIL.dll version MSP430.dll version slac050s.zip FET_R512.exe 1.2.4.0 2.3.4.2
14.1 Known Limitations HEADERFILES2

Wrong base address used for RTC in msp430x54x.h and io430x54x.h The register definitions for the RTC should start at 0x04A0 instead of 0x0480. Edit used header file accordingly with correct addresses. Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Known issues when debugging the MSP430F5xx family There are possible debug scenarios where a code breakpoint being hit can corrupt the expected program execution flow. These are specifically: Single stepping over an instruction that sets the CPUOFF bit in the CPU Status Register (SR) (for example BIS #CPUOFF,SR). Single stepping while the DMA gets triggers to transfer data. Single stepping into an interrupt service routine (the return value on the stack might be corrupted due to debugger interaction). When single stepping over or running into a breakpoint that is set on an instruction that performs a 20-bit write back operation to memory the Program Counter (PC) might not point to the next instruction but to the address of the next instruction plus 2. Avoid setting breakpoints in one of the described scenarios. In some cases it is possible to manually restore the CPU state to continue with a correct program execution flow (for example, manually set the PC to the next instruction, put the correct return address on the stack, etc.) .
JTAG2
Description
Workaround
EEM7
Description
Workaround
CSPY2
Description
Workaround

17
Prior Version: IAR 4.010E / WIN, FET 5.11 / WIN
www.ti.com
15
Prior Version: IAR 4.010E / WIN, FET 5.11 / WIN

Literature # Executable file name HIL.dll version MSP430.dll version slac050r.zip FET_R511.exe 1.2.2.0 2.3.3.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case when a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Integer values of C-type 'long' (32 bit) are displayed incorrectly in Watch window for MSP430X architecture This affects 32-bit values that are held in two CPU registers; for example, a value of 0x00123456 is stored in R14 and R15. The lower word of the 32-bit value is stored as R14 = 0x3456, and the higher word is stored as R15 = 0x0012. The C-Spy Watch window shows a value of 0x12003456. This is a problem with the Watch window onlythe program code produces the correct results. It is recommended not to change the dedicated 32-bit value via the Watch window, as this can cause unpredictable behavior. This limitation is only valid when a device with the MSP430X architecture is the target of a debug session. None
Workaround
EEM7
Description
Workaround
CSPY1
Description
Workaround
18

www.ti.com
16

Literature # Executable file name HIL.dll version MSP430.dll version slac050q.zip FET_R510.exe 1.2.2.0 2.3.1.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None MSP430F2616 and MSP430F2617 devices are not correctly recognized by debugger When starting a debug session the Emulator shows a warning that "Chosen derivative (MSP430F2616) and actual hardware (MSP430F2619) do not match." for a project configured for MSP430F2616 and "Chosen derivative (MSP430F2617) and actual hardware (MSP430F2618) do not match." for a project configured for MSP430F2617. Message can be ignored. Click 'Yes' to continue download and start debug session. Advanced Trigger of type Register does not work properly for MSP430X architecture The configuration of an Advanced Trigger of type Register [for example, to observe the Stack Pointer (SP) register value] does not show the expected behavior in the case where a device with the MSP430X architecture (for example, MSP430FG461x, MSP430F241x, and MSP430F261x) is the target of a debug session. None Key bindings are deleted If this version of the IAR Embedded Workbench (4.09A / WIN) is installed in the same subdirectory where a previous version (for example, 3.42A / WIN) is already installed, all key bindings [for example, debug hotkeys F5 (Go), F10 (Step Over), F11 (Step Into)] are deleted in both versions. Select in main menu Tools -> Options... -> Key Bindings and push the 'Reset All' button in each IAR installation.
Workaround
DEVICE3
Description
Workaround
EEM7
Description
Workaround
IDE1
Description
Workaround

19
www.ti.com
CSPY1
Description
Integer values of C-type 'long' (32 bit) are displayed incorrectly in Watch window for MSP430X architecture This affects 32-bit values that are held in two CPU registers; for example, a value of 0x00123456 is stored in R14 and R15. The lower word of the 32-bit value is stored as R14 = 0x3456, and the higher word is stored as R15 = 0x0012. The C-Spy Watch window shows a value of 0x12003456. This is a problem with the Watch window onlythe program code produces the correct results. It is recommended not to change the dedicated 32-bit value via the Watch window, as this can cause unpredictable behavior. This limitation is only valid in the case where a device with the MSP430X architecture is the target of a debug session. None
Workaround
20

www.ti.com
17

Literature # Executable file name HIL.dll version MSP430.dll version slac050p.zip FET_R463.exe 1.2.2.0 2.1.10.1
17.1 Known Limitations CONFIGFILES2

Description
RAM size definition in lnk430f23x0.xcl linker command files

Workaround
RAM segments definition in lnk430f2330.xcl should be 0x05FF instead of 0x02FF. RAM segments definition in lnk430f2350.xcl should be 0x09FF instead of 0x03FF.
Edit linker command files accordingly. Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Emulator Clock Control is not active by default The "Emulator -> Clock Control" feature is not enabled by default when the C-Spy debugger starts. Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OK button. Emulation clock control is now activated.
JTAG2
Description
Workaround
EEM6
Description
Workaround

21
www.ti.com
18

Literature # Executable file name HIL.dll version MSP430.dll version slac050o.zip FET_R462.exe 1.2.2.0 2.1.10.0
18.1 Known Limitations CONFIGFILES2

Description
RAM size definition in lnk430f23x0.xcl linker command files

Workaround
Edit linker command files accordingly. Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Emulator Clock Control is not active by default The "Emulator -> Clock Control" feature is not enabled by default when the C-Spy debugger starts. Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OK button. Emulation clock control is now activated.
JTAG2
Description
Workaround
DEVICE2
Description
Workaround
EEM6
Description
Workaround
22

www.ti.com
19

Literature # Executable file name HIL.dll version MSP430.dll version slac050n.zip FET_R461.exe 1.2.2.0 2.1.9.0
19.1 Known Limitations HEADERFILES1

Description
Definitions in generic header files msp430.h and io430.h

Workaround
Both files do not include any definitions for MSP430F161x devices. Both files contain wrong definitions for FE, FG, and FW devices (exclusive MSP430FG461x devices). The file msp430.h includes io430x22x2.h instead of msp430x22x2.h for MSP430F22x2 devices.
Use device-specific header files rather than the generic header files or edit generic header files accordingly. RAM size definition in lnk430f223x.xcl linker command files A value of 0x02FF is specified for RAM segments (DATA16_I, DATA16_N, DATA16_N, CSTACK, HEAP), which corresponds to a RAM size of 256 bytes. Actually, MSP430F223x devices have 512 bytes of RAM, which results in a value of 0x03FF. Edit linker command files accordingly. RAM size definition in lnk430f23x0.xcl linker command files
CONFIGFILES1
Description
Workaround
CONFIGFILES2
Description

Workaround
Edit linker command files accordingly. JTAG security fuse blowing for MSP430F23x0 devices It is not possible to burn the JTAG security fuse of MSP430F23x0 devices. None Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None
JTAG1
JTAG2
Description
Workaround

23
www.ti.com
DEVICE2
Description
Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Emulator Clock Control is not active by default The "Emulator -> Clock Control" feature is not enabled by default when the C-Spy debugger starts. Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OK button. Emulation clock control is now activated.
Workaround
EEM6
Description
Workaround
24

www.ti.com
20

Literature # Executable file name HIL.dll version MSP430.dll version slac050m.zip FET_R460.exe 1.2.2.0 2.1.8.1

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Support for MSP430F22x2 device derivatives MSP430F22x2 devices are recognized by the Emulator driver as the corresponding MSP430F22x4 derivative. This results in an Emulator warning that the "Chosen derivative (MSP430F22x2) and actual hardware (MSP430F22x4) do not match". The Emulator warning can be ignored. MSP430F22x2 and MSP430F22x4 derivatives are identical in terms of memory configuration. No issue is caused by ignoring the Emulator warning. Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Emulator Clock Control is not active by default The "Emulator -> Clock Control" feature is not enabled by default when the C-Spy debugger starts. Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OK button. Emulation clock control is now activated.
Workaround
DEVICE1
Description
Workaround
DEVICE2
Description
Workaround
EEM6
Description
Workaround

25
Prior Version: IAR 3.41G / WIN, FET 4.53 / WIN
www.ti.com
21
Prior Version: IAR 3.41G / WIN, FET 4.53 / WIN

Literature # Executable file name HIL.dll version MSP430.dll version slac050l.zip FET_R453.exe 1.2.2.0 2.1.8.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Enhanced Emulation Module Advanced Trigger Changing the Action in the Advanced Trigger dialog sometimes has no effect, especially with triggers of type Register. Disable/enable the according trigger by unchecking/checking the checkbox in the global Breakpoints window.
Workaround
DEVICE2
Description
Workaround
EEM5
Description
Workaround
26

www.ti.com
22

Literature # Executable file name HIL.dll version MSP430.dll version slac050k.zip FET_R452.exe 1.2.1.0 2.1.7.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Enhanced Emulation Module Breakpoint Combiner It is not possible to combine an Advanced Trigger of type Register with any other configured trigger. None Enhanced Emulation Module Sequencer Control Opening the Sequencer Control window prevents further debugging. The workbench hangs up. None
Workaround
DEVICE2
Description
Workaround
EEM1
Description
Workaround
EEM2
Description
Workaround

27
Prior Version: IAR 3.40B / WIN, FET 4.51 / WIN
www.ti.com
23

Literature # Executable file name HIL.dll version MSP430.dll version slac050j.zip FET_R451.exe 1.2.1.0 2.1.6.0

Description
Attach to running target The "Attach to running target" feature is not working 100% reliably, especially for Spy-BiWire capable devices. None Support for MSP430F11x1A device derivatives Revision J Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulator driver. It is not possible to download and debug program code on this dedicated silicon revision. None Enhanced Emulation Module Breakpoint Combiner It is not possible to combine an Advanced Trigger of type Register with any other configured trigger. None Enhanced Emulation Module Sequencer Control Opening the Sequencer Control window prevents further debugging. The workbench hangs up. None Enhanced Emulation Module Clock Control Any changes made in the Clock Control window have no effect and are discarded after clicking the "OK" button. None Breakpoints Advanced Triggers of type Register where the specified register is any other CPU register than the SP (Stack Pointer) have no effect. None
Workaround
DEVICE2
Description
Workaround
EEM1
Description
Workaround
EEM2
Description
Workaround
EEM3
Description
Workaround
EEM4
Description
Workaround
28

www.ti.com
FLASH1
Description
Debugger Flash Programming It is not possible to link any code/data into Information Memory segments B, C, and D of MSP430F2xx devices without erasing DCO calibration data in segment A. None
Workaround

29
Version Matrix: Known Limitations
www.ti.com
24
Version Matrix: Known Limitations

EEM State Storage
HEADERFILES1
HEADERFILES2
EEM Sequencer
CONFIGFILES1
CONFIGFILES2
CSPY Attach
Literature No. slac050ah.zip slac050ag.zip slac050af.zip slac050ae.zip slac050z.zip slac050y.zip slac050x.zip slac050w.zip slac050v.zip slac050u.zip slac050t.zip slac050s.zip slac050r.zip slac050q.zip slac050p.zip slac050o.zip slac050n.zip slac050m.zip slac050l.zip slac050k.zip slac050j.zip
30

UIF Update
DEVICE1
DEVICE2
DEVICE3
FLASH1
CSPY1
CSPY2
JTAG1
JTAG2
EEM1
EEM2
EEM3
EEM4
EEM5
EEM6
EEM7
IDE1
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products are sold subject to TIs terms and conditions of sale supplied at the time of order acknowledgment. TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TIs standard warranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where mandated by government requirements, testing of all parameters of each product is not necessarily performed. TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using TI components. To minimize the risks associated with customer products and applications, customers should provide adequate design and operating safeguards. TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask work right, or other TI intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information published by TI regarding third-party products or services does not constitute a license from TI to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI. Reproduction of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for such altered documentation. Information of third parties may be subject to additional restrictions. Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. TI products are not authorized for use in safety-critical applications (such as life support) where a failure of the TI product would reasonably be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifically governing such use. Buyers represent that they have all necessary expertise in the safety and regulatory ramifications of their applications, and acknowledge and agree that they are solely responsible for all legal, regulatory and safety-related requirements concerning their products and any use of TI products in such safety-critical applications, notwithstanding any applications-related information or support that may be provided by TI. Further, Buyers must fully indemnify TI and its representatives against any damages arising out of the use of TI products in such safety-critical applications. TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products are specifically designated by TI as military-grade or "enhanced plastic." Only products designated by TI as military-grade meet military specifications. Buyers acknowledge and agree that any such use of TI products which TI has not designated as military-grade is solely at the Buyer's risk, and that they are solely responsible for compliance with all legal and regulatory requirements in connection with such use. TI products are neither designed nor intended for use in automotive applications or environments unless the specific TI products are designated by TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any non-designated products in automotive applications, TI will not be responsible for any failure to meet such requirements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions: Products Audio Amplifiers Data Converters DLP Products DSP Clocks and Timers Interface Logic Power Mgmt Microcontrollers RFID OMAP Mobile Processors Wireless Connectivity www.ti.com/audio amplifier.ti.com dataconverter.ti.com www.dlp.com dsp.ti.com www.ti.com/clocks interface.ti.com logic.ti.com power.ti.com microcontroller.ti.com www.ti-rfid.com www.ti.com/omap www.ti.com/wirelessconnectivity TI E2E Community Home Page e2e.ti.com Applications Automotive and Transportation www.ti.com/automotive Communications and Telecom www.ti.com/communications Computers and Peripherals Consumer Electronics Energy and Lighting Industrial Medical Security Space, Avionics and Defense Video and Imaging www.ti.com/computers www.ti.com/consumer-apps www.ti.com/energy www.ti.com/industrial www.ti.com/medical www.ti.com/security www.ti.com/space-avionics-defense www.ti.com/video
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265 Copyright 2012, Texas Instruments Incorporated

Slaa 304 V

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Slaa 304 V

Uploaded by

Copyright:

Available Formats

Release Notes

SLAA304V June 2006 Revised April 2012

IAR Embedded Workbench KickStart

Current Version: IAR 5.40.6 / WIN, FET 6.11 / WIN

EEM State Storage IAR State Storage

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN

Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN

EEM State Storage IAR State Storage

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.40.2 / WIN, FET 6.09 / WIN

Prior Version: IAR 5.40.2 / WIN, FET 6.09 / WIN

EEM State Storage IAR State Storage

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 5.40.1 / WIN, FET 6.08 / WIN

Prior Version: IAR 5.40.1 / WIN, FET 6.08 / WIN

EEM State Storage IAR State Storage

Wait until CDC drivers are installed and UIF is enumerated.

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.40.1 / WIN, FET 6.08 / WIN

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 5.20.4 / WIN, FET 6.04 / WIN

Prior Version: IAR 5.20.4 / WIN, FET 6.04 / WIN

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.20.4 / WIN, FET 6.04 / WIN

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 5.20.1 / WIN, FET 6.03 / WIN

Prior Version: IAR 5.20.1 / WIN, FET 6.03 / WIN

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.10.6 / WIN, FET 6.02 / WIN

Prior Version: IAR 5.10.6 / WIN, FET 6.02 / WIN

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 5.10.4 / WIN, FET 6.01 / WIN

Prior Version: IAR 5.10.4 / WIN, FET 6.01 / WIN

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 5.10.1 / WIN, FET 6.00 / WIN

Prior Version: IAR 5.10.1 / WIN, FET 6.00 / WIN

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 4.21. / WIN, FET 5.21 / WIN

Prior Version: IAR 4.21. / WIN, FET 5.21 / WIN

10.1 Known Limitations JTAG2

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

IAR Embedded Workbench KickStart

Prior Version: IAR 4.21. / WIN, FET 5.21 / WIN

Prior Version: IAR 4.21. / WIN, FET 5.21 / WIN

11.1 Known Limitations JTAG2

IAR Embedded Workbench KickStart

SLAA304V June 2006 Revised April 2012 Submit Documentation Feedback

Prior Version: IAR 4.20.4 / WIN, FET 5.20 / WIN