Release NotesSLAA304V–June 2006–Revised April 2012

IAR Embedded Workbench KickStart

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

Literature # slac050ah.zip

Executable file name FET_R611exe

HIL.dll version 1.2.6.0

MSP430.dll version 3.2.3.15

1.1 Known Limitations

EEM State Storage IAR State Storage

Description Not implemented yet, work in progress.

Workaround None

EEM Sequencer IAR Sequencer

Description Not implemented yet, work in progress.

Workaround None

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 tocontinue the update process (IAR informs the user when the additional update step isrequired).

Workaround None

1SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN www.ti.com

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

Literature # slac050ag.zip

Executable file name FET_R610exe

HIL.dll version 1.2.6.0

MSP430.dll version 3.2.3.2

2.1 Known Limitations

EEM State Storage IAR State Storage

Description Not implemented yet, work in progress.

Workaround None

EEM Sequencer IAR Sequencer

Description Not implemented yet, work in progress.

Workaround None

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

CSPY Attach Attach to running target

Description The "Attach to running target" feature is not working if Timer_A Clock Control is enabled.

Workaround None

2 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 5.40.3 / WIN, FET 6.10 / WIN

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

3SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.40.2 / WIN, FET 6.09 / WIN www.ti.com

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

Literature # slac050af.zip

Executable file name FET_R609.exe

HIL.dll version 1.2.6.0

MSP430.dll version 3.2.2.0

3.1 Known Limitations

EEM State Storage IAR State Storage

Description Not implemented yet, work in progress.

Workaround None

EEM Sequencer IAR Sequencer

Description Not implemented yet, work in progress.

Workaround None

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

4 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 5.40.1 / WIN, FET 6.08 / WIN

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

Literature # slac050ae.zip

Executable file name FET_R608.exe

HIL.dll version 1.2.6.0

MSP430.dll version 3.2.2.0

4.1 Known Limitations

EEM State Storage IAR State Storage

Description Not implemented yet, work in progress.

Workaround None

EEM Sequencer IAR Sequencer

Description Not implemented yet, work in progress.

Workaround None

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

UIF Update Major version update with UIF hardware revision 1.3

Description When updating a UIF with hardware revision 1.3, a manual reconnect is necessary tocontinue the update process. IAR informs the user when the additional update step isrequired.

If the user confirms the reconnect dialog before the UIF has been enumeratedsuccessfully, the update fails.

Workaround Wait until CDC drivers are installed and UIF is enumerated.

5SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.40.1 / WIN, FET 6.08 / WIN www.ti.com

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

Description Use of multiple MSP-FET430UIF interfaces on one PC: There may be connection issuesif multiple USB interfaces are connected to the same USB hub.

Workaround Connect interfaces to different hubs or use only one interface.

Description It is not possible to reset the device using the Reset button on the toolbar while theapplication is running.

Workaround Stop application execution before using the Reset button.

6 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 5.20.4 / WIN, FET 6.04 / WIN

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

Literature # slac050ab.zip

Executable file name FET_R604.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.8.2

5.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

7SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.20.4 / WIN, FET 6.04 / WIN www.ti.com

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

Description Use of multiple MSP-FET430UIF interfaces on one PC: There may be connection issuesif multiple USB interfaces are connected to the same USB hub.

Workaround Connect interfaces to different hubs or use only one interface.

Description It is not possible to reset the device using the Reset button on the toolbar while theapplication is running.

Workaround Stop application execution before using the Reset button.

8 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 5.20.1 / WIN, FET 6.03 / WIN

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

Literature # slac050z.zip (6 December 2010)

Executable file name FET_R603.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.7.1

6.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

Description Usage of multiple MSP-FET430UIF interfaces on one PC: There may be connectionissues if multiple USB interfaces are connected to the same USB hub.

Workaround Connect interfaces to different hubs or use only one interface.

9SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.10.6 / WIN, FET 6.02 / WIN www.ti.com

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

Literature # slac050z.zip (15 September 2010)

Executable file name FET_R602.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.6.1

7.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

Description Usage of multiple MSP-FET430UIF interfaces on one PC: There may be connectionissues if multiple USB interfaces are connected to the same USB hub.

Workaround Connect interfaces to different hubs or use only one interface.

Description Single stepping stability issue: If 0x40 is moved to any CPU register the program counterwill be corrupted and single stepping will fail (device may reset itself).

Workaround Do not single step this instruction. Use instead the free run.

10 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 5.10.4 / WIN, FET 6.01 / WIN

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

Literature # slac050y.zip

Executable file name FET_R601.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.5.3

8.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

11SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 5.10.1 / WIN, FET 6.00 / WIN www.ti.com

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

Literature # slac050x.zip

Executable file name FET_R600.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.4.0

9.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

12 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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

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

Literature # slac050w.zip

Executable file name FET_R522.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.2.0

10.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

13SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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

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

Literature # slac050v.zip

Executable file name FET_R521.exe

HIL.dll version 1.2.6.0

MSP430.dll version 2.4.1.4

11.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.).

NOTE MSP430F5527 and MSP430F5418A are not supported by the current IAR version4.2.1.

14 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 4.20.4 / WIN, FET 5.20 / WIN

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

Literature # slac050u.zip

Executable file name FET_R520.exe

HIL.dll version 1.2.5.2

MSP430.dll version 2.4.0.2

12.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example manually set the PC to the next instruction, put thecorrect return address on the stack, etc.) .

15SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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 # slac050t.zip

Executable file name FET_R513.exe

HIL.dll version 1.2.5.0

MSP430.dll version 2.3.5.0

13.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example manually set the PC to the next instruction, put thecorrect return address on the stack, etc.) .

16 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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

14 Prior Version: IAR 4.11A / WIN, FET 5.12 / WIN

Literature # slac050s.zip

Executable file name FET_R512.exe

HIL.dll version 1.2.4.0

MSP430.dll version 2.3.4.2

14.1 Known Limitations

HEADERFILES2 Wrong base address used for RTC in msp430x54x.h and io430x54x.h

Description The register definitions for the RTC should start at 0x04A0 instead of 0x0480.

Workaround Edit used header file accordingly with correct addresses.

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY2 Known issues when debugging the MSP430F5xx family

Description There are possible debug scenarios where a code breakpoint being hit can corrupt theexpected program execution flow. These are specifically:

• Single stepping over an instruction that sets the CPUOFF bit in the CPU StatusRegister (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 mightbe corrupted due to debugger interaction).

• When single stepping over or running into a breakpoint that is set on an instructionthat 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.

Workaround 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 correctprogram execution flow (for example, manually set the PC to the next instruction, put thecorrect return address on the stack, etc.) .

17SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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 # slac050r.zip

Executable file name FET_R511.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.3.3.0

15.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhen a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

CSPY1 Integer values of C-type 'long' (32 bit) are displayed incorrectly in Watch windowfor MSP430X architecture

Description This affects 32-bit values that are held in two CPU registers; for example, a value of0x00123456 is stored in R14 and R15. The lower word of the 32-bit value is stored asR14 = 0x3456, and the higher word is stored as R15 = 0x0012. The C-Spy Watchwindow shows a value of 0x12003456. This is a problem with the Watch windowonly–the program code produces the correct results. It is recommended not to changethe dedicated 32-bit value via the Watch window, as this can cause unpredictablebehavior. This limitation is only valid when a device with the MSP430X architecture isthe target of a debug session.

Workaround None

18 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 4.09A / WIN, FET 5.10 / WIN

16 Prior Version: IAR 4.09A / WIN, FET 5.10 / WIN

Literature # slac050q.zip

Executable file name FET_R510.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.3.1.0

16.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE3 MSP430F2616 and MSP430F2617 devices are not correctly recognized bydebugger

Description When starting a debug session the Emulator shows a warning that "Chosen derivative(MSP430F2616) and actual hardware (MSP430F2619) do not match." for a projectconfigured for MSP430F2616 and "Chosen derivative (MSP430F2617) and actualhardware (MSP430F2618) do not match." for a project configured for MSP430F2617.

Workaround Message can be ignored. Click 'Yes' to continue download and start debug session.

EEM7 Advanced Trigger of type Register does not work properly for MSP430Xarchitecture

Description The configuration of an Advanced Trigger of type Register [for example, to observe theStack Pointer (SP) register value] does not show the expected behavior in the casewhere a device with the MSP430X architecture (for example, MSP430FG461x,MSP430F241x, and MSP430F261x) is the target of a debug session.

Workaround None

IDE1 Key bindings are deleted

Description If this version of the IAR Embedded Workbench (4.09A / WIN) is installed in the samesubdirectory where a previous version (for example, 3.42A / WIN) is already installed, allkey bindings [for example, debug hotkeys F5 (Go), F10 (Step Over), F11 (Step Into)] aredeleted in both versions.

Workaround Select in main menu Tools -> Options... -> Key Bindings and push the 'Reset All' buttonin each IAR installation.

19SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 4.09A / WIN, FET 5.10 / WIN www.ti.com

CSPY1 Integer values of C-type 'long' (32 bit) are displayed incorrectly in Watch windowfor MSP430X architecture

Description This affects 32-bit values that are held in two CPU registers; for example, a value of0x00123456 is stored in R14 and R15. The lower word of the 32-bit value is stored asR14 = 0x3456, and the higher word is stored as R15 = 0x0012. The C-Spy Watchwindow shows a value of 0x12003456. This is a problem with the Watch windowonly–the program code produces the correct results. It is recommended not to changethe dedicated 32-bit value via the Watch window, as this can cause unpredictablebehavior. This limitation is only valid in the case where a device with the MSP430Xarchitecture is the target of a debug session.

Workaround None

20 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 3.42A / WIN, FET 4.63 / WIN

17 Prior Version: IAR 3.42A / WIN, FET 4.63 / WIN

Literature # slac050p.zip

Executable file name FET_R463.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.1.10.1

17.1 Known Limitations

CONFIGFILES2 RAM size definition in lnk430f23x0.xcl linker command files

Description

• RAM segments definition in lnk430f2330.xcl should be 0x05FF instead of 0x02FF.

• RAM segments definition in lnk430f2350.xcl should be 0x09FF instead of 0x03FF.

Workaround Edit linker command files accordingly.

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

EEM6 Emulator Clock Control is not active by default

Description The "Emulator -> Clock Control" feature is not enabled by default when the C-Spydebugger starts.

Workaround Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OKbutton. Emulation clock control is now activated.

21SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 3.42A / WIN, FET 4.62 / WIN www.ti.com

18 Prior Version: IAR 3.42A / WIN, FET 4.62 / WIN

Literature # slac050o.zip

Executable file name FET_R462.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.1.10.0

18.1 Known Limitations

CONFIGFILES2 RAM size definition in lnk430f23x0.xcl linker command files

Description

• RAM segments definition in lnk430f2330.xcl should be 0x05FF instead of 0x02FF.

• RAM segments definition in lnk430f2350.xcl should be 0x09FF instead of 0x03FF.

Workaround Edit linker command files accordingly.

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM6 Emulator Clock Control is not active by default

Description The "Emulator -> Clock Control" feature is not enabled by default when the C-Spydebugger starts.

Workaround Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OKbutton. Emulation clock control is now activated.

22 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 3.42A / WIN, FET 4.61 / WIN

19 Prior Version: IAR 3.42A / WIN, FET 4.61 / WIN

Literature # slac050n.zip

Executable file name FET_R461.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.1.9.0

19.1 Known Limitations

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

Description

• Both files do not include any definitions for MSP430F161x devices.

• Both files contain wrong definitions for FE, FG, and FW devices (exclusiveMSP430FG461x devices).

• The file msp430.h includes io430x22x2.h instead of msp430x22x2.h forMSP430F22x2 devices.

Workaround Use device-specific header files rather than the generic header files or edit genericheader files accordingly.

CONFIGFILES1 RAM size definition in lnk430f223x.xcl linker command files

Description 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.

Workaround Edit linker command files accordingly.

CONFIGFILES2 RAM size definition in lnk430f23x0.xcl linker command files

Description

• RAM segments definition in lnk430f2330.xcl should be 0x05FF instead of 0x02FF.

• RAM segments definition in lnk430f2350.xcl should be 0x09FF instead of 0x03FF.

Workaround Edit linker command files accordingly.

JTAG1 JTAG security fuse blowing for MSP430F23x0 devices

Description It is not possible to burn the JTAG security fuse of MSP430F23x0 devices.

Workaround None

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

23SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Prior Version: IAR 3.42A / WIN, FET 4.61 / WIN www.ti.com

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM6 Emulator Clock Control is not active by default

Description The "Emulator -> Clock Control" feature is not enabled by default when the C-Spydebugger starts.

Workaround Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OKbutton. Emulation clock control is now activated.

24 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 3.42A / WIN, FET 4.60 / WIN

20 Prior Version: IAR 3.42A / WIN, FET 4.60 / WIN

Literature # slac050m.zip

Executable file name FET_R460.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.1.8.1

20.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE1 Support for MSP430F22x2 device derivatives

Description MSP430F22x2 devices are recognized by the Emulator driver as the correspondingMSP430F22x4 derivative. This results in an Emulator warning that the "Chosenderivative (MSP430F22x2) and actual hardware (MSP430F22x4) do not match".

Workaround The Emulator warning can be ignored. MSP430F22x2 and MSP430F22x4 derivativesare identical in terms of memory configuration. No issue is caused by ignoring theEmulator warning.

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM6 Emulator Clock Control is not active by default

Description The "Emulator -> Clock Control" feature is not enabled by default when the C-Spydebugger starts.

Workaround Open "Emulator -> Clock Control" dialog box and close it again by clicking on the OKbutton. Emulation clock control is now activated.

25SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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 # slac050l.zip

Executable file name FET_R453.exe

HIL.dll version 1.2.2.0

MSP430.dll version 2.1.8.0

21.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM5 Enhanced Emulation Module Advanced Trigger

Description Changing the Action in the Advanced Trigger dialog sometimes has no effect, especiallywith triggers of type Register.

Workaround Disable/enable the according trigger by unchecking/checking the checkbox in the globalBreakpoints window.

26 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

www.ti.com Prior Version: IAR 3.41A / WIN, FET 4.52 / WIN

22 Prior Version: IAR 3.41A / WIN, FET 4.52 / WIN

Literature # slac050k.zip

Executable file name FET_R452.exe

HIL.dll version 1.2.1.0

MSP430.dll version 2.1.7.0

22.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM1 Enhanced Emulation Module Breakpoint Combiner

Description It is not possible to combine an Advanced Trigger of type Register with any otherconfigured trigger.

Workaround None

EEM2 Enhanced Emulation Module Sequencer Control

Description Opening the Sequencer Control window prevents further debugging. The workbenchhangs up.

Workaround None

27SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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

23 Prior Version: IAR 3.40B / WIN, FET 4.51 / WIN

Literature # slac050j.zip

Executable file name FET_R451.exe

HIL.dll version 1.2.1.0

MSP430.dll version 2.1.6.0

23.1 Known Limitations

JTAG2 Attach to running target

Description The "Attach to running target" feature is not working 100% reliably, especially for Spy-Bi-Wire capable devices.

Workaround None

DEVICE2 Support for MSP430F11x1A device derivatives Revision J

Description Silicon revision J of MSP430F11x1A devices is not recognized correctly by the Emulatordriver. It is not possible to download and debug program code on this dedicated siliconrevision.

Workaround None

EEM1 Enhanced Emulation Module Breakpoint Combiner

Description It is not possible to combine an Advanced Trigger of type Register with any otherconfigured trigger.

Workaround None

EEM2 Enhanced Emulation Module Sequencer Control

Description Opening the Sequencer Control window prevents further debugging. The workbenchhangs up.

Workaround None

EEM3 Enhanced Emulation Module Clock Control

Description Any changes made in the Clock Control window have no effect and are discarded afterclicking the "OK" button.

Workaround None

EEM4 Breakpoints

Description Advanced Triggers of type Register where the specified register is any other CPUregister than the SP (Stack Pointer) have no effect.

Workaround None

28 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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

FLASH1 Debugger Flash Programming

Description It is not possible to link any code/data into Information Memory segments B, C, and D ofMSP430F2xx devices without erasing DCO calibration data in segment A.

Workaround None

29SLAA304V–June 2006–Revised April 2012 IAR Embedded Workbench KickStartSubmit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

Version Matrix: Known Limitations www.ti.com

24 Version Matrix: Known Limitations

Literature No. HE

AD

ER

FIL

ES

1

HE

AD

ER

FIL

ES

2

CO

NF

IGF

ILE

S1

CO

NF

IGF

ILE

S2

JTA

G1

JTA

G2

DE

VIC

E1

DE

VIC

E2

DE

VIC

E3

EE

M1

EE

M2

EE

M3

EE

M4

EE

M5

EE

M6

EE

M7

EE

MS

tate

Sto

rag

e

EE

MS

equ

ence

r

FL

AS

H1

IDE

1

CS

PY

Att

ach

CS

PY

1

CS

PY

2

UIF

Up

dat

e

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 IAR Embedded Workbench KickStart SLAA304V–June 2006–Revised April 2012Submit Documentation Feedback

Copyright © 2006–2012, Texas Instruments Incorporated

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 shouldobtain the latest relevant information before placing orders and should verify that such information is current and complete. All products aresold subject to TI’s 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 TI’s standardwarranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except wheremandated 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 andapplications using TI components. To minimize the risks associated with customer products and applications, customers should provideadequate 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. Informationpublished by TI regarding third-party products or services does not constitute a license from TI to use such products or services or awarranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectualproperty 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 accompaniedby all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptivebusiness practice. TI is not responsible or liable for such altered documentation. Information of third parties may be subject to additionalrestrictions.

Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids allexpress and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is notresponsible 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 reasonablybe expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifically governingsuch use. Buyers represent that they have all necessary expertise in the safety and regulatory ramifications of their applications, andacknowledge and agree that they are solely responsible for all legal, regulatory and safety-related requirements concerning their productsand any use of TI products in such safety-critical applications, notwithstanding any applications-related information or support that may beprovided by TI. Further, Buyers must fully indemnify TI and its representatives against any damages arising out of the use of TI products insuch safety-critical applications.

TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products arespecifically designated by TI as military-grade or "enhanced plastic." Only products designated by TI as military-grade meet militaryspecifications. Buyers acknowledge and agree that any such use of TI products which TI has not designated as military-grade is solely atthe 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 aredesignated by TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any non-designatedproducts 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 Applications

Audio www.ti.com/audio Automotive and Transportation www.ti.com/automotive

Amplifiers amplifier.ti.com Communications and Telecom www.ti.com/communications

Data Converters dataconverter.ti.com Computers and Peripherals www.ti.com/computers

DLP® Products www.dlp.com Consumer Electronics www.ti.com/consumer-apps

DSP dsp.ti.com Energy and Lighting www.ti.com/energy

Clocks and Timers www.ti.com/clocks Industrial www.ti.com/industrial

Interface interface.ti.com Medical www.ti.com/medical

Logic logic.ti.com Security www.ti.com/security

Power Mgmt power.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defense

Microcontrollers microcontroller.ti.com Video and Imaging www.ti.com/video

RFID www.ti-rfid.com

OMAP Mobile Processors www.ti.com/omap

Wireless Connectivity www.ti.com/wirelessconnectivity

TI E2E Community Home Page e2e.ti.com

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265Copyright © 2012, Texas Instruments Incorporated