Get Started with the FRDM-K32L3A6

1. Install device pack

After the MDK tools are installed, Keil 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.

1. Open the MDK IDE, which is called µVision. In the IDE, select the "Pack Installer" icon.

   

2. In the Pack Installer window, find the K32L3A6 device pack in the Devices list on the left (they are in alphabetical order). Select the K32L3A60VPJ1A. The NXP packs start with “NXP::" and are followed by the MCU family name, for example "NXP::K32L3A60_DFP". Because this example uses the FRDM-K32L3A6 platform, the K32L3A6 family pack is selected. Click on the "Install" button next to the pack. This process requires an internet connection to successfully complete.

   

3. After the installation finishes, close the Pack Installer window and return to the µVision IDE.

2. Build the Example Application

The following steps will guide you through opening the hello_world application. These steps may change slightly for other example applications as some of these applications may have additional layers of folders in their path.

1. If not already done, open the desired demo application workspace in:

   <install_dir>/boards/<sdk_board_name>/<example_type>/<application_name>/mdk

   The workspace file is named <application_name>.uvmpw, so for this specific example, the actual path is:

   <install_dir>/boards/frdmk32l3a6/demo_apps/hello_world/mdk/hello_world.uvmpw

2. To build the demo project, select the "Rebuild" button, highlighted in red.

   

3. The build will complete without errors.

3. Run an Example Application

The FRDM-K32L3A6 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 http://www.nxp.com/opensda for information on updating or restoring your board to the factory state.

1. Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.

2. Open the terminal application on the PC (such as PuTTY or TeraTerm) and connect to the debug COM port you determined earlier. Configure the terminal with these settings:

   • 15,200 baud rate
   • No parity
   • Eight data bits
   • One stop bit

3. After the application is properly built, click the "Start/Stop Debug Session" button to download the application to the target and start debugging.

   

4. Run the code by clicking the "Run" button to start the application.

   

5. The hello_world application is now running and a banner is displayed on the terminal. If this is not the case, check your terminal settings and connections.

   

1. Import the MCUXpresso SDK.

1. Open up the MCUXpresso IDE.
2. Switch to the Installed SDKs view within the MCUXpresso IDE window.
   
3. Open Windows Explorer, and drag and drop the FRDM-K32L3A6 SDK file into the Installed SDKs view.
4. You will get the following pop-up. Click on OK to continue the import:
   
5. The installed SDK will appear in the Installed SDKs view as shown below:
   

2. Build an Example Application.

The following steps will guide you through opening the hello_world example.

1. Find the Quickstart Panel in the lower left-hand corner

   

2. Then click on Import SDK examples(s)…

   

3. Click on the frdmk32l3a6 board to select that you want to import an example that can run on that board, and then click on Next.

   

4. Use the arrow button to expand the demo_apps category, and then click the checkbox next to hello_world to select that project. To use the UART for printing (instead of the default semihosting), select UART in the SDK Debug Console options. Then, click on Finish

   

5. Now build the project by clicking on the project name and then click on the Build icon.

   

6. You can see the status of the build in the Console tab.

   

3. Run an Example Application.

1. Now that the project has been compiled, you can now flash it to the board and run it.
2. Make sure that the FRDM-K32L3A6 board is plugged in, and click on Debug in the Quickstart Panel
   

3. MCUXpresso IDE will probe for connected boards and should find the MBED CMSIS-DAP debug probe that is part of the integrated OpenSDA circuit on the FRDM-K32L3A6. Click on OK to continue.

   

4. The firmware will be downloaded to the board and the debugger started.

   

5. Open up a terminal program and connect to the COM port the board enumerated as. Use 115,200 baud 8 data bits, no parity, and 1 stop bit.

6. Start the application by clicking the "Resume" button:

   

7. The hello_world application is now running and a banner is displayed on the terminal. If this is not the case, check your terminal settings and connections.

   

8. Use the controls in the menu bar to pause, step into, and step over instructions, and then stop the debugging session by click on the Terminate icon:

   

1. Set Up Toolchain

This section contains the steps to install the necessary components required to build and run an MCUXpresso SDK demo application with the ARM GCC toolchain, as supported by the MCUXpresso 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.

Install GCC Arm Embedded Toolchain

Download and run the installer from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads. 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.

Install MinGW

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.

1. Download the latest MinGW mingw-get-setup installer from sourceforge.net/projects/mingw/files/Installer/.

2. Run the installer. The recommended installation path is C:\MinGW, however, you may install to any location.

NOTE

The installation path cannot contain any spaces.

3. Ensure that the "mingw32-base" and "msys-base" are selected under Basic Setup.

   

4. Click "Apply Changes" in the "Installation" menu and follow the remaining instructions to complete the installation.

   

5. 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 does 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.

   

Add a New Environment Variable for ARMGCC_DIR

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.9 2015q3

for the exact path name of your installation.


Install CMake

1. Download CMake 3.0.x from www.cmake.org/cmake/resources/software.html.

2. Install CMake, ensuring that the option "Add CMake to system PATH" is selected when installing. It's up to the user to select whether it's installed into the PATH for all users or just the current user. In this example, the assumption is that it's installed for all users.

   

3. Follow the remaining instructions of the installer.

4. You may need to reboot your system for the PATH changes to take effect.

2. Build an Example Application

To build an example application, follow these steps.

1. If not already running, open a GCC Arm Embedded tool chain command window. To launch the window, from the Windows operating system Start menu, go to “Programs -> GNU Tools Arm Embedded <version>” and select “GCC Command Prompt”.

   

2. Change the directory to the example application project directory, which has a path like this:

   <install_dir>/boards/<board_name>/<example_type>/<application_name>/armgcc

   For this guide, the exact path is:

   <install_dir>/boards/frdmk32l3a6/demo_apps/hello_world/armgcc

3. Type “build_debug.bat” on the command line or double click on the "build_debug.bat" file in Windows operating system Explorer to perform the build. The output is shown in this figure:

   

3. Run an Example Application.

The GCC tools require a J-Link debug interface. To update the OpenSDA firmware on your board to the latest J-Link app, visit www.nxp.com/opensda. After installing the J-Link OpenSDA application, download the J-Link driver and software package from www.segger.com/downloads.html.

1. Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.

2. Open the terminal application on the PC (such as PuTTY or TeraTerm) and connect to the debug COM port you determined earlier. Configure the terminal with these settings:

   • 15,200 baud rate
   • No parity
   • Eight data bits
   • One stop bit

3. Open the J-Link GDB Server application. Assuming the J-Link software is installed, the application can be launched by going to the Windows operating system Start menu and selecting "Programs -> SEGGER -> J-Link <version> J-Link GDB Server".

4. Modify the settings as shown below. The target device selection chosen for this example is the “K32L3Axxxxxxxx_M4” and use the SWD interface.

   

5. After it is connected, the screen should resemble this figure:

   

6. If not already running, open a GCC Arm Embedded tool chain command window. To launch the window, from the Windows operating system Start menu, go to "Programs -> GNU Tools Arm Embedded <version>" and select "GCC Command Prompt".

   

7. 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>/boards/<board_name>/<example_type>/<application_name>/armgcc/debug

   <install_dir>/boards/<board_name>/<example_type>/<application_name>/armgcc/release

   For this guide, the path is:

   <install_dir>/boards/frdmk32l3a6/demo_apps/hello_world/armgcc/debug

8. Run the command "arm-none-eabi-gdb.exe <demo_name>.elf". For this example, it is "hello_world_demo_cm4.elf".

   

9. Run these commands:

   • "target remote localhost: 2331"
   • "monitor reset"
   • "monitor halt"
   • "load"
   • "monitor reset"

10. The application is now downloaded and halted at the reset vector. Execute the "monitor go" command to start the example application.

    The hello_world application is now running and a banner is displayed in the terminal window.

    

1. Open the MCUXpresso IDE.
2. Click Import SDK Examples from the QuickStart Panel.
3. Click on the FRDM-K32L3A6 board to select that you want to import an example that can run on that board, and then click on Next.
4. Type “LED” into the search bar, and select the “gpio_led_output” project under the GPIO driver example. This particular project doesn’t make use of the UART, but for projects that do, make sure to select the “UART” option for the SDK Debug Console Then, click on Finish.
5. Click on the “frdmk32l3a6_gpio_led_output” project in the Project Explorer View and build, compile, and run the demo as described previously.
6. You should see the LEDs blinking on the board.
7. Terminate the debug session.

1. Open the MCUXpresso Config Tool.
2. In the wizard that comes up, browse to the place where the MCUXpresso SDK was unzipped, and then select the “Clone SDK example and create a new configuration” radio button and click on Next.
3. On the next screen, select the location of the MCUXpresso SDK that you had unzipped earlier. Then select the IDE that is being used. Then select the project to clone. For this example we want to use the LED project. You can filter for this by typing “led” in the filter box and then selecting the “gpio_led_output” project. You can then also specify where to clone the project to. Then click on Finish.
4. You should see a red LED blinking on the board.
5. Terminate the debug session.
6. Go back to the MCUXpresso Config Tools program and continue on with the next section to learn how to use the Pins tool.

If using MCUXpresso IDE, open the pins tool by left clicking on the arrow next to the “MCUXpresso Config Tools” icon and then “Open Pins”

If using the MCUXpresso Config Tools program and if the pins tool is not already open, then select the project that you had cloned and then And open the pins tool by selecting Tools->Pins from the toolbar.

1. The pins tool should now display the pin configuration for the led_output project.
2. In the Pins view, look at the Routed Pins box to see all the routed pins for the project. You can see the peripheral the pin is associated with and the signal name, and the pin options.
3. In the current configuration, PTA24 is routed as a GPIO to toggle the red LED. For this example we’ll use PTA22 instead to drive the blue LED.
4. First in the Pins screen, scroll down until you see PTA24. Click the checkbox next to it to unselect it.
5. You’ll see the following dialog box come up. Click next to PTB22 to unselect it and then click on Done.
6. Then click on the checkbox next to PTA22 to use that pin and select the PTA22 GPIO pin.
7. PTA22 already has a defined identifier (i.e. “LED_BLUE”) set up for the FRDM-K32L3A6 for the led_output example configuration. Let’s change the identifier to “MY_LED” next to PTA22 in the Pins table.
8. Now it’s time to implement these changes into the GPIO project by exporting the new updated pin_mux.c and pin_mux.h files that are generated by the Pins tool. Click on Update Code in the menu bar.
9. The screen that pops up will show the files that are changing and you can click on “diff” to see the difference between the current file and the new file generated by the Pins tool. Click on “OK” to overwrite the new files into your project.

NOTE

The clocks and peripherals files may also be tagged as being updated since the header has been changed.


10. Now inside the IDE, open up the gpio_led_ouput.c file
11. Change two #defines to tell the GPIO project to use the new PTA22 pin. Use the #defines that are found in pin_mux.h where were created by the Pins Tool.
#define BOARD_LED_GPIO BOARD_INITPINS_MY_LED_GPIO
#define BOARD_LED_GPIO_PIN BOARD_INITPINS_MY_LED_PIN
12. Now build and run the project as before. You will now see the blue LED blink!

If using MCUXpresso IDE, open the pins tool by left clicking on the arrow next to the “MCUXpresso Config Tools” icon and then “Open Clocks”

If using the MCUXpresso Config Tools program and the pins tool is not already open, then select the project that you had cloned and then

And open the pins tool by selecting Tools->Clocks from the toolbar.

1. The clock configuration for the “led_output” project will appear in the clocks tool:
2. Switch to the Clocks Diagram view by clicking the tab in the upper left corner.
3. Change the core clock frequency by clicking in the Core Clock field and typing “12”. You’ll see all the other clock values automatically change as well to adjust to this slower speed. It will look like this when done:
4. Now it’s time to implement these changes into the GPIO project by exporting the new updated clock_config.c and clock_config.h files that are generated by the Pins tool. Click on Update Code in the menu bar.
5. The screen that pops up will show the files that are changing and you can click on “diff” to see the difference between the current file and the new file generated by the Pins tool. Click on “OK” to overwrite the new files into your project.

NOTE

The pins and peripherals files may also be tagged as being updated since the header has been changed.


6. Now open the led project in your IDE, and build, download, and run the project as you did before.
7. The blue LED should now be blinking at a much slower rate!