MSP430 Release

IAR Embedded Workbench


General

Release consists of the RTOS sources and three sample projects - see Release description for details. Each sample located in separate folder. Structure of test project folder (folders are in brackets '[]'):

[Config]          - linker scripts and other utilities
[Exe]             - executable product[s]
[List]            - listings and other temporary text files
[Obj]             - objects and other intermediate files
[settings]        - IAR IDE auxiliary files
[Src]             - test project sources
slon.vpj          - SlickEdit project file
slon.MSP430.vpw   - SlickEdit workspace file
SConstruct        - Scons main script file
slon.ewd          - IAR IDE auxiliary file
slon.ewp          - IAR IDE project
slon.eww          - IAR IDE workspace

slon is test project name.

Structure of the RTOS folder:

scmRTOS
  Common            - common RTOS sources
  MSP430            - portable part

See Distribution section and below about release using manners.


Building

There are several ways to build any sample.

The first is to use IAR IDE. Just launch IDE, open appropriate workspace (*.eww file) and build the project.

Another way is to employ SCons build system. Scons is actually Python script, so Python interpreter is necessary to use SCons. Python interpreter can be downloaded from Python's official site. SCons, in a certain sense, is analog of popular build utility make, but much more powerful because of comprehensive underground of programming language (Python).

To use SCons:

  • download and install Python interpreter v2.4.
  • download and install SCons tool.
  • launch SCons by typing tool name in command line in folder where SConstruct file (SCons main script) located [1].
$PROMPT$>scons

SCons will build the project.

If user want to use his own build system [2] he has to specify the following command-line options for various tools:

Assembler:

-S
-DF169
-M()
-LList\
-OObj\
-ISrc
-I../scmRTOS/Common
-I../scmRTOS/MSP430
-I$TOOLKIT_PATH$\430\inc
-I$TOOLKIT_PATH$\430\inc\dlib

Compiler:

-e
--eec++
-s9
-lC List
--silent
--debug
-o Obj
-DF169
-ISrc
-I../scmRTOS/Common
-I../scmRTOS/MSP430
-I$TOOLKIT_PATH$\430\inc
-I$TOOLKIT_PATH$\430\inc\dlib

Linker:

-s __program_start
-r
-xsmeo
dl430fn.r43
-o Exe\slon.d43
-l List\slon.map
-f Config\lnk430F169.xcl
-I$TOOLKIT_PATH$\430\lib\dlib
-f $TOOLKIT_PATH$\430\config\multiplier.xcl

Note

where $TOOLKIT_PATH$ - path to folder with toolkit installed.


[1]SConstruct file contains variable TOOLKIT_PATH that specifies path to toolkit on particular PC. The user should correct this path according to his PC toolkit location. The path can be specified directly or through system environment variables as well.
[2]For example, make utility or simple bat file.