Freescale Kinetis CPU Support Package

This package contains project templates and system files for the Freescale Kinetis.

Installation Instructions

CrossWorks Version 2.x Installation Instructions

To install this support package using CrossStudio:

1. Click the Tools > Package Manager menu option to open the package manager window.
2. Right click on the Freescale Kinetis 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.

Alternatively, to manually install this support package:

1. Download the file Kinetis.hzq using your web browser.
2. Click the Tools > Manually Install Packages menu option.
3. Select the file you have just downloaded to install the package.

To view the support package and its contents:

1. Click the Tools > Show Installed Packages.
2. Click on the Freescale Kinetis CPU Support Package link.

Release Notes

1.4

• Support for latest parts based on the sub-family name and memory size rather than specific part numbers. For example MK60DN512ZVMD10 has become MK60DN512Zxxx10. You will need to reselect the Target Processer property for existing projects.
• Updated the flash loader to handle 50Mhz and 120Mhz devices.
• Modified the startup code to have part specific vector tables.
• Modified the startup code to enable the FPU for devices that have one.
• Supplied samples for TWR-K20D50M, TWR-K60F120M and TWR-K70F120M.

1.3

• Supplied samples for TWR-K53N512.
• Supplied firmware update for OSJTAG.
• Kinetis projects now have the 'GCC Target' property set to be 'arm-unknown-eabi'.
• Fixed reset script to stop the target prior to accessing MDM registers for 'P&E' target interface.

1.2

• Support for latest parts and new part numbering e.g MK60N512VMD100 has become MK60DN512ZVMD10. You will need to reselect the Target Processor property for existing projects.
• Added GetPartName and MatchPartName functions to the target script. New projects will set the Get Part Name Script and Match Part Name Script project properties to enable part name detection on connect and compatibility on start debugging (requires CrossWorks for ARM Version 2.1.2 and above).
• Removed Kinetis_SystemInit.c you'll need to add the appropriate CMSIS system_MKxxDZ10.c file to your project.
• Startup code now supplies a default weak SystemInit() function that disables the watchdog.

1.1

• Fixed Flash Vectors In RAM placement when the Enable Unused Symbol Removal property is enabled.

1.0

• Initial Release.

Documentation

1) Creating Kinetis Projects

To create a new Kinetis project

• Select the File > New > New Project menu item.
• Select the appropriate Generic Kinetis 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.
• 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.

2) Kinetis 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 View Memory Map or View Memory Map (as text).

Selecting the target processor will cause the preprocessor definition __TARGET_PROCESSOR to be set to the specified processor name when you compile the project.

Section Placement

CrossStudio for ARM supports Kinetis projects running applications in a number of different memory configurations. You can select the memory configuration you require by right clicking on the project node in the project explorer and selecting the Placement entry.

For Kinetis projects the set of placements are:

• Flash application runs in internal Flash memory.
• Flash Vectors In RAM application runs in internal Flash memory with exception vectors in RAM memory.
• Flash Copy To RAM application starts in internal flash and copies itself to run internal RAM memory.
• RAM application runs internal RAM memory.

Stack and Heap Sizes

The stack and heap sizes are set to be 128 bytes by default when a project is created. This enables projects to run on the smallest of the Kinetis processors. It is likely that you will need to change these values when developing applications to run on the larger of the Kinetis processors.

Target Startup Code

The startup code Kinetis_Startup.s is common to all Kinetis 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 symbol SystemInit with the stack pointer set to the top of RAM. 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 symoblic names (and weak implementations) for each interrupt service routine, for example the PORTA_IRQHandler function will be called when this interrupt occurs. If you are porting code that has application specific interrupt service routine names then you can use the preprocessor definitions to rename the symbol for example PORTA_IRQHandler=porta_isr.

Target Reset Script

The reset script Kinetis_Target.js is used by the debugger to reset the target board. For OSJTAG and CrossConnect/FTDI/Wiggler target interfaces the MDM-AP is used to reset the target board. For J-Link target interfaces this script will use the SRST signal so in order to reset the target properly and therefore debug your application reliably from a defined state the SRST signal should be connected.

Kinetis Internal Flash Loader

The source code to the flash loaders (click to load solution) for the internal Flash of the Kinetis is provided.

Memory Simulator

An Kinetis memory simulator is provided that simulates the memories of the various Kinetis 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 are included as part of the new project setup. The file Kinetis.h is provided which selects the appropriate header file depending on the target processor selection.

CTL support

The file Kinetis_ctl.c implements the CTL system timer using the Cortex-M4 SysTick timer. The timer is configured to interrupt at a 10 millisecond rate and increment the CTL system timer by 10 to give a millisecond timer. The implementation uses the CMSIS SystemCoreClock global variable to determine the CPU clock frequency. The CTL samples that are provided in this package have board specific files that initialise this variable.

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 and disables global interrupts by raising the NVIC basepriority above the highest CTL priority. This enables you to use the upper half of the NVIC priorities for interrupts that do not use CTL and should not be disabled by a CTL interrupt.

3) CrossWorks Shared Sample Projects

The following project files are supplied that can be used to run the standard CrossWorks shared samples.

• TWR-K20D50M Shared Samples (click to load project)
• TWR-K40X256 Shared Samples (click to load project)
• TWR-K53N512 Shared Samples (click to load project)
• TWR-K60N512 Shared Samples (click to load project)
• TWR-K60F120M Shared Samples (click to load project)
• TWR-K70F120M Shared Samples (click to load project)

The board specific file Kinetis_ctl_board.c is included in the samples that sets up the PLL (either using a bespoke constructor function or the standard Freescale CMSIS function) and implements the ctl board support functions to flash a led and handle a button press.

4) CTL Sample Projects

The following project files are supplied that can be used to run the standard CrossWorks CTL samples.

• TWR-K20D50M CTL Samples (click to load project)
• TWR-K40X256 CTL Samples (click to load project)
• TWR-K53N512 CTL Samples (click to load project)
• TWR-K60N512 CTL Samples (click to load project)
• TWR-K60F120M CTL Samples (click to load project)
• TWR-K60F120M CTL VFP Sample (click to load project)
• TWR-K70F120M CTL Samples (click to load project)
• TWR-K70F120M CTL VFP Sample (click to load project)

The board specific file Kinetis_ctl_board.c is included in the samples that sets up the PLL (either using a bespoke constructor function or the standard Freescale CMSIS function) and implements the ctl board support functions to flash a led and handle a button press.

5) OSJTAG Firmware Update

The package contains an update to the firmware that can be loaded on to the OSJTAG hardware of the TWR CPU modules. The updated firmware improves the download and debug performance of the CrossWorks 'Kinetis OSJTAG' target interface. You'll need to use the firmware update procedure available from PE micro and point the updater program at the supplied file osbdm-jm60_kinetis_rowley_101_0.s19. You can click on the above link to get a copy of the firmware into the editor and then right click on the editor tab and select 'Copy Full Path' to get the path to the filename of the firmware into the paste buffer.