Texas Instruments StellarisWare Updates for CrossWorks For ARM

Texas Instruments StellarisWare Updates for CrossWorks For ARM

CrossWorks Version 4 Installation Instructions

To install this support package

1. Click the Tools > Package Manager menu option to open the package manager window.
2. Right click on the Texas Instruments StellarisWare Updates for CrossWorks For ARM entry and select Install Selected Packages.
3. Click Next to take you to the summary page.
4. Click Next to install the package.
5. Click Finish to close the package manager window.
6. Click the Tools > Show Installed Packages.
7. Click on the Texas Instruments StellarisWare Updates for CrossWorks For ARM link to view the package and its contents.

To manually install this support package

1. If you have not done so already, follow the CMSIS 3 Support Package, CrossWorks Tasking Library Package and Texas Instruments Stellaris CPU Support Package installation instructions.
2. Download the file StellarisWareUpdates.hzr using your web browser.
3. Click the Tools > Manually Install Packages menu option.
4. Select the file you have just downloaded to install the package.
5. Click the Tools > Show Installed Packages.
6. Click on the Texas Instruments StellarisWare Updates for CrossWorks For ARM link to view the package and its contents.

To install this support package using other versions

• CrossWorks Version 2 Installation Instructions
• CrossWorks Version 3 Installation Instructions

Release Notes

1.3

• Updated to version 7611 of StellarisWare packages.
• Removed flash_placement_boot_loadee.xml and flash_placement_boot_loader.xml files.
• Modified bl_crossworks.s so that it only configures the micro after reset.
• Removed updated driverlib files.

1.2

• Updated to version 6075 of StellarisWare packages.
• Added samples for RDK-IDM-L35.
• Each example now has it's own project file.
• Boot loadee examples now use the standard LM3S Flash placement and set the FLASH_START linker macro to reserve space for the bootloader.
• Boot loader examples now use the standard LM3S Flash Copy To RAM placement.

1.1

• Updated to latest version of StellarisWare packages.
• Added samples for DK-LM3S9B96.

1.0

• Initial Release.

Documentation

1) Installation

You should download and install the appropriate StellarisWare package(s) from the Luminary Micro website.

When you install this package you will be prompted for the StellarisWare installation directory. This package will add CrossWorks project files to the StellarisWare installation directory. This package will also overwrite some StellarisWare source files that have been modified, you may be prompted before the files are overwritten, if so answer yes.

The CrossWorks package installation process will set the CrossWorks global macro STELLARISWARE which is used by the CrossWorks project files to refer to StellarisWare directories and files. If you subsequently move the StellarisWare installation directory you should modify this macro using the "Tools|Macros" dialog.

This package has been tested with version 4781 of the StellarisWare packages.

2) Building StellarisWare Libraries

The StellarisWare libraries are built in CrossWorks using StellarisWareLibrary.hzp (click to load project) in either Debug or Release configuration. The code generation options are the same for both configurations, however the debug level is reduced to backtrace only support when built in Release configuration. When built in Debug configuration the preprocessor define DEBUG is set which enables the StellarisWare error handling - see the Error Handling section of the StellarisWare driver library documentation for details.

3) StellarisWare Examples

A subset (based on hardware availibility and the rate of attrition) of Luminary Micro board examples have been built and tested.

The project properties that are required for the examples are set on the project node in Common configuration so if you want to see what properties are required to build a particular example project you need only look in one place. Note that you can look at (and modify) project files by right-clicking on the solution node in the project explorer and selecting Edit Solution As Text. The properties that have to be set are typically:

• Preprocessor Definitions for the StellarisWare library: gcc, PART_LM3Sxxx, TARGET_IS_DUSTDEVIL_RA0, TARGET_IS_TEMPEST_RB1.
• Preprocessor Definitions for the LM3S_Startup.s file: STARTUP_FROM_RESET and renaming of interrupt handler functions to the application specific interrupt handler function name e.g. Analog_Comparator_0_ISR=CompIntHandler.
• User Include Directories: $(STELLARISWARE);..;. adds the StellarisWare installation directory, the board directory and the project directory to the include directory search path.
• Linker Additional Input Files: $(STELLARISWARE)/lib/libdriver.a.
• Main Stack Size: The stack size in (word sized) bytes.

The following project files are supplied.

• DK-LM3S9B96 (click to load project)
• DK-LM3S101 (click to load project)
• DK-LM3S102 (click to load project)
• DK-LM3S301 (click to load project)
• DK-LM3S801 (click to load project)
• DK-LM3S811 (click to load project)
• DK-LM3S815 (click to load project)
• DK-LM3S817 (click to load project)
• DK-LM3S818 (click to load project)
• DK-LM3S828 (click to load project)
• EK-LM3S1968 (click to load project)
• EK-LM3S2965 (click to load project)
• EK-LM3S3748 (click to load project)
• EK-LM3S6965 (click to load project)
• EK-LM3S811 (click to load project)
• EK-LM3S8962 (click to load project)
• EK-LM3S9B90 (click to load project)
• EK-LM3S9B92 (click to load project)
• RDK-IDM (click to load project)
• RDK-IDM-L35 (click to load project)

The bootloader examples (e.g. boot_serial) are built with Flash Copy To RAM placement and use the CrossWorks specific file bl_crossworks.s for the bootloader main code.

The bootloadee examples (e.g. boot_demo1) set the macro FLASH_START using the Section Placement Macros project property to reserve space for the bootloader e.g. FLASH_START=0x1000 will reserve 4 kilo bytes for the bootloader.

4) Known Problems

• The USB host/stick samples don't work.
• The ethernet bootloader doesn't work.
• The MPU fault sample fails on the DK-LM3S9B96.