1
Plug It In2
Get Software3
Build, Run4
CreateSign in to save your progress. Don't have an account? Create one.
Let's take your FRDM-KL46Z for a test drive! Follow the detailed actions list below.
Something went wrong! Please try again.
Your FRDM-KL46Z comes loaded with a "bubble level" demo that leverages the on-board accelerometer. When the board is flat, the RGB LED is turned off, and when the board is tilted, the red or green LEDs gradually illuminate based on the degree of tilt on the X- and Y-Axis.
Something went wrong! Please try again.
Choose a Development Path:
The Kinetis Software Development Kit (SDK) is complimentary and includes full source code under a permissive open-source license for all hardware abstraction and peripheral driver software. Learn about SDK.
Click below to download the SDK Release appropriate for your computer's operating system.
Something went wrong! Please try again.
NXP offers a complimentary toolchain called Kinetis Design Studio (KDS).
No problem! The Kinetis SDK includes support for other tools such as IAR , Keil and command-line GCC .
Something went wrong! Please try again.
Many of the example applications output data over the MCU UART so you'll want to make sure that the driver for the board's virtual COM port is installed. It should install automatically when you plug the board in to your PC. If the driver does not automatically install, click here to download the installer.
With the serial port driver installed, run your favorite terminal application to view the serial output from the MCU's UART. Configure the terminal to 115,200 baud rate, 8 data bits, no parity and 1 stop bit. To determine the port number of the FRDM-KL46Z's virtual COM port, open the device manager and look under the "Ports" group.
Not sure how to use a terminal application? Try one of these tutorials: Tera Term Tutorial, PuTTY Tutorial.
Something went wrong! Please try again.
The Kinetis SDK comes with a long list of demo applications and driver examples. To see what's available,
browse to the SDK 'examples' folder of your SDK installation and select your board, the
FRDM-KL46Z: <sdk_install_directory>/examples/frdmkl46z
.
To learn more about demo applications or driver examples, open the Kinetis SDK Demo Applications User's Guide,
located in <sdk_install_directory>/doc
.
Something went wrong! Please try again.
If one or more of the demo applications or driver examples sounds interesting, you're probably wanting to know how you can build and debug yourself. The Getting Started with Kinetis SDK guide provides easy, step-by-step instructions on how to configure, build, and debug demos for all toolchains supported by the SDK.
Use the guide below to learn how to open, build and debug an example application using the Kinetis Design Studio (KDS) IDE.
Before using KDS IDE with KSDK, the KSDK Eclipse Update must be applied. Without this update, Eclipse cannot generate KSDK-compatible projects.
The steps required for Mac OS are identical to Windows; the only difference is that the IDE looks slightly different.
<install_dir>/tools/eclipse_update
folder and select the KSDK_<version>_Eclipse_Update.zip
file
The following instructions were performed using Ubuntu 14.04. These steps may be slightly different for other Linux distributions.
user@ubuntu:~$ sudo /opt/NXP/KDS_x.x.x/eclipse/kinetis-design-studio
The KDS IDE version (shown above as x.x.x) should reflect the version installed on your machine, for example, 3.0.0
<install_dir>/tools/eclipse_update
folder and select the KSDK_<version>_Eclipse_Update.zip
file
These steps show how to open and build the platform library project in KDS IDE. The platform library is required by the demo and does not build without it.
Note: The steps required for Linux and Mac OS are identical to those for Windows.
Point to the platform library project for the appropriate device, which can be found using this path:
<install_dir>/lib/ksdk_platform_lib/kds/KL46Z4
To build a demo application, repeat the steps listed in the "Build the Platform Library" section using a demo application project instead of the platform library project. Demo application projects are located in this folder:
<install_dir>/examples/frdmkl46z/demo_apps/<demo_name>/kds
For this example, the path is:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/kds
Note: The steps required for Linux and Mac OS are identical to those for Windows.
The FRDM-KL46Z board comes loaded with the mbed/CMSIS-DAP debug interface from the factory. If you have changed the debug OpenSDA application on your board, visit OpenSDA for information on updating or restoring your board to the factory state.
Mac users must install the J-Link OpenSDA application in order to use the KDS IDE to download and debug their board.
For Linux OS users only, run the following commands in your terminal. These install libudev onto your system, which is required by KDS IDE to launch the debugger
user@ubuntu:~$ sudo apt-get install libudev-dev libudev1
user@ubuntu:~$ sudo ln -s /usr/lib/x86_64-linux-gnu/libudev.so /usr/lib/x86_64-linux-gnu/libudev.so.0
These steps show how to open a demo workspace in IAR Embedded Workbench, how to build the platform library required by the demo, and how to build the demo application. The example used below is for the hello_world demo, but similar steps can be applied to any demo in the KSDK.
Open demo workspace (*.eww file) in:
<install_dir>/examples/frdmkl46z/demo_apps/<demo_name>/iar
After the workspace is open, two projects are shown: one for the KSDK platform library and one for the demo. Also, the platform library project is bold, indicating that it is the active project. The active project can be changed at any time by right clicking on the desired project and selecting "Set as Active" or via the build target drop-down at the top of the workspace browser
When the build is complete, the library (libksdk_platform.a) is generated in one of the following directories, according to the chosen build target:
<install_dir>/lib/ksdk_platform_lib/iar/KL46Z4/debug
<install_dir>/lib/ksdk_platform_lib/iar/KL46Z4/release
The KSDK demo applications are built upon the software building blocks provided in the Kinetis SDK platform library, built in the previous section. If the platform library is not present, the linker displays an error indicating that it cannot find the library.
An easy way to check whether the library is present is to expand the Output folder in the ksdk_platform_lib project. If the platform library binary is not built and present, follow the steps on the previous section to build it. Otherwise, continue with the following steps to build the desired demo application.
If not already done, open the desired demo application workspace (*.eww file). This example's workspace file is located in:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/iar
The FRDM-KL46Z board comes loaded with the mbed/CMSIS-DAP debug interface from the factory. If you have changed the debug OpenSDA application on your board, visit OpenSDA for information on updating or restoring your board to the factory state.
After the MDK tools are installed, Cortex® Microcontroller Software Interface Standard (CMSIS) device packs must be installed to fully support the device from a debug perspective. These packs include things such as memory map information, register definitions and flash programming algorithms. Follow these steps to install the appropriate CMSIS pack.
Note: This process requires an internet connection to successfully complete.
These steps show how to open the demo workspace in µVision, how to build the platform library required by the demo, and how to build the demo application.
Demo workspace files can be found using this path:
<install_dir>/examples/frdmkl46z/demo_apps/<demo_name>/mdk
The workspace file is named <demo_name>.uvmpw. For this specific example, the actual path is:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/mdk/hello_world.uvmpw
After the workspace is open, two projects show up: one for the KSDK platform library, and one for the demo. By default, the demo project is selected as the active project
There are two project configurations (build targets) supported for each KSDK project:
The tool allows selection of the build target based on the active project, so in order to change the configuration for the platform library it must be the active project. Choose the appropriate build target: "Debug" or "Release" from the drop-down menu. For this example, select the "ksdk_platform_lib Debug" configuration
The KSDK demo applications are built upon the software building blocks provided in the Kinetis SDK platform library, built in the previous section. If the platform library is not present, the linker displays an error indicating that it cannot find the library. If the platform library binary is not built and present, follow the steps on the previous section to build it. Otherwise, continue with the following steps to build the desired demo application.
If not already done, open the desired demo application workspace in:
<install_dir>/examples/frdmkl46z/demo_apps/<demo_name>/mdk
The workspace file is named <demo_name>.uvmpw, so for this specific example, the actual path is:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/iar/hello_world.uvmpw
The FRDM-KL46Z board comes loaded with the mbed/CMSIS-DAP debug interface from the factory. If you have changed the debug OpenSDA application on your board, visit OpenSDA for information on updating or restoring your board to the factory state.
This section contains the steps to install the necessary components required to build and run a KSDK demo application with the Arm GCC toolchain, as supported by the Kinetis SDK.
There are many ways to use Arm GCC tools, but this example focuses on a Windows environment. Though not discussed here, GCC tools can also be used with both Linux OS and Mac OSX.
Download and run the installer from GNU Arm Embedded Toolchain . This is the actual toolchain (i.e., compiler, linker, etc.). The GCC toolchain should correspond to the latest supported version, as described in the Kinetis SDK Release Notes.
The Minimalist GNU for Windows (MinGW) development tools provide a set of tools that are not dependent on third party C-Runtime DLLs (such as Cygwin). The build environment used by the KSDK does not utilize the MinGW build tools, but does leverage the base install of both MinGW and MSYS. MSYS provides a basic shell with a Unix-like interface and tools.
Note: The installation path cannot contain any spaces.
Add the appropriate item to the Windows operating system Path environment variable. It can be found under Control Panel → System and Security → System → Advanced System Settings in the "Environment Variables..." section. The path is:
<mingw_install_dir>\bin
Assuming the default installation path, "C:\MinGW", an example is shown below. If the path is not set correctly, the toolchain will not work
Note: If you have C:\MinGW\msys\x.x\bin
in your PATH variable (as required by KSDK 1.0.0),
remove it to ensure that the new GCC build system works correctly.
Create a new system environment variable and name it ARMGCC_DIR. The value of this variable should point to the Arm GCC Embedded tool chain installation path, which, for this example, is:
C:\Program Files (x86)\GNU Tools Arm Embedded\4.8 2014q3
Change the directory of the command window to the platform library directory in the KSDK:
<install_dir>/lib/ksdk_platform_lib/armgcc/KL46Z4
There are two project configurations (build targets) supported for each KSDK project:
There are batch files provided to build both configurations. For this example, the "Debug" target is built and "build_debug.bat" is typed on the command line. If the "Release" target is desired, type the "build_release.bat" instead. Alternatively, if using the command line is not desired, you can double click on the batch files from Windows Explorer
The library (libksdk_platform.a) is generated in one of these directories, according to the build target:
<install_dir>/lib/ksdk_platform_lib/armgcc/KL46Z4/debug
<install_dir>/lib/ksdk_platform_lib/armgcc/KL46Z4/release
KSDK demo applications require that the platform library for the same build target (Debug or Release) is present. Please ensure that you follow the steps in previous section prior to attempting to build a demo application.
To build a demo application, follow these steps.
Change the directory to the demo application project directory, which has a path like this:
<install_dir>/examples/frdmkl46z/demo_apps/<demo_name>/armgcc
For this example, the exact path is:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/armgcc
The GCC tools require a J-Link debug interface. To update the OpenSDA firmware on your board to the latest J-Link app, visit OpenSDA. After installing the J-Link OpenSDA application, download the J-Link driver and software package from SEGGER Downloads .
Change to the directory that contains the demo application output. The output can be found in using one of these paths, depending on the build target selected:
<install_dir>/examples/<board_name>/demo_apps/<demo_name>/armgcc/debug
<install_dir>/examples/
For this example, the path is:
<install_dir>/examples/frdmkl46z/demo_apps/hello_world/armgcc/debug
Something went wrong! Please try again.
Let's create our own project and make a simple SDK-based application. NXP provides an intuitive, simple project generation utility that allows creation of custom projects based on the Kinetis SDK.
Something went wrong! Please try again.
After extracting the ZIP file, open the utility by clicking on the KSDK_Project_Generator executable for your computer's operating system. Point the tool to your SDK installation path, name your project and select the board that it uses as a reference. Click on the Quick Generate button to finish.
Something went wrong! Please try again.
Your new project will be located in
<sdk_install_directory>/examples/frdmkl46z/user_apps
. Open the project in your toolchain of choice by using the same process described in Section 3.2.
Something went wrong! Please try again.
Now, let's make our new project do something other than spin in an infinite loop. The SDK examples provide a board support package (BSP) to do various things specific to the board, including macros and definitions for items such as LEDs, switches and peripheral instances. To keep things simple, let's make the LED blink using the BSP macros.
Update the main() function in your project's main.c file with the following code:
let copy = ""
let copied = ""
let lang = NXP.locale ? NXP.locale : "en"
switch (lang) {
case "en":
copy = "Copy"
copied = "Copied"
break
case "zh":
copy = "复制"
copied = "已复制"
break
case "cn":
copy = "复制"
copied = "已复制"
break
case "ja":
copy = "コピー"
copied = "コピー済"
break
default:
break
}
volatile int delay;
// Configure board specific pin muxing
hardware_init();
// Initialize the UART terminal
dbg_uart_init();
PRINTF("\r\nRunning the myProject project.\n");
// Enable GPIO port for LED1
LED1_EN;
for (;;){
LED1_ON;
delay = 5000000;
while(delay--);
LED1_OFF;
delay = 5000000;
while(delay--);
}
Something went wrong! Please try again.
With the changes made to your main() function, build your application. Remember to build the SDK platform library first, if you did not build any of the other SDK examples in the previous steps. Once the build is complete, download the application to your board.
If you need help figuring out how to build, download or run an application, reference your tool-specific guide from Section 3.2.
Something went wrong! Please try again.
With the application downloaded, you will see the FRDM-KL46Z's green LED blinking. You can also view terminal output using PRINTF.
Something went wrong! Please try again.
Tera Term is a very popular open source terminal emulation application. This program can be used to display information sent from your NXP development platform's virtual serial port.
PuTTY is a popular terminal emulation application. This program can be used to display information sent from your NXP development platform's virtual serial port.
Documents and Videos | Description |
---|---|
AN4507 Using the Kinetis Security and Flash Protection Features | Using the system security and flash protection features on Kinetis MCUs to protect code and data from unauthorized access or modification. |
Documents and Videos | Description |
---|---|
AN12377 Tuning I²C Timing in Target Mode | How to configure the I²C timing of a slave device to meet application needs which apply to Kinetis parts that contain I²C IP instead of LPI2C. |
Several examples, demos and drivers are available within the SDK to help you get started. Some common examples for wired communications are listed below.
Demonstrates basic usage of the on-board accelerometer to implement a bubble level. A bubble level utilizes two axes to visually show deviation from a level plane (0 degrees) on a given axis.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/bubble
Demonstrates how to implement a command line shell application.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/shell
A number of driver examples exist within the SDK including I²C, SPI, LPSCI and UART.
Path: <SDK_PATH>/boards/frdmkl46z/driver_examples
These examples are built on and demonstrate various USB classes and provide jumping off points for your application.
Path: <SDK_PATH>/boards/frdmkl46z/usb_examples
Documents and Videos | Description |
---|---|
AN4631 Using Asynchronous DMA features of Kinetis L Series | How to use the asynchronous DMA of low-power Kinetis L microcontrollers and save power consumption in your application. |
AN4503 Power Management for Kinetis MCUs | When and how to use Kinetis low-power modes. |
AN5088 Power Management for Kinetis L Family | Shows details of each power modes and provides use case examples in the SDK power manage demo. Tips are given for using each of the power modes. |
Several examples, demos and drivers are available within the SDK to help you get started. Some common examples for power management are listed below.
Demonstrates the use of power modes in the SDK.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/power_mode_switch
How to change power modes in the SDK.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/power_manager
Demonstrates the usage of the ADC peripheral while in a low power mode.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/adc16_low_power
Demonstrates the usage of the ADC and DMA peripheral while in a low power mode.
Path: <SDK_PATH>/boards/frdmkl46z/demo_apps/adc16_low_power_async_dma
Documents and Videos | Description |
---|---|
USB Speakers User’s Guide | Explains the features and usage of the USB Speakers reference design. |
Several examples, demos and drivers are available within the SDK to help you get started. Some common examples for audio are listed below.
CMSIS DSP examples are provided to demonstrate CMSIS DSP driver usage in the SDK environment.
Path: <SDK_PATH>/CMSIS/DSP/Examples/ARM
Examples that enumerate a recording device.
Path: <SDK_PATH>/boards/frdmkl46z/usb_examples/usb_device_audio_generator
and <SDK_PATH>/boards/frdmkl46z/usb_examples/usb_device_composite_hid_audio
Documents and Videos | Description |
---|---|
AN12570 Using SLCD controller on K32L2B3 MCU | Describes the usage of the on-chip SLCD controller by enabling an SLCD device. |
Several examples, demos and drivers are available within the SDK to help you get started. A common example for display and graphics is listed below.
How to use the SLCD driver.
Path: <SDK_PATH>/boards/frdmkl46z/driver_examples/slcd
No problem! Your board simply came in the old packaging and has a different out-of-box demo loaded into the flash memory.
You should be seeing the RGB LED toggling between each of the three colors: red, blue and green. It's OK to move onto the next step when you're ready.
Try proceeding to the next steps to get other example applications running on your board. If you still have problems, try contacting us through the NXP Community .
Want to learn more about using the FRDM-KL46Z? Check out our selection of training offerings ranging from online mini tech sessions to hands-on deep-dive training for help.
Documents and Videos | Description |
---|---|
Basic Application Development Using MCUXpresso IDE and MCUXpresso Config Tools | This three-part video series covers the basic interactions between the MCUXpresso IDE and Config Tools when working with either an imported SDK example project or creating a new one. |
Connect with other engineers and get expert advice on designing with the FRDM-KL46Z on one of our community sites.