2.1 Overview
2.2 Using KickStart
2.2.1 Project Settings
Overview
Applications are developed in assembler and/or C using the Workbench, and they are debugged using
C-SPY. C-SPY is seamlessly integrated into the Workbench. However, it is more convenient to make the
distinction between the code development environment (Workbench) and the debugger (C-SPY). C-SPY
can be configured to operate with the FET (i.e., an actual MSP430 device), or with a software simulator of
the device. KickStart is used to refer to the Workbench and C-SPY collectively. The KickStart software
tools are a product of IAR.
Documentation for the MSP430 family and KickStart is extensive. The CD-ROM supplied with this tool
contains a large amount of documentation describing the MSP430. The MSP430 home page
(www.ti.com/msp430 ) is another source of MSP430 information. The components of KickStart
(workbench/debugger, assembler, compiler, linker) are fully documented in <Installation Root>\Embedded
Workbench x.x\common\doc and <Installation Root>\Embedded Workbench\430\doc. .htm files located
throughout the KickStart directory tree contain the most up-to-date information and supplement the .pdf
files. In addition, KickStart documentation is available online via Help.
Read Me First files from IAR and TI and this document can be accessed using Start → Programs → IAR
Systems → IAR Embedded Workbench KickStart for MSP430 V3.
Tool User's Guide Most Up-To-Date Information
Workbench/C-SPY EW430_UsersGuide.pdf readme.htm, ew430.htm, cs430.htm, cs430f.htm
Assembler EW430_AssemblerReference.pdf a430.htm, a430_msg.htm
Compiler EW430_CompilerReference.pdf icc430.htm, icc430_msg.htm
C library CLibrary.htm
Linker and Librarian xlink.pdf xlink.htm, xman.htm, xar.htm
The KickStart development environment is function limited. The following restrictions are in place:
• The C compiler does not generate an assembly code list file.
• The linker links a maximum of 4K bytes of code originating from C source (but an unlimited amount of
code originating from assembler source).
• The simulator inputs a maximum of 4K bytes of code.
A full (i.e., unrestricted) version of the software tools can be purchased from IAR. A mid-featured tool set –
called Baseline, with a 12K-byte C-code size limitation and basic floating-point operations – is also
available from IAR. Consult the IAR web site (www.iar.se ) for more information.
The settings required to configure the Workbench and C-SPY are numerous and detailed. Please read
and thoroughly understand the documentation supplied by IAR when dealing with project settings. Review
the project settings of the supplied assembler and C examples (the project settings are accessed using
Project → Options with the project name selected). Use these project settings as templates when
developing your own projects. Note that if the project name is not selected when settings are made, the
settings are applied to the selected file (not to the project).
The following project settings are recommended/required:
• Specify the target device (General Options → Target → Device).
• Enable an assembler project or a C/assembler project (General Options → Target → Assembler-only
project).
• Enable the generation of an executable output file (General Options → Output → Output file →
Executable)
• To most easily debug a C project, disable optimization [C/C++ Compiler → Optimizations → Size →
None (Best debug support)].
16 Development Flow SLAU138F – June 2004 – Revised March 2007
Submit Documentation Feedback
To Next Page
Loading...
Need help?
General
