
Development Flow
Note: Avoid the use of absolute pathnames when referencing files.
Instead, use the relative pathname keywords $TOOLKIT_DIR$ and
$PROJ_DIR$. Refer to the IAR documentation for a description of these keywords. The use of relative pathnames will permit projects to be moved easily, and projects will not require modification when IAR systems are upgraded (say, from Kickstart, or Baseline, to Full).
2.2.2Creating a Project from Scratch
The following section presents
1)Start the Workbench
EMBEDDED WORKBENCH KICKSTART FOR MSP430
2)Create a new text file
3)Enter the program text into the file.
Note: Use .h files to simplify your code development
Kickstart is supplied with files for each device that define the device registers and the bit names, and these files can greatly simplify the task of developing your program. The files are located in <Installation Root>\Embedded Workbench x.x\430\inc. Simply include the .h file corresponding to your target device in your text file (#include “msp430xyyy.h”). Additionally, files io430xxxx.h are provided, and are optimized to be included by C source files.
4)Save the text file
It is recommended that assembler text file be saved with a file type suffix of “.s43”, and that C text files be saved with a file type suffix of “.c”.
5)Create a new workspace
6)Create a new project
7)Add the text file to the project