Texas Instruments MSP432 CPU Support Package

This package contains project templates and system files for the Texas Instruments MSP432.

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 MSP432 CPU Support Package 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 MSP432 CPU Support Package 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 4 CMSIS-CORE Support Package, CMSIS 4 CMSIS-DSP Support Package and CrossWorks Tasking Library Package installation instructions.
2. Download the file MSP432.hzq 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 MSP432 CPU Support Package link to view the package and its contents.

To install this support package using other versions

• CrossWorks Version 3 Installation Instructions

Release Notes

3.0

• Initial Release.

Documentation

Creating MSP432 Projects

To create a new MSP432 project

• Select the File > New > New Project menu item.
• Select the appropriate Generic MSP432 from the Categories list.
• Select the required project template type from the Templates list.
• Set the required project name and location directory.
• Click OK.

To build and debug an application the runs in Flash memory

• Select the project to work on by using the Project > Set Active Project menu option.
• Select the configuration you require by using the Build > Set Active Build Configuration menu option.
• Right click on the project node in the project explorer and select the Flash placement property.
• Build the project by using the Build > Build Project menu option.
• Connect to the appropriate target in the target window.
• Download and start debugging the current project by using Debug > Start Debugging.

To make the application startup from reset

• Right click on the project node in the project explorer and select Properties...
• In the properties window scroll down to the Preprocessor Options section.
• Type STARTUP_FROM_RESET into the Preprocessor Definitions property editor.

MSP432 Project Specifics

Target Processor

Once a project has been created you can select different target processors by right clicking on the project node in the project explorer and selecting the Target Processor entry.

Selecting the target processor will specify the memory map that is used for the build and debug. You can view the selected memory map by right clicking on the project node in the project explorer and selecting Edit Memory Map.

Section Placement

CrossStudio for ARM supports MSP432 projects running applications in a number of different memory configurations. You can select the memory configuration you require by setting the Section Placement property.

For MSP432 projects the set of placements are:

• Flash application runs in internal Flash memory.
• Flash Vectors In RAM application run in Flash memory, exception vectors are in RAM.
• Flash Copy To RAM application boots from Flash memory and runs in RAM.
• RAM application runs in RAM memory.

Stack and Heap Sizes

The default stack and heap sizes are set to be 256 and 0 bytes by default when a project is created.

Target Startup Code

The startup code MSP432_Startup.s is common to all MSP432_Startup processors. There are a set of preprocessor defines that configure the startup code and are documented in the startup file itself. The startup code calls out to a weak symbol SystemInit with the stack pointer set to the top of of SRAM. The SystemInit function can be used to set the CPU clock or configure any external memories prior to the C initialisation code as such it cannot access initialised static data. Note that the SystemInit() function is called with the stackpointer pointing to the end of the first block of SRAM.

The startup code declares symbolic names (and weak implementations) for each interrupt service routine, for example the PORT1_IRQHandler function will be called when the P1IFG interrupt occurs. The names of the interrupt service routines match those in the CMSIS header file. If you are porting code that has application specific interrupt service routines then you can use preprocessor definitions to rename the declared symbolic name for example PORT1_IRQHandler=Port1IsrHandler.

Target Reset Script

The reset script MSP432_Target.js is used by the debugger to reset the target board.

Memory Simulator

An MSP432 memory simulator is provided that simulates the memories of the various MSP432 devices. The memory simulation parameter (which is set by the Target Processor selection) specifies the device name, the size of the internal Flash and RAM memories.

CMSIS support

CMSIS header files and library are referenced as part of the new project setup. The Texas Instruments MSP432 CMSIS files and driverlib files are supplied.

CTL support

The file ctl_msp430.c implements the CTL system timer using the standard Cortex-M SysTick timer. The timer is configured to interrupt at approximately a 10 millisecond rate and increment the CTL system timer by 10 to give a millisecond timer.

The CTL interrupt support functions ctl_global_interrupts_set, ctl_set_priority, ctl_unmask_isr and ctl_mask_isr are implemented in this file. The implementation uses the lowest half of the available NVIC priorities (top bit set in the priority) for CTL interrupts.