CCS Manual
CCS Manual
CCS Manual
1 for MSP430
User's Guide
Preface ........................................................................................................................................ 6
1 Get Started Now! .................................................................................................................. 9
1.1 Software Installation ....................................................................................................... 10
1.2 Flashing the LED ........................................................................................................... 10
1.3 Important MSP430 Documents on the DVD and Web.............................................................. 11
2 Development Flow .............................................................................................................. 13
2.1 Using Code Composer Studio IDE (CCS) ............................................................................ 14
2.1.1 Creating a Project From Scratch ................................................................................ 14
2.1.2 Project Settings .................................................................................................... 15
2.1.3 Using Math Library for MSP430 (MSPMathlib) in CCS v5.5 and Newer................................... 15
2.1.4 Using an Existing CCE v2, CCE v3, CCE v3.1, CCS v4.x, or CCS v5.x Project ......................... 15
2.1.5 Stack Management ............................................................................................... 16
2.1.6 How to Generate Binary Format Files (TI-TXT and INTEL-HEX) ........................................... 16
2.2 Using the Integrated Debugger ........................................................................................... 16
2.2.1 Breakpoint Types .................................................................................................. 16
2.2.2 Using Breakpoints ................................................................................................. 19
3 EnergyTrace Technology.................................................................................................. 23
3.1 Introduction .................................................................................................................. 23
3.2 Energy Measurement ...................................................................................................... 23
3.3 Code Composer Studio Integration ................................................................................... 23
3.3.1 EnergyTrace Technology Settings .............................................................................. 24
3.3.2 Controlling EnergyTrace Technology ........................................................................... 28
3.3.3 EnergyTrace++ Mode ............................................................................................. 29
3.3.4 EnergyTrace Mode ................................................................................................ 34
3.3.5 Comparing Captured Data With Reference Data ............................................................. 37
3.4 EnergyTrace Technology FAQs .......................................................................................... 38
4 Memory Protection Unit and Intellectual Property Encapsulation ............................................. 42
4.1 Memory Protection Unit (MPU) ........................................................................................... 42
4.2 Intellectual Property Encapsulation (IPE) ............................................................................... 43
4.2.1 IPE Debug Settings ............................................................................................... 44
A Frequently Asked Questions ................................................................................................ 46
A.1 Hardware .................................................................................................................... 47
A.2 Program Development (Assembler, C-Compiler, Linker, IDE) ....................................................... 47
A.3 Debugging ................................................................................................................... 48
B Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS .............................................................. 52
B.1 Interrupt Vector Definition ................................................................................................. 53
B.2 Intrinsic Functions .......................................................................................................... 53
B.3 Data and Function Placement ............................................................................................ 53
B.3.1 Data Placement at an Absolute Location ...................................................................... 53
B.3.2 Data Placement Into Named Segments ........................................................................ 54
B.3.3 Function Placement Into Named Segments ................................................................... 54
B.4 C Calling Conventions ..................................................................................................... 55
B.5 Other Differences........................................................................................................... 55
B.5.1 Initializing Static and Global Variables ......................................................................... 55
List of Figures
2-1. Breakpoints.................................................................................................................. 19
2-2. Breakpoint Properties ...................................................................................................... 20
3-1. Pulse Density and Current Flow .......................................................................................... 23
3-2. EnergyTrace Button in the Toolbar Menu ............................................................................... 24
3-3. Exit EnergyTrace Mode ................................................................................................... 24
3-4. EnergyTrace Technology Preferences................................................................................ 25
3-5. Project Properties .......................................................................................................... 26
3-6. Debug Properties ........................................................................................................... 27
3-7. Battery Selection ........................................................................................................... 28
3-8. Custom Battery Type ...................................................................................................... 28
3-9. Target Connection.......................................................................................................... 28
3-10. EnergyTrace Technology Control Bar ................................................................................ 29
3-11. Debug Session With EnergyTrace++ Graphs .......................................................................... 30
3-12. Profile Window .............................................................................................................. 31
3-13. States Window .............................................................................................................. 32
3-14. Power Window .............................................................................................................. 33
3-15. Energy Window ............................................................................................................. 33
3-16. Debug Session With EnergyTrace Graphs ............................................................................. 34
3-17. EnergyTrace Profile Window ............................................................................................. 35
3-18. Zoom Into Power Window ................................................................................................. 35
3-19. Zoom Into Energy Window ................................................................................................ 36
3-20. Energy Profile of the Same Program in Resume (Yellow Line) and Free Run (Green Line) .................... 36
3-21. Comparing Profiles in EnergyTrace++ Mode ........................................................................... 37
3-22. Comparing Profiles in EnergyTrace Mode .............................................................................. 38
4-1. MPU Configuration Dialog ................................................................................................ 42
4-2. IPE Configuration Dialog .................................................................................................. 43
4-3. IPE Debug Settings ........................................................................................................ 44
F-1. MSP430L092 Modes....................................................................................................... 76
F-2. MSP430L092 in C092 Emulation Mode ................................................................................. 77
F-3. MSP430C092 Password Access ......................................................................................... 78
F-4. Allow Access to BSL ....................................................................................................... 79
F-5. MSP430 Password Access ............................................................................................... 80
F-6. Enable Ultra-Low-Power Debug Mode .................................................................................. 82
List of Tables
1-1. System Requirements ..................................................................................................... 10
2-1. Device Architecture, Breakpoints, and Other Emulation Features ................................................... 17
3-1. Availability of EnergyTrace and EnergyTrace++ Modes .............................................................. 24
3-2. EnergyTrace Technology Control Bar Icons ......................................................................... 29
CAUTION
This is an example of a caution statement.
A caution statement describes a situation that could potentially damage your
software or equipment.
WARNING
This is an example of a warning statement.
A warning statement describes a situation that could potentially
cause harm to you.
The information in a caution or a warning is provided for your protection. Read each caution and warning
carefully.
Texas Instruments, Code Composer Studio, MSP430, EnergyTrace are trademarks of Texas Instruments.
IAR Embedded Workbench is a registered trademark of IAR Systems.
ThinkPad is a registered trademark of Lenovo.
Microsoft, Windows, Windows Vista, Windows 7 are registered trademarks of Microsoft Corporation.
All other trademarks are the property of their respective owners.
This chapter provides instructions on installing the software, and shows how to run the demonstration
programs.
NOTE: The legacy MSP-FET430PIF (parallel port emulator) is not supported by this version of CCS.
NOTE: Fully extract the zip archive (setup_CCS_x_x_x.zip) before running setup_CCS_x.x.x.x.exe.
NOTE: The predefined examples work with most MSP430 boards. Specific examples are
automatically selected for MSP430G221x, MSP430L092, and MSP430FR59xx devices.
Certain MSP430F4xx boards use Port P5.0 for the LED connection, which must be changed
manually in the code.
7. To compile the code and download the application to the target device, click Run Debug (F11).
CAUTION
Never disconnect the JTAG or emulator USB cable during an active debug
session. Always terminate a running debug session properly (by clicking on the
"Terminate" icon) before disconnecting the target device.
8. To start the application, click Run Resume (F8) or click the Play button on the toolbar.
See FAQ Debugging #1 if the CCS debugger is unable to communicate with the device.
Congratulations, you have just built and tested an MSP430 application!
Development Flow
This chapter describes how to use Code Composer Studio IDE (CCS) to develop application software and
how to debug that software.
CAUTION
Never disconnect the JTAG or emulator USB cable during an active debug
session. Always terminate a running debug session properly (by clicking on the
"Terminate" icon) before disconnecting the target device.
2.1.3 Using Math Library for MSP430 (MSPMathlib) in CCS v5.5 and Newer
TI's MSPMathlib is part of CCSv5.5 and newer releases. This optimized library provides up to 26x better
performance in applications that use floating point scalar math. For details, see the MSPMathlib web page
(www.ti.com/tool/mspmathlib).
MSPMathlib is active by default in CCSv5.5+ for all new projects on all supported devices. For imported
projects, it is used only if the project already uses MSPMathlib or if it has been manually enabled.
To disable MSPMathlib: Remove libmath.a under Project Properties Build MSP430 Linker
File Search Path in the "Include library file or command file as input (--library, -l)" field.
To enable MSPMathlib: Add libmath.a under Project Properties Build MSP430 Linker File
Search Path in the "Include library file or command file as input (--library, -l)" field. Important: Put
libmath.a before other libraries that may be listed here.
2.1.4 Using an Existing CCE v2, CCE v3, CCE v3.1, CCS v4.x, or CCS v5.x Project
CCS v6.1 supports the conversion of workspaces and projects created in version CCE v2, v3, v3.1 and
CCS v4.x, CCS v5.x to the CCS v6.1 format (File Import General Existing Projects into
Workspace Next). Browse to legacy CCE or CCS workspace that contains the project to be imported.
The Import Wizard lists all of the projects in the given workspace. Specific Projects can then be selected
and converted. CCEv2 and CCEv3 projects may require manual changes to the target configuration file
(*.ccxml) after import.
CCS may return a warning that an imported project was built with another version of Code Generation
Tools (CGT) depending on the previous CGT version.
While the support for assembly projects has not changed, the header files for C code have been modified
slightly to improve compatibility with the IAR Embedded Workbench IDE (interrupt vector definitions). The
definitions used in CCE 2.x are still given but have been commented out in all header files. To support
CCE 2.x C code, remove the "//" in front of the #define statements that are located at the end of each .h
file in the section "Interrupt Vectors".
NOTE: A software breakpoint replaces the instruction at the breakpoint address with a call to
interrupt the code execution. Therefore, there is a small delay when setting a software
breakpoint. In addition, the use of software breakpoints always requires proper termination of
each debug session; otherwise, the application may not be operational stand-alone, because
the application on the device would still contain the software breakpoint instructions.
Both address (code) and data (value) breakpoints are supported. Data breakpoints and range breakpoints
each require two MSP430 hardware breakpoints.
(1)
The 2-wire JTAG debug interface is also referred to as Spy-Bi-Wire (SBW) interface. This interface is supported only by the USB
emulators (eZ430-xxxx, eZ-FET, and MSP-FET430UIF USB JTAG emulator) and the MSP-GANG430 production programming tool.
(2)
Support is limited to Spy-Bi-Wire (SBW) on MSP-FET430UIF. No limitations on MSP-FET.
Table 2-1. Device Architecture, Breakpoints, and Other Emulation Features (continued)
Break- Range LPMx.5
MSP430 4-Wire 2-Wire Clock State Trace
Device points Break- Debugging
Architecture JTAG JTAG (1) Control Sequencer Buffer
(N) points Support
MSP430F461x1 MSP430X X 8 X X X X
MSP430F47x MSP430 X 2 X
MSP430FG47x MSP430 X 2 X
MSP430F47x3 MSP430 X 2 X
MSP430F47x4 MSP430 X 2 X
MSP430F471xx MSP430X X 8 X X X X
MSP430F51x1 MSP430Xv2 X X 3 X X
MSP430F51x2 MSP430Xv2 X X 3 X X
MSP430F52xx MSP430Xv2 X X 3 X X
MSP430F530x MSP430Xv2 X X 3 X X
MSP430F5310 MSP430Xv2 X X 3 X X
MSP430F532x MSP430Xv2 X X 8 X X X X
MSP430F533x MSP430Xv2 X X 8 X X X X
MSP430F534x MSP430Xv2 X X 8 X X X X
MSP430F54xx MSP430Xv2 X X 8 X X X X
MSP430F54xxA MSP430Xv2 X X 8 X X X X
MSP430SL54xxA MSP430Xv2 X X 8 X X X X
MSP430F550x MSP430Xv2 X X 3 X X
MSP430F5510 MSP430Xv2 X X 3 X X
MSP430F552x MSP430Xv2 X X 8 X X X X
MSP430F535x MSP430Xv2 X X 8 X X X X
MSP430F563x MSP430Xv2 X X 8 X X X X
MSP430F565x MSP430Xv2 X X 8 X X X X X(2)
MSP430FR57xx MSP430Xv2 X X 3 X X X
MSP430FR59xx MSP430Xv2 X X 3 X X X
MSP430F643x MSP430Xv2 X X 8 X X X X
MSP430F645x MSP430Xv2 X X 8 X X X X X(2)
MSP430F665x MSP430Xv2 X X 8 X X X X X(2)
MSP430F663x MSP430Xv2 X X 8 X X X X
MSP430F67xx MSP430Xv2 X X 3 X X X(2)
MSP430F67xx1 MSP430Xv2 X X 3 X X X(2)
MSP430F67xxA MSP430Xv2 X X 3 X X X(2)
MSP430F67xx1A MSP430Xv2 X X 3 X X X(2)
MSP430FG642x MSP430Xv2 X X 8 X X X X X(2)
MSP430FG662x MSP430Xv2 X X 8 X X X X X(2)
MSP430FR203x MSP430Xv2 X X 3 X X
MSP430FR41xx MSP430Xv2 X X 3 X X
MSP430FR58xx MSP430Xv2 X X 3 X X X
MSP430FR68xx MSP430Xv2 X X 3 X X X
MSP430FR69xx MSP430Xv2 X X 3 X X X
MSP430i20xx MSP430 X X 2 X
MSP430L092 MSP430Xv2 X 2 X
MSP430TCH5E MSP430 X X 2 X
RF430FRL15xH MSP430Xv2 X X 2 X
NOTE: Not all options are available on every MSP430 derivative (see Table 2-1). Therefore, the
number of predefined breakpoint types in the breakpoint menu varies depending on the
selected device.
For more information on advanced debugging with CCS, see the application report Advanced Debugging
Using the Enhanced Emulation Module (EEM) With CCS Version 4 (SLAA393).
EnergyTrace Technology
3.1 Introduction
EnergyTrace Technology is an energy-based code analysis tool that measures and displays the
applications energy profile and helps to optimize it for ultra-low power consumption.
MSP430 devices with built-in EnergyTrace+[CPU State]+[Peripheral States] (or in short
EnergyTrace++) technology allow real-time monitoring of many internal device states while user
program code executes. EnergyTrace++ technology is supported on selected MSP430 devices and
debuggers.
EnergyTrace mode (without the "++") is the base of EnergyTrace Technology and enables analog
energy measurement to determine the energy consumption of an application but does not correlate it to
internal device information. The EnergyTrace mode is available for all MSP430 devices with selected
debuggers, including CCS.
The benefit of sampling continuously is evident: even the shortest device activity that consumes energy
contributes to the overall recorded energy. No shunt-based measurement system can achieve this.
During a debugging session, the EnergyTrace and EnergyTrace++ modes are available, depending on the
supported hardware features on the target device. Only EnergyTrace mode is available with stand-alone
running applications (see Table 3-1).
3. Click the start trace collection button ( ) to start the EnergyTrace Technology measurement.
4. Click the stop trace collection button ( ) to stop the EnergyTrace Technology measurement.
5. Refer to Section 3.3.4 for more details.
To exit this mode, click the in the EnergyTrace Technology window (see Figure 3-3).
Enable Auto-Launch on target connect: check this box to enable the EnergyTrace modes when
entering a debug session.
Two capture modes are supported:
The full-featured EnergyTrace+[CPU State]+[Peripheral States] mode that delivers real-time
device state information together with energy measurement data
The EnergyTrace mode that delivers only energy measurement data
Use the radio button to select the mode to enable when a debug session is launched. If an
MSP430 device does not support device state capturing, the selection is ignored and Code
Composer Studio starts in the EnergyTrace mode.
While a debug session is active, click the icon in the Profile window to switch between the modes.
To use the EnergyTrace+[CPU State]+[Peripheral States] mode to capture real-time device state
information while an application is executing, the default Debug Properties of the project must also be
modified. Right click on the active project in the Project Explorer and click on Properties (see Figure 3-5).
In the Debug section, enable the Enable Ultra Low Power debug / Debug LPMx.5 option in the Low
Power Mode Settings (see Figure 3-6). If this option is not enabled, the EnergyTrace+[CPU
State]+[Peripheral States] mode cannot capture data from the device.
NOTE: If the EnergyTrace Technology windows are not opened when a debug session starts, verify
the following items:
Does the hardware (debugger and device) support EnergyTrace Technology? To
determine if your selected device supports EnergyTrace technology, refer to the device-
specific data sheet, the MSP430 Hardware Tools Users Guide (SLAU278), or the user
guide that came with the evaluation board.
Is EnergyTrace Technology globally enabled in Window Preferences Code
Composer Studio Advanced Tools EnergyTrace Technology?
Is the "Enable Ultra Low Power debug / Debug LPMx.5" option enabled in Project
Properties Debug Low Power Mode Settings (required only when selecting
EnergyTrace mode)?
Battery Selection (see Figure 3-7): The window is used to select one of the available standard
batteries or define a customized battery. The EnergyTrace will use the battery characteristics to
calculate the estimated selected battery lifetime for the current application depending on the measured
current consumption. Availabe standard batteries are CR2032, 2xAAA or 2xAA.
A custom battery can also be selected, and its characteristics can be entered (see Figure 3-8).
Cell voltage (V)
Cell capacity (mAh)
Peak current - continuous (mA)
Peak current - pulse (mA)
Target lifetime (days)
Target Connection (see Figure 3-9): The menu is used to select which debug probe is used for
EnergyTrace measurement. The voltage can be also adjusted.
The Profile window (see Figure 3-12) is the control interface for EnergyTrace++. It can be used to set the
capturing time or to save the captured data for later reference. The Profile window also displays a
compressed view of the captured data and allows comparison with previous data.
The Profile window enables a quick overview of the resource use of the profiled application. The
resources are split into three categories:
CPU: Shows information about program execution
Low Power Mode: Shows a summary of low-power mode use. Valid low-power modes are LPM0,
LPM1, LPM2, LPM3, LPM4, LPM3.5, and LPM4.5. If the low-power mode cannot be properly
determined, a line labeled as <Undetermined> is displayed to indicate the time spent in that mode.
Active Mode: Shows which functions have been executed during active mode. Functions in the run-
time library are listed separately under the _RTS_ subcategory. If the device supports IP
Encapsulation, a line labeled as <Protected> is displayed to indicate the time executing out of IP
encapsulated memory.
Peripherals: Shows relative on time of the device peripherals
System Clocks: Shows relative on time of the system clocks
The States window (see Figure 3-13) shows the real-time trace of the target microcontroller's internal
states during the captured session. State information includes the Power Modes, on and off state of
peripheral modules and the state of the system clocks.
Figure 3-13 shows a device wakeup from low-power mode LPM2 to Active Mode, with the FRAM memory
enabled during the active period. It can be clearly seen that the device high-speed clocks MCLK and
SMCLK, as well as the MODOSC, are only active while the device is in active mode. The States window
allows a direct verification of whether or not the application exhibits the expected behavior; for example,
that a peripheral is disabled after a certain activity.
The Power window (see Figure 3-14) shows the dynamic power consumption of the target over time. The
current profile is plotted in light blue color, while a previously recorded profile that has been reloaded for
comparison is plotted in yellow color.
The Energy window (see Figure 3-15) shows the accumulated energy consumption of the target over
time. The current profile is plotted in light blue color, while a previously recorded profile that has been
reloaded for comparison is plotted in yellow color.
NOTE: During the capture of the internal states, the target microcontroller is constantly accessed by
the JTAG or Spy-Bi-Wire debug logic. These debug accesses consume energy; therefore, no
absolute power numbers are shown on the Power and Energy graph vertical axis. To see
absolute power numbers of the application, TI recommends using the EnergyTrace mode in
combination with the Free Run option. In this mode, the debug logic of the target
microcontroller is not accessed while measuring energy consumption.
In the EnergyTrace mode, the Profile window shows statistical data about the application that has been
profiled (see Figure 3-17). The following parameters are shown:
Captured time
Total energy consumed by the application (in mJ)
Minimum, mean, and maximum power (in mW)
Mean voltage (in V)
Minimum, mean, and maximum current (in mA)
Estimated life time of the selected battery (in days) for the captured energy profile
NOTE: The formula to calculate the battery life time assumes an ideal 3-V battery and does not
account for temperature, aging, peak current, and other factors that could negatively affect
battery capacity. It should also be noted that changing the target voltage (for example, from
3.6 V to 3 V) might cause the analog circuitry to behave differently and operate in a more or
less efficient state, hence reducing or increasing energy consumption. The value shown in
the Profile window cannot substitute measurements on real hardware.
The Power window (see Figure 3-18) shows the dynamic power consumption of the target over time. The
current profile is plotted in light blue color, while a previously recorded profile that has been reloaded for
comparison is plotted in yellow color.
The Energy window (see Figure 3-19) shows the accumulated energy consumption of the target over
time. The current profile is plotted in light blue color, while a previously recorded profile that has been
reloaded for comparison is plotted in yellow color.
NOTE: During program execution through the debugger's view Resume button, the target
microcontroller is constantly accessed by the JTAG or Spy-Bi-Wire protocol to detect when a
breakpoint has been hit. Inevitably, these debug accesses consume energy in the target
domain and change the result shown in both Energy and Power graphs. To see the absolute
power consumption of an application, TI recommends using the Free Run mode. In Free
Run mode, the debug logic of the target microcontroller is not accessed. See Figure 3-20 for
an example of the effect of energy consumption coming from debug accesses. The yellow
profile was recorded in Resume mode, and the green profile was recorded in Free Run
mode.
Figure 3-20. Energy Profile of the Same Program in Resume (Yellow Line) and Free Run (Green Line)
In the EnergyTrace mode, no States information is available to generate an exhaustive report. However,
the overall energy consumed during the measurement is compared and, with it, the Min, Mean, and Max
values of power and current. Parameters that have become better are shown with a green bar, and
parameters that have become worse are shown with a red bar (see Figure 3-22).
The delta bars are drawn linearly from 0% to 50%. Deltas larger than 50% do not result in a larger delta
bar.
Q: I have a code that repeatedly calls functions that have the same size. I would expect the
function profile to show an equal distribution of the run time. In reality, I see some functions
having slightly more run time than expected, and some functions slightly less.
A: During program counter trace, various factors affect the number of times a function is detected by the
profiler over time. The microcontroller code could benefit from the internal cache, thus executing some
functions faster than others. Another influencing factor is memory wait states and CPU pipeline stalls,
which add time variance to the code execution. An outside factor is the sampling frequency of the
debugger itself, which normally runs asynchronous to the microcontroller's code execution speed, but in
some cases shows overlapping behavior, which also results in an unequal function run time distribution.
Q: My power mode profile sometimes shows short periods of power modes that I haven't used
anywhere in my code. For example, I'm expecting a transition from active mode to LPM3, but I see
a LPM2 during the transition.
A: When capturing in EnergyTrace++ mode, digital information is continuously collected from the target
device. One piece of this information is the power mode control signals. Activation of low-power modes
requires stepping through a number of intermediate states. Usually this happens too quickly to be
captured by the trace function, but sometimes intermediate states can be captured and are displayed for a
short period of time as valid low-power modes.
Q: My profile sometimes includes an <Undetermined> low-power mode, and there are gaps in the
States graph Power Mode section. Where does the <Undetermined> low-power mode originate
from?
A: During transitions from active mode to low-power mode, internal device clocks are switched off, and
occasionally the state information is not updated completely. This state is displayed as <Undetermined> in
the Profile window, and the States graph shows a gap during the time that the <Undetermined> low-power
mode persists. The <Undetermined> state is an indication that your application has entered a low-power
mode, but which mode cannot be accurately determined. If your application is frequently entering low-
power modes, the <Undetermined> state will probably be shown more often than if your application only
rarely uses low-power modes.
Q: When capturing in EnergyTrace mode, the min and max values for power and current show
deviation, even though my program is the same. I would expect absolutely the same values.
A: The energy measurement method used on the hardware counts dc-dc charge pulses over time. Energy
and power are calculated from the energy over time. Due to statistical sampling effects and charge and
discharge effects of the output voltage buffer capacitors, it is possible that minimum and maximum values
of currents vary by some percent, even though the program is identical. The captured energy, however,
should be almost equal (in the given accuracy range).
Q: What are the influencing factors for the accuracy of the energy measurement?
A: The energy measurement circuit is directly supplied from the USB bus voltage, and thus it is sensitive
to USB bus voltage variations. During calibration, the energy equivalent of a single dc-dc charge pulse is
defined, and this energy equivalent depends on the USB voltage level. To ensure a good repeatability and
accuracy, power the debugger directly from an active USB port, and avoid using bus-powered hubs and
long USB cables that can lead to voltage drops, especially when other consumers are connected to the
USB hub. Furthermore the LDO and resistors used for reference voltage generation and those in the
calibration circuit come with a certain tolerance and ppm rate over temperature, which also influences
accuracy of the energy measurement.
Q: I am trying to capture in EnergyTrace++ mode or EnergyTrace mode with a MSP430 device that
is externally powered, but there is no data shown in the Profile, Energy, Power and States window.
A: Both EnergyTrace++ mode and EnergyTrace mode require the target to be supplied from the
debugger. No data can be captured when the target microcontroller is externally powered.
Q: I cannot measure LPM currents when I am capturing in EnergyTrace++ mode. I am expecting a
few microamps but measure more than 150 A.
A: Reading digital data from the target microcontroller consumes energy in the JTAG domain of the
microcontroller. Hence, an average current of approximately 150 A is measured when connecting an
ampere meter to the device power supply pins. If you want to eliminate energy consumption through
debug communication, switch to EnergyTrace mode, and let the target microcontroller execute in Free
Run mode.
Q: My LPM currents seem to be wrong. I am expecting a few microamps, but measure more, even
in Free Run mode or when letting the device execute without debug control from an independent
power supply.
A: The most likely cause of this extra current is improper GPIO termination, as floating pins can lead to
extra current flow. Also check the JTAG pins again, especially when the debugger is still connected (but
idle), as the debugger output signal levels in idle state might not match how the JTAG pins have been
configured by the application code. This could also lead to extra current flow.
Q: When I start the EnergyTrace++ windows through View Other MSP430-EnergyTrace before
launching the debug session, data capture sometimes does not start.
A: Enable EnergyTrace through Window Preferences Code Composer Studio Advanced
Tools EnergyTrace Technology. When launching a debug session, the EnergyTrace++ windows
automatically open, and data capture starts when the device executes. If you accidentally close all
EnergyTrace++ windows during a debug session, you can reopen them through View Other
MSP430-EnergyTrace.
42 Memory Protection Unit and Intellectual Property Encapsulation SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Intellectual Property Encapsulation (IPE)
Figure 4-1 shows the MPU Configuration Dialog of CCS that is available for FRAM devices that have the
MPU feature. It can be accessed by selecting the menu Project Properties General MSP430
MPU. It allows enabling or disabling of the MPU and choosing between an automatic and manual
configuration mode. For the automatic configuration, the compiler tool chain generates two memory
segments(read-write memory and executable memory). The segment borders of these two segments and
their respective access bits are placed into the according control registers during device startup. The
automatic mode will also set the bit for read access of the MPU Info Memory segment. The MPUSEGxVS
bit, which selects if a PUC must be executed on illegal access to a segment, is also set by default for each
of the segments.
As shown in Figure 4-1, the MPU dialog also allows for a complete manual configuration of the Memory
Protected Area by the user. As the beginning of Segment 1 is fixed to the start address of FRAM memory
and the end of Segment 3 is fixed to the end address of FRAM memory, only the start and end addresses
of Segment 2 need to be adjusted. As these addresses are equal to the end address and start addresses
of Segment 1 and Segment 3 respectively, these are adjusted automatically by the GUI. The memory and
its associated access rights can be configured completely independently in the manual configuration. It is
therefore also the users responsibility to place the according code and data segments into the correct
memory locations. Additional configuration of the linking process may be necessary to achieve the correct
placement of code and data in the desired memory locations.
Figure 4-2 shows the Code Composer Studio dialog for configuration of IPE memory, which is accessible
through the menu Project Properties General MSP430 IPE. The IPE dialog also provides
selections for manual and automatic configuration. In the automatic mode, a memory segment ".ipe" is
generated by the compiler tool chain and placed in the output file. Placing a variable into this section can
be performed directly from the source code:
#pragma DATA_SECTION(primeNumbers, ".ipe")
const unsigned int primeNumbers[5] = {2, 3, 5, 7, 11};
SLAU157AH May 2005 Revised March 2015 Memory Protection Unit and Intellectual Property Encapsulation 43
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Intellectual Property Encapsulation (IPE) www.ti.com
For a more detailed description on how to allocate space for certain code or data symbols inside sections,
refer to the MSP430 Optimizing C/C++ Compiler User's Guide (SLAU132).
In the Manual IPE mode, the user can configure the IPE segment borders and the control settings.
Consequently, additional configuration of the compiler or linker stage may also necessary to achieve the
correct placement of code and data in memory. To prevent the IPE from being modified, place the section
".ipestruct" inside the IP encapsulated memory area. This section contains the section borders and control
settings that are used to initialize the IPE related registers during device startup.
44 Memory Protection Unit and Intellectual Property Encapsulation SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Intellectual Property Encapsulation (IPE)
SLAU157AH May 2005 Revised March 2015 Memory Protection Unit and Intellectual Property Encapsulation 45
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Appendix A
SLAU157AH May 2005 Revised March 2015
This appendix presents solutions to frequently asked questions regarding hardware, program development
and debugging tools.
A.1 Hardware........................................................................................................... 47
A.2 Program Development (Assembler, C-Compiler, Linker, IDE) ................................... 47
A.3 Debugging......................................................................................................... 48
A.1 Hardware
For a complete list of hardware related FAQs, see the MSP430 Hardware Tools User's Guide (SLAU278).
1. A common MSP430 "mistake" is to fail to disable the watchdog mechanism. The watchdog is
enabled by default, and it resets the device if not disabled or properly managed by the application. Use
WDTCL = WDTPW + WDTHOLD; to explicitly disable the Watchdog. This statement is best placed in the
_system_pre_init() function that is executed prior to main(). If the Watchdog timer is not disabled, and
the Watchdog triggers and resets the device during CSTARTUP, the source screen goes blank, as
the debugger is not able to locate the source code for CSTARTUP. Be aware that CSTARTUP can
take a significant amount of time to execute if a large number of initialized global variables are used.
int _system_pre_init(void)
{
/* Insert your low-level initializations here */
WDTCTL = WDTPW + WDTHOLD; // Stop Watchdog timer
/*==================================*/
/* Choose if segment initialization */
/* should be done or not. */
/* Return: 0 to omit initialization */
/* 1 to run initialization */
/*==================================*/
return (1);
}
2. Within the C libraries, GIE (Global Interrupt Enable) is disabled before (and restored after) the
hardware multiplier is used.
3. It is possible to mix assembly and C programs within CCS. See the "Interfacing C/C++ With
Assembly Language" chapter of the MSP430 Optimizing C/C++ Compiler User's Guide (SLAU132).
4. Constant definitions (#define) used within the .h files are effectively reserved and include, for
example, C, Z, N, and V. Do not create program variables with these names.
5. Compiler optimization can remove unused variables and statements that have no effect and can
affect debugging. To prevent this, these variables can be declared volatile; for example:
volatile int i;.
A.3 Debugging
The debugger is part of CCS and can be used as a stand-alone application. This section is applicable
when using the debugger both stand-alone and from the CCS IDE.
1. The debugger reports that it cannot communicate with the device. Possible solutions to this
problem include:
Make sure that the correct debug interface and corresponding port number have been selected in
Project Properties General Device Connection.
Make sure that the jumper settings are configured correctly on the target hardware.
Make sure that no other software application (for example, a printer driver) has reserved or taken
control of the COM or parallel port, which would prevent the debug server from communicating
with the device.
Open the Device Manager and determine if the driver for the FET tool has been correctly installed
and if the COM or parallel port is successfully recognized by the Windows OS. Check the PC BIOS
for the parallel port settings (see FAQ Debugging #5). For users of IBM or Lenovo ThinkPad
computers, try port setting LPT2 and LPT3, even if operating system reports that the parallel port is
located at LPT1.
Restart the computer.
Make sure that the MSP430 device is securely seated in the socket (so that the "fingers" of the socket
completely engage the pins of the device), and that its pin 1 (indicated with a circular indentation on
the top surface) aligns with the "1" mark on the PCB.
CAUTION
Possible Damage To Device
Always handle MSP430 devices with a vacuum pick-up tool only; do not use
your fingers, as you can easily bend the device pins and render the device
useless. Also, always observe and follow proper ESD precautions.
2. The debugger can debug applications that use interrupts and low-power modes. See FAQ
Debugging #17).
3. The debugger cannot access the device registers and memory while the device is running. The
user must stop the device to access device registers and memory.
4. The debugger reports that the device JTAG security fuse is blown. With current MSP430-
FET430UIF JTAG interface tools, there is a weakness when adapting target boards that are powered
externally. This leads to an accidental fuse check in the MSP430 and results in the JTAG security fuse
being recognized as blown although it is not.
Workarounds:
Connect the device RST/NMI pin to JTAG header (pin 11), MSP-FET430UIF interface tools are
able to pull the RST line, this also resets the device internal fuse logic.
Do not connect both VCC Tool (pin 2) and VCC Target (pin 4) of the JTAG header. Specify a value for
VCC in the debugger that is equal to the external supply voltage.
5. The parallel port designators (LPTx) have the following physical addresses: LPT1 = 378h,
LPT2 = 278h, LPT3 = 3BCh. The configuration of the parallel port (ECP, Compatible, Bidirectional,
Normal) is not significant; ECP seems to work well. See FAQ Debugging #1 for additional hints on
solving communication problems between the debugger and the device.
6. The debugger asserts RST/NMI to reset the device when the debugger is started and when the
device is programmed. The device is also reset by the debugger Reset button, and when the device is
manually reprogrammed (using Reload), and when the JTAG is resynchronized (using Resynchronize
JTAG). When RST/NMI is not asserted (low), the debugger sets the logic driving RST/NMI to high
impedance, and RST/NMI is pulled high via a resistor on the PCB.
The RST/NMI signal is asserted and negated after power is applied when the debugger is started.
RST/NMI is then asserted and negated a second time after device initialization is complete.
7. The debugger can debug a device whose program reconfigures the function of the RST/NMI pin
to NMI.
8. The level of the XOUT/TCLK pin is undefined when the debugger resets the device. The logic
driving XOUT/TCLK is set to high impedance at all other times.
9. When making current measurements of the device, ensure that the JTAG control signals are
released, otherwise the device is powered by the signals on the JTAG pins and the measurements are
erroneous. See FAQ Debugging #10.
10. When the debugger has control of the device, the CPU is on (that is, it is not in low-power mode)
regardless of the settings of the low-power mode bits in the status register. Any low-power mode
condition is restored prior to STEP or GO. Consequently, do not measure the power consumed by the
device while the debugger has control of the device. Instead, run the application using Release JTAG
on run.
11. The MEMORY window correctly displays the contents of memory where it is present. However, the
MEMORY window incorrectly displays the contents of memory where there is none present.
Memory should be used only in the address ranges as specified by the device data sheet.
12. The debugger uses the system clock to control the device during debugging. Therefore, device
counters and other components that are clocked by the Main System Clock (MCLK) are affected
when the debugger has control of the device. Special precautions are taken to minimize the effect
upon the watchdog timer. The CPU core registers are preserved. All other clock sources (SMCLK and
ACLK) and peripherals continue to operate normally during emulation. In other words, the Flash
Emulation Tool is a partially intrusive tool.
Devices that support clock control can further minimize these effects by stopping the clock(s) during
debugging (Project Properties CCS Debug Settings Target Clock Control).
13. When programming the flash, do not set a breakpoint on the instruction immediately following
the write to flash operation. A simple work-around to this limitation is to follow the write to flash
operation with a NOP and to set a breakpoint on the instruction following the NOP.
14. Multiple internal machine cycles are required to clear and program the flash memory. When single
stepping over instructions that manipulate the flash, control is given back to the debugger before
these operations are complete. Consequently, the debugger updates its memory window with
erroneous information. A workaround for this behavior is to follow the flash access instruction with a
NOP and then step past the NOP before reviewing the effects of the flash access instruction.
15. Bits that are cleared when read during normal program execution (that is, interrupt flags) are
cleared when read while being debugged (that is, memory dump, peripheral registers).
Using certain MSP430 devices with enhanced emulation logic such as MSP430F43x and MSP430F44x
devices, bits do not behave this way (that is, the bits are not cleared by the debugger read operations).
16. The debugger cannot be used to debug programs that execute in the RAM of F12x and F41x
devices. A workaround for this limitation is to debug programs in flash.
17. While single stepping with active and enabled interrupts, it can appear that only the interrupt
service routine (ISR) is active (that is, the non-ISR code never appears to execute, and the single
step operation stops on the first line of the ISR). However, this behavior is correct because the device
processes an active and enabled interrupt before processing non-ISR (that is, mainline) code. A
workaround for this behavior is, while within the ISR, to disable the GIE bit on the stack, so that
interrupts are disabled after exiting the ISR. This permits the non-ISR code to be debugged (but
without interrupts). Interrupts can later be re-enabled by setting GIE in the status register in the
Register window.
On devices with Clock Control, it may be possible to suspend a clock between single steps and delay
an interrupt request (Project Properties CCS Debug Settings Target Clock Control).
18. On devices equipped with a Data Transfer Controller (DTC), the completion of a data transfer cycle
preempts a single step of a low-power mode instruction. The device advances beyond the low-
power mode instruction only after an interrupt is processed. Until an interrupt is processed, it appears
that the single step has no effect. A workaround to this situation is to set a breakpoint on the
instruction following the low-power mode instruction, and then execute (Run) to this breakpoint.
19. The transfer of data by the Data Transfer Controller (DTC) may not stop precisely when the
DTC is stopped in response to a single step or a breakpoint. When the DTC is enabled and a
single step is performed, one or more bytes of data can be transferred. When the DTC is enabled and
configured for two-block transfer mode, the DTC may not stop precisely on a block boundary when
stopped in response to a single step or a breakpoint.
20. Breakpoints. CCS supports a number of predefined breakpoint and watchpoint types. See
Section 2.2.2 for a detailed overview.
Source code for the TI CCS C compiler and source code for the IAR Embedded Workbench C compiler
are not fully compatible. Standard ANSI/ISO C code is portable between these tools, but implementation-
specific extensions differ and must be ported. This appendix describes the major differences between the
two compilers.
52 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Interrupt Vector Definition
If absolute data placement is needed, this can be achieved with entries into the linker command file, and
then declaring the variables as extern in the C code:
/* CCS Linker Command File Entry */
alpha = 0x200;
beta = 0x202;
/* CCS C Code */
extern char alpha;
extern int beta;
The absolute RAM locations must be excluded from the RAM segment; otherwise, their content may be
overwritten as the linker dynamically allocates addresses. The start address and length of the RAM block
must be modified within the linker command file. For the previous example, the RAM start address must
be shifted 4 bytes from 0x0200 to 0x0204, which reduces the length from 0x0080 to 0x007C (for an
MSP430 device with 128 bytes of RAM):
/* CCS Linker Command File Entry */
/****************************************************************************/
/* SPECIFY THE SYSTEM MEMORY MAP */
/****************************************************************************/
MEMORY /* assuming a device with 128 bytes of RAM */
{
...
RAM :origin = 0x0204, length = 0x007C /* was: origin = 0x200, length = 0x0080 */
...
}
The definitions of the peripheral register map in the linker command files (lnk_msp430xxxx.cmd) and the
device-specific header files (msp430xxxx.h) that are supplied with CCS are an example of placing data at
absolute locations.
NOTE: When a project is created, CCS copies the linker command file corresponding to the
selected MSP430 derivative from the include directory
(<Installation Root>\ccsv5\ccs_base\tools\compiler\MSP430\include) into the project
directory. Therefore, ensure that all linker command file changes are done in the project
directory. This allows the use of project-specific linker command files for different projects
using the same device.
SLAU157AH May 2005 Revised March 2015 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS 53
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Data and Function Placement www.ti.com
With the CCS compiler, the #pragma DATA_SECTION() directive must be used:
/* CCS C Code */
See Section B.5.3 for information on how to translate memory segment names between IAR and CCS.
With the CCS compiler, the following scheme with the #pragma CODE_SECTION() directive must be
used:
/* CCS C Code */
#pragma CODE_SECTION(g, "MYSEGMENT")
void g(void)
{
}
See Section B.5.3 for information on how to translate memory segment names between IAR and CCS.
54 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com C Calling Conventions
CCS Version:
;----------------------------------------------------------------------------
; void WriteDWBE(unsigned char *Add, unsigned long Data)
;
; Writes a DWORD to the given memory location in big-endian format. The
; memory address MUST be word-aligned.
;
; IN: R12 Address (Add)
; R13 Lower Word (Data)
; R14 Upper Word (Data)
;----------------------------------------------------------------------------
WriteDWBE
swpb R13 ; Swap bytes in lower word
swpb R14 ; Swap bytes in upper word
mov.w R14,0(R12) ; Write 1st word to memory
mov.w R13,2(R12) ; Write 2nd word to memory
ret
However, the TI CCS compiler does not pre-initialize these variables; therefore, it is up to the application
to fulfill this requirement:
/* CCS, global variable, manually zero-initialized */
int Counter = 0;
SLAU157AH May 2005 Revised March 2015 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS 55
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Other Differences www.ti.com
The return value controls whether or not data segments are initialized by the C startup code. With the
CCS C compiler, the custom boot routine name is _system_pre_init(). It is used the same way as in the
IAR compiler.
/* CCS C Code */
int _system_pre_init(void)
{
/* Insert your low-level initializations here */
/*================================== */
/* Choose if segment initialization */
/* should be done or not. */
/* Return: 0 to omit initialization */
/* 1 to run initialization */
/*================================== */
return (1);
}
Note that omitting segment initialization with both compilers omits both explicit and non-explicit
initialization. The user must ensure that important variables are initialized at run time before they are used.
56 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Other Differences
SLAU157AH May 2005 Revised March 2015 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS 57
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Other Differences www.ti.com
58 Migration of C Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Appendix C
SLAU157AH May 2005 Revised March 2015
Source for the TI CCS assembler and source code for the IAR assembler are not 100% compatible. The
instruction mnemonics are identical, but the assembler directives are somewhat different. This appendix
describes the differences between the CCS assembler directives and the IAR assembler directives.
SLAU157AH May 2005 Revised March 2015 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS 59
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Sharing C/C++ Header Files With Assembly Source www.ti.com
With the CCS Asm430 assembler, a different scheme that uses the .cdecls directive must be used. This
directive allows programmers in mixed assembly and C/C++ environments to share C/C++ headers
containing declarations and prototypes between the C/C++ and assembly code:
.cdecls C,LIST,"msp430x14x.h" ; Include device header file
More information on the .cdecls directive can be found in the MSP430 Assembly Language Tools User's
Guide (SLAU131).
To allocate code and data sections to specific addresses with the CCS assembler, it is necessary to
create and use memory sections defined in the linker command files. The following example demonstrates
interrupt vector assignment in both IAR and CCS assembly to highlight the differences.
;--------------------------------------------------------------------------
; Interrupt Vectors Used MSP430x11x1 and 12x(2) - IAR Assembler
;--------------------------------------------------------------------------
ORG 0FFFEh ; MSP430 RESET Vector
DW RESET ;
ORG 0FFF2h ; Timer_A0 Vector
DW TA0_ISR ;
;-------------------------------------------------------------------------- ;
Interrupt Vectors Used MSP430x11x1 and 12x(2) - CCS Assembler
;--------------------------------------------------------------------------
.sect ".reset" ; MSP430 RESET Vector
.short RESET ;
.sect ".int09" ; Timer_A0 Vector
.short TA0_ISR ;
Both examples assume that the standard device support files (header files, linker command files) are
used. Note that the linker command files are different between IAR and CCS and cannot be reused. See
Section B.5.3 for information on how to translate memory segment names between IAR and CCS.
60 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Translating A430 Assembler Directives to Asm430 Directives
C.3.1 Introduction
The following sections describe, in general, how to convert assembler directives for the IAR A430
assembler (A430) to Texas Instruments CCS Asm430 assembler (Asm430) directives. These sections are
intended only as a guide for translation. For detailed descriptions of each directive, see either the MSP430
Assembly Language Tools User's Guide (SLAU131) from Texas Instruments or the MSP430 IAR
Assembler Reference Guide from IAR.
The A430 assembler is not case sensitive by default. These sections show the A430 directives written in
uppercase to distinguish them from the Asm430 directives, which are shown in lower case.
SLAU157AH May 2005 Revised March 2015 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS 61
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Translating A430 Assembler Directives to Asm430 Directives www.ti.com
(3)
Alignment on byte boundary .align 1
Alignment on word boundary .align 2 EVEN
(1)
.bss and .usect do not require switching back and forth between the original and the uninitialized section. For example:
; IAR Assembler Example
RSEG DATA16_N ; Switch to DATA segment
EVEN ; Ensure proper alignment
ADCResult: DS 2 ; Allocate 1 word in RAM
Flags: DS 1 ; Allocate 1 byte in RAM
RSEG CODE ; Switch back to CODE segment
; CCS Assembler Example #1
ADCResult .usect ".bss",2,2 ; Allocate 1 word in RAM
Flags .usect ".bss",1 ; Allocate 1 byte in RAM
; CCS Assembler Example #2
.bss ADCResult,2,2 ; Allocate 1 word in RAM
.bss Flags,1 ; Allocate 1 byte in RAM
(2)
Space is reserved in an uninitialized segment by first switching to that segment, then defining the appropriate memory block, and
then switching back to the original segment. For example:
RSEG DATA16_Z
LABEL: DS 16 ; Reserve 16 byte
RSEG CODE
(3)
Initialization of bit-field constants (.field) is not supported, therefore, the section counter is always byte-aligned.
62 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Translating A430 Assembler Directives to Asm430 Directives
Description Asm430 Directive (CCS) A430 Directive (IAR)
Allow false conditional code block listing .fclist LSTCND-
Inhibit false conditional code block listing .fcnolist LSTCND+
Set the page length of the source listing .length PAGSIZ
Set the page width of the source listing .width COL
Restart the source listing .list LSTOUT+
Stop the source listing .nolist LSTOUT-
LSTEXP+ (macro)
Allow macro listings and loop blocks .mlist
LSTREP+ (loop blocks)
LSTEXP- (macro)
Inhibit macro listings and loop blocks .mnolist
LSTREP- (loop blocks)
(1)
Select output listing options .option
Eject a page in the source listing .page PAGE
(2)
Allow expanded substitution symbol listing .sslist
(2)
Inhibit expanded substitution symbol listing .ssnolist
(3)
Print a title in the listing page header .title
(1)
No A430 directive directly corresponds to .option. The individual listing control directives (above) or the command-line option -c
(with suboptions) should be used to replace the .option directive.
(2)
There is no directive that directly corresponds to .sslist and .ssnolist.
(3)
The title in the listing page header is the source file name.
Modules may be used with the Asm430 assembler to create individually linkable routines. A file may
contain multiple modules or routines. All symbols except those created by DEFINE, #define (IAR
preprocessor directive) or MACRO are "undefined" at module end. Library modules are, furthermore,
linked conditionally. This means that a library module is included in the linked executable only if a public
symbol in the module is referenced externally. The following directives are used to mark the beginning and
end of modules in the A430 assembler.
SLAU157AH May 2005 Revised March 2015 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS 63
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Translating A430 Assembler Directives to Asm430 Directives www.ti.com
64 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Translating A430 Assembler Directives to Asm430 Directives
SLAU157AH May 2005 Revised March 2015 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS 65
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Translating A430 Assembler Directives to Asm430 Directives www.ti.com
66 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Translating A430 Assembler Directives to Asm430 Directives
Listing Control Directives C-Style Preprocessor Directives (3) Symbol Control Directives
LSTMAC () #define ASEG
LSTCOD () #undef RSEG
LSTPAG () #if, #else, #elif COMMON
LSTXREF () #ifdef, #ifndef STACK
#endif ORG
#include
#error
(1)
There is no direct support for IAR REPTC and REPTI directives in CCS. However, equivalent functionality can be achieved using
the CCS .macro directive:
; IAR Assembler Example
REPTI zero,"R4","R5","R6"
MOV #0,zero
ENDR
; CCS Assembler Example
zero_regs .macro list
.var item
.loop
.break ($ismember(item, list) = 0)
MOV #0,item
.endloop
.endm
Code that is generated by calling "zero_regs R4,R5,R6":
MOV #0,R4
MOV #0,R5
MOV #0,R6
(2)
In CCS, local labels are defined by using $n (with n=09) or with NAME?. Examples are $4, $7, or Test?.
(3)
The use of C-style preprocessor directives is supported indirectly through the use of .cdecls. More information on the .cdecls
directive can be found in the MSP430 Assembly Language Tools User's Guide (SLAU131).
SLAU157AH May 2005 Revised March 2015 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS 67
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Translating A430 Assembler Directives to Asm430 Directives www.ti.com
68 Migration of Assembler Code from IAR 2.x, 3.x, or 4.x to CCS SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Appendix D
SLAU157AH May 2005 Revised March 2015
Source code for the TI CCS C compiler and source code for the Red Hat GCC for MSP430 compiler are
not fully compatible. Standard ANSI/ISO C code is portable between these tools, but implementation-
specific extensions differ and must be ported. This appendix describes the major differences between the
two compilers.
SLAU157AH May 2005 Revised March 2015 Writing Portable C Code for CCS and Red Hat GCC for MSP430 69
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Interrupt Vector Definition www.ti.com
Further information on the use of the GCC compiler can be found in the document Using the GNU
Compiler Collection.
70 Writing Portable C Code for CCS and Red Hat GCC for MSP430 SLAU157AH May 2005 Revised March 2015
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
www.ti.com Interrupt Vector Definition
SLAU157AH May 2005 Revised March 2015 Writing Portable C Code for CCS and Red Hat GCC for MSP430 71
Submit Documentation Feedback
Copyright 20052015, Texas Instruments Incorporated
Appendix E
SLAU157AH May 2005 Revised March 2015
FET-Specific Menus
This appendix describes the CCS menus that are specific to the FET.
E.1 Menus
F.1 MSP430L092
NOTE: See the corresponding MSP430 device family user's guide for additional LPMx.5 and ultra-
low-power debug mode details.
Revision History
Changes from December 17, 2014 to March 19, 2015 .................................................................................................... Page
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other
changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest
issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All semiconductor products (also referred to herein as components) are sold subject to TIs terms and conditions of sale
supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TIs terms
and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary
to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily
performed.
TI assumes no liability for applications assistance or the design of Buyers products. Buyers are responsible for their products and
applications using TI components. To minimize the risks associated with Buyers products and applications, Buyers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or
other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information
published by TI regarding third-party products or services does not constitute a license 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 significant portions 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. TI is not responsible or liable for such altered
documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service
voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.
TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support
that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which
anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause
harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use
of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TIs goal is to
help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and
requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties
have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or enhanced plastic are designed and intended for use in
military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components
which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and
regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use of
non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
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 Applications Processors www.ti.com/omap TI E2E Community e2e.ti.com
Wireless Connectivity www.ti.com/wirelessconnectivity
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright 2015, Texas Instruments Incorporated