NXP KL03/KL17/KL27系列MCU 基础开发包代码

1 Overview

The Kinetis Software Development Kit (KSDK) provides

comprehensive software support for Kinetis Microcontrollers.

The KSDK includes a flexible set of peripheral drivers

designed to speed up and simplify development of embedded

applications. Along with the peripheral drivers, the KSDK

provides an extensive and rich set of example applications

covering everything from basic peripheral use case examples

to full demo applications. The KSDK also contains RTOS

ksdk

Document Number: KSDK20GSUG

NXP Semiconductors

User's Guide

Rev. 1, 06/2016

Getting Started with Kinetis SDK

(KSDK) v.2.0

Contents

1 Overview................................ ................................ 1

2 KSDK Board Support Folders......... .......................2

TrueSTUDIO®....................................... ..............25

7 Run a demo using ARM GCC.............................. 33

8 Appendix A - How to determine COM

port.........................................................................42

9 Appendix B - Default debug interfaces ................44

10 Appendix C - Updating OpenSDA

firmware................................................ ................45

11 Revision History................................................... 46

Figure 1. KSDK layers

2 KSDK Board Support Folders

KSDK board support provides example applications for Kinetis development and evaluation boards. Board support packages

are found inside of the top level boards folder, and each supported board has its own folder (a KSDK package can support

multiple boards). Within each <board_name> folder there are various sub-folders to classify the type of examples they

(for example, ADC conversion using DMA).

• rtos_examples: Basic FreeRTOS examples showcasing the use of various RTOS objects (semaphores, queues, and so

on) and interfacing with the KSDK’s RTOS drivers

• usb_examples: Applications that use the USB host/device/OTG stack.

This section describes how the various types of example applications interact with the other components in the KSDK. To get

a comprehensive understanding of all KSDK components and folder structure, see the Kinetis SDK v.2.0 API Reference

Manual document (KSDK20APIRM).

Each <board_name> folder in the boards directory contains a comprehensive set of examples that are relevant to that specific

piece of hardware. We’ll discuss the hello_world example (part of the demo_apps folder), but the same general rules apply to

Figure 2. Application folder structure

All files in the application folder are specific to that example, so it’s very easy to copy-paste an existing example to start

developing a custom application based on a project provided in the KSDK.

When opening an example application in any of the supported IDEs, there are a variety of source files referenced. The KSDK

• devices/<device_name>/drivers: All of the peripheral drivers for your specific MCU.

• devices/<device_name>/<tool_name>: Toolchain-specific startup code. Vector table definitions are here.

• devices/<device_name>/utilities: Items such as the debug console that are used by many of the example applications.

For examples containing middleware/stacks and/or a RTOS, there will be references to the appropriate source code.

Middleware source files are located in the middleware folder and RTOSes are in the rtos folder. Again, the core files of each

of these are shared, so modifying them could have potential impacts on other projects that depend on them.

3 Run a demo application using IAR

This section describes the steps required to build, run, and debug example applications provided in the Kinetis SDK. The

hello_world demo application targeted for the FRDM-K64F Freedom hardware platform is used as an example, although

these steps can be applied to any example application in the KSDK.

Using the FRDM-K64F Freedom hardware platform as an example, the hello_world workspace is located in

<install_dir>/boards/frdmk64f/demo_apps/hello_world/iar/hello_world.eww

Figure 3. Demo build target selection

The build completes without errors.