NXP K32L CPU Support Package

This package contains project templates and system files for the NXP K32L.

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 NXP K32L 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 NXP K32L 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 5 CMSIS-Core(M) Support Package, CMSIS 5 CMSIS-DSP Support Package, CMSIS 5 Support Package and CrossWorks Tasking Library Package installation instructions.
2. Download the file K32L.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 NXP K32L CPU Support Package link to view the package and its contents.

Release Notes

4.0

• Initial Release.

Documentation

Creating K32L Projects

To create a new K32L project

• Select the File > New > New Project menu item.
• Select the appropriate Generic K32L 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 SRAM 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.
• 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 import MCUXpresso project files

• Select File > Import Project... > Import Eclipse Project menu item.
• Navigate to the directory containing the eclipse .project and select it.
• Type "K32L" in the Project Template Chooser search.
• Select one of the displayed project templates.
• Set the Section Placement and Target Processor properties.
• For projects that use the CrossWorks tools you will need to remove the startup and drivers folders from the project.

K32L Project Specifics

Stack and Heap Sizes

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

Target Startup Code

The startup code is device specific and is selected with the Target Processor entry. 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 end of the stack section. 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.

The startup code declares symbolic names (and weak implementations) for each interrupt service routine, for example the RTC_SEC_IRQHandler function will be called when the RTC second match 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 RTC_SEC_IRQHandler=RTC_SEC_DriverIRQHandler.

Target Reset Script

The reset script K32L_Target.js is used by the debugger to reset the target board and to enable the tracing capabilities of the device.