Jump To
Plug It In!
Let's take your K32W board for a test drive! You have the choice of watching the sequence in a short video or following the detailed actions list below.
1.1 Attach the USB Cable
The green light on the PN7150 NFC control shield will blink once powered.
1.2 Collaterals Package Download
The FTDI driver allows the board to communicate with your PC.
The ZGWUI.exe file is used to setup the ZigBee network. It is available from the JN-AN-1247-ZigBee-3-0-ControlBridge package (folder AN1247\Tools\TestGUI\Source\bin\Debug).
1.3 Start your network
On your PC, open the Zigbee Gateway User Interface (ZGWUI) by double clicking on the executable file ZGWUI.exe.
a. Click on the ‘Settings menu: select the COM port connected to the control bridge and click on ‘OK’.
b. Click on ’Open Port’ menu (button state changes to ‘Close port’).
c. Click on ‘Start NWK’, you can see at the bottom left of the ZGWUI window the raw data and bottom right the received message log.
1.4 Commission the network via NFC
1) Connect the light node to a PC USB port.
2) Tap the NFC antenna of the light node on the NFC antenna of the control bridge:
The green LED on the NFC reader shield blinks more quickly during commissioning and then returns back to its initial state. The node is then commissioned.
3) Repeat step 1 and 2 with the generic switch node.
4) The 2 nodes are present on ‘Discover Devices’ tab of the ZGWUI:
Click on ‘Discover devices’ button, there are 2 short addresses listed standing for the 2 nodes:
In case none or only one short address is present but not 2, redo the commissioning nodes from step 2.
1.5 Controlling the Light from the Generic Switch Node
-
1) Bind the generic switch node to the light node as follows:
- a. Light node: Press and release the USER INTERFACE button. The 3 white LEDs will start to f lash.
-
b. Generic switch node:
- i. Press and release SW1.
-
ii. Hold down the USER INTERFACE button:
- 1. Once LED D1 starts flashing on the generic switch node, press and release the SW2 button.
- 2. Release the USER INTERFACE button only when the light node LEDs stay ON.
- 2) Experiment with the buttons SW1 to SW4 to control the white LEDs on the Light node, as follows:
Get software
2.1 Download MCUXpresso SDK with Connectivity Software
MCUXpresso SDK for the K32W integrates the MCUXpresso Software Development Kit with all the wireless connectivity stacks required to develop your solution with ZigBee/BLE.
Click below to download a pre-configured SDK release for the K32W that includes the wireless connectivity ZigBee/BLE stack for the K32W.
Extract the contents of the download SDK zip and locate the flash programmer installer (SDK_X.X.X_K32W061DK6\tools\JN-SW-4401-DK6-Flash-Programmer). Add the installation location to your system path.
2.2 Install Your Toolchain
NXP offers a complimentary toolchain called MCUXpresso IDE.
2.3 Install Python 3.8
The K32W bootloader requires an image signature to verify the validity of a binary image. The image signing tool requires a Python install to exist on the PC. Download and the latest install Python 3.8 and add it to your system path. Then in a terminal window enter pip install pycryptodome to install the library.
Get software
The K32W Wireless Connectivity Stack comes with a list of demo applications and driver examples ready to be compiled and run.
3.1 Install the SDK
To install the SDK, open MCUXpresso and drag and drop the SDK zip file into the installed SDKs window. Confirm the installation to copy the SDK into the MCUXpresso IDE framework.
3.2 Import SDK examples
From the quickstart panel, select “Import SDK examples”, select K32W061DK6, click next and choose wireless examples. Next, choose “ble_zigbee”, “zigbee_bdt_ed_ble_beacon”, “bm” (Refer to the wireless example’s documentation to find out more information). Then click finish to import the project.
3.3 Build your project
Build your imported project by selecting “Build” in the quickstart panel. Once complete, a binary file (.bin) will be generated inside the project folder under the folder called “Debug” (the name of the selected build configuration.)
3.4 Flash your device
Connect the light or switch DK6 boards to your PC. Open a terminal window in the location of your binary file (Your_MCUxpresso_Workspace\Project_Name\Debug). In your terminal window enter:
DK6Programmer -l
To list your connected COM ports. Identify the COM port of your device. then enter:
DK6Programmer.exe -V 5 -P 1000000 -s <COM_PORT> -e Flash
This will wipe the flash of the board.
Next, provision the image by flashing the PSECTOR with the following command:
DK6Programmer.exe -V5 -s <COM_PORT> -P 1000000 -w PSECT:64@0x160=00400000900401010000000000000000000000000000000000000
0000000000000000000000000000000000000000
00000000000000000000000000000000000
This wireless example requires a second stage bootloader. A pre-built binary for the bootloader is available inside the unzipped SDK. Under SDK_2.6.0_K32W061DK6\boards\k32w061dk6\wireless_examples\framework\ssbl\binary. Flash the bootloader by entering:
Replace <Path to ssbl.bin> with the ssbl.bin in the SDK by dragging and dropping the ssbl.bin from an explorer window into the terminal window. Or enter the path manually. Press enter and then Y.
Flash the application image by entering the following in the terminal window and press enter then y:
DK6Programmer.exe -V5 -s <COM_PORT> -P 1000000 -p FLASH@0x4000=k32w061dk6_zigbee_bdt_ed_ble_beacon_bm.bin
The device will automatically start and try and find a ZigBee network.
3.5 Running the ZigBee app
To setup and join the device. Start the ZGWUI application and connect the control bridge device. Click Settings, select the COM port of the control bridge and open port. Set the CMSK to 12 and click CMSK. Set the Permit join state to FFFC FE and click Permit Join. Finally, click on Start NWK.
The dual mode device should join the network and show it’s device information in the “Received Messages” dialogue box. The LD2 on the dual mode device can now be toggled by sending a toggle command to the device from the “On/Off Cluster” page in ZGWUI. Refer to the JN-AN-1247 documentation for further information.
3.6 Download the IoT Toolbox for your smartphone.
In order to use the Bluetooth Low Energy examples, the NXP IoT Toolbox needs to be installed on a smartphone. This application provides several examples that can be used in conjunction with the connectivity stack to connect your phone to the development board over BLE.
3.7 Running the BLE app.
Open the IoT Toolbox app on your smartphone and select the “Beacons” icon to preview the beacons transmitted by the device.
Running a demo using IAR
The following steps will guide you through compiling, flashing, and running a simple Heart Rate Sensor ZigBee application using the K32W board.
1- Build a ZigBee Application
-
Navigate to the Heart Rate Sensor workspace (located at ''\boards\K32Wcdk\wireless_examples\bluetooth\heart_rate_sensor\freertos\iar)
-
After the workspace is open, select the project.
-
Click the Make button to build the project.
2- Download and Run the application demo
-
Connect the first K32W board to your PC if it is not already. Use the J2 USB connector on the K32W.
-
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:
-
Click the "Download and Debug" button to download the application to the target.
-
The firmware will be downloaded to the board and then you may see the following message. Check the “Don’t show again” checkbox and then click on the Yes button.
-
The debugger will then be started. Click on the “Go” button to begin running the demo.
4- Run the Heart Rate Sensor demo
-
Open the NXP IoT Toolbox application on your mobile device and click on the Heart Rate icon.
-
On the K32W board, press Buton1 to begin ZigBee advertising.
-
In the smartphone app, you should now see the FSL_HRS name. Click on it.
-
The board will then connect to the phone, and you’ll see a graph of the random BPM reading.
Use Keil MDK
1 – Install CMSIS device pack
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.
1. Open the MDK IDE, which is called μVision. In the IDE, select the “Pack Installer” icon.
2. In the Pack Installer window, search for “JN” to bring up the K32W family. Click on the K32W name, and then in the right hand side you’ll see the NXP::K32W_DFP pack. 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 an Example Application
The following steps will guide you through opening the heart_rate_sensor ZigBee demo.
1. Inside the MDK, go to Project->Open Project
2. Navigate to the Heart Rate Sensor workspace (located at
3. To build the demo project, select the "Rebuild" button, highlighted in red.
4. The build will complete without errors.
3 - Run an Example Application
1. Connect the first K32W board to your PC if it is not already. Use the J2 USB connector on the K32W.
2. Click on the Start/Stop Debug Session button to download the code to the board and start debugging it.
3. Run the code by clicking the "Run" button to start the application.
4 - Run the Heart Rate Sensor demo
1. Open the NXP IoT Toolbox application on your mobile device and click on the Heart Rate icon.
2. On the K32W board, press Buton1 to begin ZigBee advertising.
3. In the smartphone app, you should now see the FSL_HRS name. Click on it.
4. The board will then connect to the phone, and you’ll see a graph of the random BPM reading.
Running a demo using MCUXpresso IDE
1- Import the MCUXpresso SDK
- Open up the MCUXpresso IDE
-
Switch to the Installed SDKs view within the MCUXpresso IDE window
- Open Windows Explorer, and drag and drop the K32W SDK directory (installed at into the Installed SDKs view).
-
You will get the following pop-up. Click on
OK to continue the import:
-
The installed SDK will appear in the Installed SDKs view as shown below:
2- Build a ZigBee Application
The following steps will guide you through opening the hybrid example. This project will be loaded to one board, while another project will be loaded on the 2nd board.
-
Find the Quickstart Panel in the lower left hand corner
-
Then click on Import SDK examples(s)…
-
Click on the K32W board to select that you want to import an example that can run on that board, and then click on Next.
-
Now we need to select the project to import. Use the arrow button to expand the wireless_examples category, and then under the bluetooth category expand the heart_rate_sensor project and select the freertos version of project.
This particular project doesn’t make use of the UART, but for projects that do, select the “UART” option for the SDK Debug Console. Then, click on Finish.
-
Now build the project by clicking on the K32Wcdk_wireless_examples_bluetooth_heart_rate_sensor_freertos project name and then in the Quickstart Panel click on Build.
-
You can see the status of the build in the Console tab. If you get a compile error, make sure you had imported two projects at the same.
3- Download and run the application demo
- Connect the first K32W board to your PC if it is not already. Use the J2 USB connector on the K32W.
-
In the Quickstart Panel click on
Debug ‘K32Wcdk_wireless_examples_bluetooth_heart_rate_sensor_freertos’ [Debug]
-
MCUXpresso IDE will probe for connected boards and should find the LPC-LINK2 CMSIS-DAP debug probe that is part of the integrated debug circuit on the K32W. Click on OK to continue.
-
You may get the following error. Hit “OK” to dismiss it.
-
The firmware will be downloaded to the board and the debugger started
4- Run the Heart Rate Sensor demo
-
Open the NXP IoT Toolbox application on your mobile device and click on the Heart Rate icon.
-
On the K32W board, press Buton1 to begin ZigBee advertising.
-
In the smartphone app, you should now see the FSL_HRS name. Click on it.
-
The board will then connect to the phone, and you’ll see a graph of the random BPM reading.
4.1 Sensors
Explore the world with a full assortment of NXP sensor solutions. From accelerometers, pressure sensors, touch sensors, and many more, NXP has a sensor solution for your project. Find out more at nxp.com/sensors
4.2 NFC
Near Field Communication is a simple, intuitive technology that lets you interact securely with the world around you with a simple touch. Learn more about NXP’s NFC solutions at nxp.com/nfc
4.3 Wireless Connectivity Communities
Connect with other engineers and get expert advice on designing with JN MCUs and Wireless Connectivity software. Join the community discussion in the Wireless Connectivity Community
Demo not working?
Did your board come in a box that looks like this?
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.
Still not working?
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.
Running a demo using Keil® MDK/µVision®
1. Install CMSIS device pack
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.
-
Open the MDK IDE, which is called µVision. In the IDE, select the "Pack Installer" icon.
-
In the Pack Installer window, navigate to the section with the Kinetis packs (they are in alphabetical order). The Kinetis packs start with "Keil::Kinetis" and are followed by the MCU family name, for example "Keil::Kinetis_K60_DFP". Because this example uses the FRDM-K64F platform, the K60 family pack is selected. Click on the "Install" button next to the pack. This process requires an internet connection to successfully complete.
-
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.
-
If not already done, open the desired demo application workspace in:
/boards/ / / /mdk The workspace file is named
.uvmpw, so for this specific example, the actual path is: /boards/frdmk64f/demo_apps/hello_world/mdk/hello_world.uvmpw -
To build the demo project, select the "Rebuild" button, highlighted in red.
-
The build will complete without errors.
3. Run an Example Application
The FRDM-K64F 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.
-
Connect the development platform to your PC via USB cable between the "SDAUSB" USB port on the board and the PC USB connector.
-
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:
- 15200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
After the application is properly built, click the "Download" button to download the application to the target.
-
After clicking the "Download" button, the application downloads to the target and should be running. To debug the application, click the "Start/Stop Debug Session" button, highlighted in red.
-
Run the code by clicking the "Run" button to start the application.
-
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.
Proximity Application
The demo application programmed out of the box for the K32W board is the Proximity Reporter demo. It implements a GATT server and the following profile and services.
- Proximity Profile v1.0.1
- Immediate Alert Service v1.0
- TX Power Service v1.0
- Link Loss Service v1.0.1
- Battery Service v1.0
- Device Information Service v1.1
Running the Demo
First you will need to download and install the IoT Toolbox smartphone app from the Google Play or iTunes store.
After powering on the board, press Button1 to begin advertising, and the blinking light should turn red. Open the IoT Toolbox app and click on the Proximity icon.
Look for the FSL_PXR name and tap to connect.
Experiment with the different options on the Proximity screen and move your phone away from and toward the board to see the RSSI values change.
