Audio
Interfaces
Peripherals and Logic
Power Management
Sensors
RF
RFID/NFC
Security and Authentication
Wireless Connectivity
Browse all products
Product Information
Application-Specific Products
NXP Community
Design ideas, demo videos, quality answers. Connect with NXP professionals and other knowledgeable designers ready to help.
Design Resources
Software, documentation, evaluation tools. The resources to build comprehensive solutions and accelerate your time to market.
Access our design resource library
Careers at NXP
We're always looking for passionate and talented people to work with us.
Join our teamJump To
Quick Reference
- Chip Documents
- Board Information
- Software
- Support
Plug It In!
Let's take your USB-KW019032 for a test drive!
1.1 Attach the USB-KW019032 to the PC
1.2 Start the board and run the Out-of-Box Demo
Your USB-KW019032 Power green LED and OpenSDA blue LED should stay ON when you connect the board.
Installing software for the USB-KW019032
In this step, we are going to guide you through the process to get the required software to enable the USB-KW019032 dongle as a IEEE 802.15.4 sniffer. You can also use the USB-KW019032 as a development platform. Select the option you want to accomplish with your USB-KW019032.
Choose a Development Path:
2.1 Download Test Tool for Connectivity Products!
Test Tool for Connectivity Products is a set of graphical user interface modules and applications for testing and deploying Kinetis-W wireless. This tool offers a protocol analyzer for the Kinetis-W family and a Kinetis Firmware Loader.
2.2 Download the driver for your USB-KW019032
Download and install the driver for your USB-KW019032. Before running the driver installer, you MUST have the board plugged in to your PC.
2.3 Download the sniffer application
This step only applies in case you previously downloaded other demo to your board and you require to re-program the board with the snifer application.
You can find this binary and the versions for the EU & JA bands of the sniffer app in the next path after installing the KW01 Connectivity Software v1.0.0:
How to download the sniffer binary file into the KW01.
-
Connect your USB-KW019032 to your PC, MBED (E:) will be detected.
-
Drag and drop the Sniffer_usbkw01_US.bin to MBED (E:) using the MSD capabilities of the CMSIS-DAP.
-
MBED (E:) will blink, disconnect the board, connect it again and the new firmware will start to run in the KW01.
Tera Term Tutorial
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.
- Download Tera Term from SourceForge. After the download, run the installer and then return to this webpage to continue.
- Launch Tera Term. The first time it launches, it will show you the following dialog. Select the serial option. Assuming your board is plugged in, there should be a COM port automatically populated in the list.
- Configure the serial port settings (using the COM port number identified earlier) to 115200 baud rate, 8 data bits, no parity and 1 stop bit. To do this, go to Setup -> Serial Port and change the settings.
- Verify that the connection is open. If connected, Tera Term will show something like below in it's title bar.
- You're ready to go
PuTTY Tutorial
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.
- Download PuTTY using the button below. After the download, run the installer and then return to this webpage to continue.
- Launch PuTTY by either double clicking on the *.exe file you downloaded or from the Start menu, depending on the type of download you selected.
- Configure In the window that launches, select the Serial radio button and enter the COM port number that you determined earlier. Also enter the baud rate, in this case 115200.
- Click Open to open the serial connection. Assuming the board is connected and you entered the correct COM port, the terminal window will open. If the configuration is not correct, PuTTY will alert you.
- You're ready to go
3.1 Configure your sniffer tool
USB-KW019032 comes pre-programmed with a sniffer application. Once all the required software is installed in the PC. You are ready to start sniffing your IEEE 802.15.4 applications.
How to use the Test Tool's Protocol Analyzer?
Protocol Analyzer
-
Connect the USB KW019032 to PC
-
Open the undefinedprotocol analyzer tab.
undefined
undefined
-
undefined
The undefinedProtocol Analyzer should automatically detect the KW01 sniffer. If not, close the tab, unplug the board, plug it back and re-open the tab. If this doesn’t work, try restarting undefinedTest Tool.undefined
undefinedundefinedundefined
undefined
undefined
-
undefined
To start “sniffing” the desired channel, click the arrow down button from undefinedundefinedDevices: KW01 (COMx) Offundefined and select the desired mode and channel.undefined
undefinedundefinedundefined
undefined
undefinedundefined
undefined
undefined
-
undefined
The tab will change to ON meaning that KW01 will "sniff" on the specified channel. To select other channel, click the tab again and it will switch back to Off. Then select a new channel.
undefined
undefined
Each of the Wireless Connectivity Stack comes with a list of demo applications and driver examples ready to be compiled and run
3.1 Select the Connectivity Stack that you want to explore.
SMAC
Browse to the " examples\smac" folder to see the application demos:
3.2 Build, Run and Debug Wireless Connectivity Examples
You probably want to build and debug a demo by yourself. Use the guide below to learn how to build and debug an example application using one of the Wireless Connectivity Stacks provided by NXP.
3.1 Explore the Connectivity Example Codes
Browse to the "examples\hybrid" folder to see the application demos:
If you are interested in running the preprogrammed Connectivity Test Application that comes with your board
3.2 Build, Run and Debug Wireless Connectivity Examples
You probably want to build and debug a demo by yourself. Use the guide below to learn how to build and debug an example application using one of the Wireless Connectivity Stacks provided by NXP.
3.3 How to play with the Bluetooth Low Energy Connectivity Demos?
Kinetis BLE Toolbox comes with mobile applications acting as a BLE central device. The Kinetis BLE Toolbox allows you to play with different sensor applications provided by the MKW40Z Connectivity Software v1.0.0. Currently, Heart Rate Sensor and Beacon applications are supported. More demos will be added soon.
After you successfully installed the Kinetis BLE Toolbox. Follow the next steps to learn how to configure and play with Kinetis BLE Toolbox and Wireless Connectivity Applications.
- Open BLE Tool Box application in your mobile phone. Make sure that Bluetooth radio of the mobile phone is ON.
- Run Heart Rate Sensor application by pressing SW4 button of the FRDM-KW40Z. LED1 will stay ON indicating it is in advertising/discoverable mode.
- BLE Tool Box application will detect BLE Heart Rate Sensors near to the mobile phone as "FSL_BLE_HRS".
- Select the NXP Heart Rate Sensor to connect.
- Kinetis BLE Tool Box Heart Rate application will display data received from the Heart Rate Sensor.
Programming USB-KW40Z with the sniffer application
These steps show how to program USB-KW40Z with the sniffer application. In order to enable USB-KW40Z as a sniffer, you need to program both devices (K22F and KW40).
The next tools are needed to be able to program USB-KW40Z:
Hardware Tools
- J-Link/JTAG Debugger
Software Tools
- J-Link software & documentation pack
It is assumed that user already know how to flash USB-KW40Z. This means that user already went through the "Update Software of the USB-KW40Z QSG" document shown in the USB-KW40Z "Getting Started" page when using this board as a development platform.
1. Locate the sniffer binaries to be downloaded
-
Sniffer binaries files are located in the next path:
\KW40Z_Connectivity_Software_ \ConnSw\tools\binaries 
-
After the binaries are located. Please copy and paste these binary files in the JLink installation path (i.e. "C:\Program Files (x86)\SEGGER\JLink_V502").
NOTE: JLink_V502 folder name might change in the future, it is due to the JLink software version installed, so JLink_V502 or later is required to support KW40Z device
2. Flashing USB-KW40Z as sniffer
-
Make sure that Jlink debugger is connected to the corresponding JTAG MK22F connector (J6) in the USB-KW40Z.
-
Go the JLink installation path, and then open the application "JLink". Next window will be displayed.
-
Call the next instructions in next order:
- unlock kinetis
- device mk22fn512xxx12
- loadbin Sniffer_processing_core_usbkw40z_k22f.bin 0
-
In order to program the KW40Z, please, make sure that Jlink debugger is connected to the corresponding SWD MKW40Z connector (J1) in the USB-KW40Z.
-
Call the next instructions in next order:
- unlock kinetis
- device mkw40z160xxx4
- loadbin Sniffer_radio_core_usbkw40z_kw40z.bin 0
-
A success or "O.K" message should be displayed in the window once the binary file is downloaded.
-
Unplug and plug again the USB-KW40Z to your PC. Now, sniffer application has been programmed to your USB-KW40Z.
IEEE802.15.4 - Build and Run
These steps show how to:
- Build the platform libraries required by the application demo.
- Build the demo application.
- Download and run the demo application.
The example used below is for "MyWirelessApp" application demo, but these steps can be applied to any of the Wireless Connectivity demo applications.
-
Build the platform library
- Open the "MyWirelessAppCoordinator.eww" IAR workspace.
- After the workspace is open, some projects are shown: Some for the KSDK platform libraries and one for the demo application. Build ALL the required KSDK libraries by right clicking on the SDK projects and click on 'Make'.
\KW01_Connectivity_Software_v1.0.0\ConnSw\examples\ieee_802_15_4\MyWirelessApp\Coordinator\usbkw019032_kw01\FreeRTOS\build\iar\ MyWirelessAppCoordinator.eww 
-
Build the application demo
- Select and build the "MyWirelessAppCoordinator - Debug" project.
Note: If you select another project, don't forget to build the required KSDK libraries for that project.
-
Download and Run the application demo
- Connect your USB-KW019032 board to your PC.
- Click on "Download and Debug" icon to flash the board.
- Press "Stop Debugging" button.
-
Open a Terminal Emulator program and open a session to
your USB-KW019032 COM port. Configure the terminal
with these settings:
-
undefined
- 115200 baud rate undefined
- No parity undefined
- 8 data bits undefined
- 1 stop bit
- Press the reset button on the USB-KW01903, the following output will be displayed
- Repeat all steps with "MyWirelessApp" End Device demo application to communicate with this device.
-
Refer to undefined
\KW01_Connectivity_Software_v1.0.0\ConnSw\doc\802154MPDAUG.pdf – "NXP 802.15.4 Media Access Controller (MAC) Demo Applications" document for instructions on how to run all the demo applications.
If you don't see this output, verify your terminal settings and connections.
Connectivity Test Application
The Connectivity Test Application is a SMAC based Demo Application which provides the user with means to test basic transmission-reception functionalities along with several advanced testing features based on the ASP and SMAC APIs.
Configuration
The runtime configuration is performed using shortcut keys which are available in most of the application’s menus. The menus or tests will change their behavior based on what settings are applied.
Connectivity Test Shortcuts Menu
- 't' - brings up the configuration menu for the transmitter in both PER and Range tests.
- 'r' - brings up the configuration menu for the receiver in both PER and Range tests.
- 'q' - increments channel number. [11-26]
- 'w' - decrements channel number. [11-26]
- 'a' - increments output power value.
- 's' - decrements output power value.
- 'n' - increments the length of the payload (used in PER TX and Transmission Control).
- 'm': decrements the length of the payload (used in PER TX and Transmission Control).
- 'k' - increments the CCA threshold for the Carrier Sense test.
- 'l' - decrements the CCA threshold for the Carrier Sense test.
Application usage
The Connectivity Test Application has four main features:
- Continuous Tests: Allows you to test the RF performance of the transceiver for basic transmitter and receiver functionality. The Test Mode application is a collection of modes consisting of the following tests:
- Packet Error Rate: This menu depends on the 'r' or 't' shortcut key. Two boards are required to run this test, one of the boards shall be set in RX and the other in TX.
- Range Test: This menu depends on the 'r' and 't' shortcuts. Two boards are required to run this test; the test is started and stopped only by user intervention and during its execution it will display the link quality for each received packet.
-
Carrier Sense and Transmission Control:
This menu allows the user to choose between two tests:
The Carrier Sense test performs ED continuously until the ED value is above the CCA threshold and then transmit a packet which contains pseudo-random data with the payload size configured using 'n' and 'm' shortcuts.
The Transmission Control test displays a selection menu for number of packets identical with the one in PER TX test and then it prompts the user to enter the inter-packet delay. After that, the application will start sending the selected number of packets with the selected inter-packet delay, using pseudo-random data for the payload with the size configured with 'n' and 'm' shortcuts.
For additional details on how to run the Connectivity Test Application, please refer to the SMAC’s Demonstration Applications User’s Guide.
Bluetooth Low Energy (BLE)
These steps show how to:
-
Build the platform libraries required by the application demo.
-
Build the demo application.
-
Download and run the demo application.
The example used below is for the heart rate sensor demo, but these steps can be applied to any of the Wireless Connectivity demo applications.
1. Build the platform library
-
Open the " heart_rate_sensor.eww " IAR workspace.
\KW40Z_Connectivity_Software_ \ConnSw\examples \bluetooth\heart_rate_sensor\usbkw40z\FreeRTOS\build\iar\ heart_rate_sensor.eww
-
After the workspace is open, some projects are shown: One for the KSDK platform library and one for the demo application. Build ALL the required KSDK libraries by right clicking on the SDK projects and click on 'Make'.
2. Build the application demo
-
Select and build the "heart_rate_sensor - Debug" project.
Note: If you select another project, don’t forget to build the required KSDK libraries for that project.
3. Download and Run the application demo
-
Connect your USB-KW40Z board to your PC.
-
Right click on the "heart_rate_sensor - Debug" project and select "Set as Active"
-
Click on "Download and Debug" icon to flash the board.
-
Press "Stop Debugging" button.
-
Unplug and plug again the USB to your PC. LEDs labeled as D2 and D3 in the USB will start blinking.
-
Press SW1 of the USB-KW40Z, LED D2 will start blinking indicating that the board is in advertising/discoverable mode.
-
Please, see section 3.3 How to play with the Bluetooth Low Energy Connectivity Demos? to learn how to play with the app.
-
Refer to
\KW40Z_Connectivity_Software_ document for instructions on how to run all the demo applications.\ConnSw\doc\BLEDAUG.pdf – "Bluetooth Low Energy (BLE) Demo Applications User's Guide"
Hybrid (IEEE 802.15.4 + BLE)
These steps show how to:
-
Build the platform libraries required by the application demo.
-
Build the demo application.
-
Download and run the demo application.
The example used below is for “dual_mode_demo”, but these steps can be applied to any of the Wireless Connectivity demo applications.
1. Build the platform library
-
Open the " dual_mode_demo.eww " IAR workspace.
\KW40Z_Connectivity_Software_ \ConnSw\examples\hybrid\ ble_802_15_4_dual_mode_demo\usbkw40z\bare_metal\build\iar\ dual_mode_demo.eww
-
After the workspace is open, some projects are shown: One for the KSDK platform library and one for the demo application. Build ALL the required KSDK libraries by right clicking on the SDK projects and click on 'Make'.
2. Build the application demo
-
Select and build the "dual_mode_demo – dual_mode_debug_BM -Debug" project.
Note: If you select another project, don’t forget to build the required KSDK libraries for that project.
3. Download and Run the application demo
-
Connect your FRDM-KW40Z board to your PC
-
Click on "Download and Debug" icon to flash the board.
-
Open a Terminal Emulator program and open a session to your USB-KW40Z COM port.
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Press "Go" button.
-
The following output will be displayed in the serial terminal.
If you don't see this output, verify your terminal settings and connections.
-
Repeat all steps with "MyWirelessApp" End Device demo application to communicate with this device.
-
Use the Kinetis BLE Toolbox mobile application to play with the BLE part of this demo, which correspond to a Heart Rate Sensor.
-
Press SW4 of the FRDM-KW40Z, LED1 will start blinking indicating that the board is in advertising/discoverable mode.
-
Refer to
\KW40Z_Connectivity_Software_1.0.0\ConnSw\doc\BLEDAUG.pdf – "Bluetooth Low Energy (BLE) Demo Applications User's Guide" document for instructions on how to run all the demo applications.
4.1 Create your own project!
NXP provides a tool called "Project Cloner" which will allow you to copy an existing demo to use it as a base for your own development, keeping the original demo app sources for reference.
4.2 Run the Project Cloner
To create a clone of an example project:
-
Launch the Project Cloner executable which is located at:
\ConnSw\tools\project_cloner\project_cloner.exe -
Verify the Project Cloner GUI is displayed.
- Codebase path: Connectivity Stack path folder.
- Clone example app: Demo Applications available for the selected stack.
- Clone configuration: Select from the available development boards, RTOS and Toolchains.
- Cloned app name: Name that the cloned project will have.
- Destination root path: Folder where the cloned project will be created.
-
Select:
- Clone application files only: Clone the app, boards, and platform files in the stack installation – the other files will be linked from the stack installation folder using an environment variable.
- Clone full codebase: Clone the full files, folders and libraries.
- Select an example demo to be cloned and fill the options
- Press "Clone Project" to create the cloned application. A message log will be displayed in the log box as files are being copied. (Destination files will be overwritten if they already exist)
4.3 Open Your Project
Your new project will be located in path specified in the previous step . Open the project in IAR Embedded Workbench for Arm by using the same process described in Section 3.2.
4.4 Start creating your own application
Modify your recently cloned application to start your own design!
For more information about the application and the APIs available, please, look at the "Applications Development Guide".
4.5 Kinetis SDK platform
The Wireless Connectivity Stack platforms make use of the Kinetis SDK low level drivers, take a look into the SDK Demo Applications if you want to add a driver that is not currently used on the Connectivity Demo Applications.
Running a demo using IAR Download PDF
1. Build the platform library
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:
/examples/frdmk64f/demo_apps/ /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.
-
There are two project configurations (build targets) supported for each KSDK project:
- Debug - Compiler optimization is set to low, and debug information is generated for the executable. This target should be selected for development and debug.
- Release - Compiler optimization is set to high, and debug information is not generated. This target should be selected for final application deployment. The tool allows you to select either the Debug or Release configuration on a per-project basis, but since the demo has a dependency on the platform library, whichever configuration is selected for the demo must also be selected for the platform library. Selecting a configuration in the drop-down also makes whichever project and configuration that is selected the active project. For this example, select the "ksdk_platform_lib – Debug" target.
-
Click the "Make" button, highlighted in red below.
-
When the build is complete, the library (libksdk_platform.a) is generated in one of the following directories, according to the chosen build target:
/lib/ksdk_platform_lib/iar/K64F12/debug /lib/ksdk_platform_lib/iar/K64F12/release
2. Build a Demo Application
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 page 1 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:
/examples/frdmk64f/demo_apps/hello_world/iar -
Select the desired build target from the drop-down. For this example, select the "hello_world – Debug" target.
-
To build the demo application, click the "Make" button, highlighted in red below.
-
The build will complete without errors.
3. Run a Demo 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:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Click the "Download and Debug" button to download the application to the target.
-
The application is then downloaded to the target and automatically runs to the main() function.
-
Run the code by clicking the "Go" 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.
SMAC
These steps show how to:
-
Build the platform libraries required by the application demo
-
Build the demo application.
-
Download and run the demo application.
The example used below is for the SMAC Connectivity Test demo, but these steps can be applied to any of the Wireless Connectivity demo applications.
1. Build the platform library
-
Open the " Connectivity_Test.eww " IAR workspace.
\KW40Z_Connectivity_Software_ Connectivity_Test\usbkw40z\FreeRTOS\build\iar\ Connectivity_Test.eww\ConnSw\examples\smac\ 
-
After the workspace is open, some projects are shown: One for the KSDK platform library and one for the demo application. Build ALL the required KSDK libraries by right clicking on the SDK projects and click on 'Make'.
2. Build the application demo
-
Select and build the "Connectivity_Test - Debug" project.
Note: If you select another project, don't forget to build the required KSDK libraries for that project.
3. Download and Run the application demo
-
Connect your FRDM-KW40Z board to your PC.
-
Right click on the "Connectivity_Test – Debug" project and select "Set as Active"
-
Click on "Download and Debug" icon to flash the board.
-
Open a Terminal Emulator program and open a session to your USB-KW40Z COM port.
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Press "Go" button.
-
The following output will be displayed in the serial terminal.
If you don't see this output, verify your terminal settings and connections.
-
Refer to
\KW40Z_Connectivity_Software_ document for instructions on how to run all the demo applications.\ConnSw\doc\MKW40ZSMACDAUG.pdf – "MKW40Z Simple Media AccessController (SMAC) Demonstration Applications"
IEEE 802.15.4
These steps show how to:
-
Build the platform libraries required by the application demo.
-
Build the demo application.
-
Download and run the demo application.
The example used below is for “MyWirelessApp” application demo (Coordinator), but these steps can be applied to any of the Wireless Connectivity demo applications.
1. Build the platform library
-
Open the " MyWirelessAppCoordinator.eww " IAR workspace.
\KW40Z_Connectivity_Software_ \ConnSw\examples \ieee_802_15_4\MyWirelessApp\Coordinator\usbkw40z\FreeRTOS\build\iar\ MyWirelessAppCoordinator.eww
-
After the workspace is open, some projects are shown: One for the KSDK platform library and one for the demo application. Build ALL the required KSDK libraries by right clicking on the SDK projects and click on 'Make'.
2. Build the application demo
-
Select and build the "MyWirelessAppCoordinator - Debug" project.
Note: If you select another project, don’t forget to build the required KSDK libraries for that project.
3. Download and Run the application demo
-
Connect your USB-KW40Z board to your PC.
-
Right click on the "MyWirelessAppCoordinator – Debug" project and select "Set as Active"
-
Click on "Download and Debug" icon to flash the board.
-
Open a Terminal Emulator program and open a session to your USB-KW40Z COM port.
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Press "Go" button.
-
The following output will be displayed in the serial terminal.
If you don't see this output, verify your terminal settings and connections.
-
Now unplug the first board, and plug in the other USB-KW40Z.
-
Program the second USB-KW40Z with the "MyWirelessApp" End Device demo application which can be found at
\KW40Z_Connectivity_Software_ \ConnSw\examples\ieee_802_15_4\MyWirelessApp\EndDevice\usbkw40z\FreeRTOS\build\iar\ MyWirelessAppEndDevice.eww using the same steps as above. -
Close any open terminal windows, then power cycle both boards, and with both boards plugged into your computer, open up a terminal window for each board.
-
Press SW1 on the Coordinator board, and then press SW1 on the board programmed with the EndDevice application, and wait for them to connect.
-
Once connected, type into the terminal of either of the boards, and you will see the text print out on the other board.
-
Refer to
\KW40Z_Connectivity_Software_ document for instructions on how to run all the demo applications.\ConnSw\doc\802154MPDAUG.pdf – "NXP 802.15.4 Media Access Controller (MAC) Demo Applications"
IEEE 802.15.4 Sniffer QSG
These steps show how to:
-
Configure Kinetis Protocol Analyzer Adapter and Wireshark Network Analyzer.
-
Sniff IEEE 802.15.4 wireless applications.
1. Configure Kinetis Protocol Analyzer and Wireshark Network Analyzer
-
Open the "Kinetis Protocol Analyzer Adapter".
-
Make sure, you have USB-KW40Z connected to your PC when opening Kinetis Protocol Analyzer Adapter, it will start looking for Kinetis sniffer hardware. Once USB-KW40Z is detected, KW40Z device will be displayed.
-
Click on the Wireshark icon to open Wireshark Network Protocol Analyzer.
-
Wireshark Network Analyzer will be opened. On the "Capture" option of the main window, select the Local Area Connection that was created by the Kinetis Protocol Analyzer, in this example, Kinetis Protocol Analyzer created "Local Area Connection 2", then click "Start" button.
-
"Capture" window will be opened.
-
Select the desired IEEE 802.15.4 channel to scan in the Kinetis Protocol Analyzer Adapter window. In this guide, we are going to select channel 19 as an example.
-
USB-KW40Z will start to sniff and upcoming data will be displayed in the "Capture" window of the Wireshark Network Protocol Analyzer.
-
Refer to the "Kinetis Protocol Analyzer Adapter User's Guide" for more information about how to enable other features of your USB-KW40Z sniffer. Document can be found in the next path:
\Kinetis Protocol Analyzer Adapter\Kinetis Protocol Analyzer Adapter User's Guide.pdf
BLE Sniffer QSG
These steps show how to:
-
Configure Kinetis Protocol Analyzer Adapter and Wireshark Network Analyzer.
-
Sniff BLE wireless applications.
1. Configure Kinetis Protocol Analyzer and Wireshark Network Analyzer
-
Open the "Kinetis Protocol Analyzer Adapter".
-
Make sure, you have USB-KW40Z connected to your PC when opening Kinetis Protocol Analyzer Adapter, it will start looking for Kinetis sniffer hardware. Once USB-KW40Z is detected, KW40Z device will be displayed.
-
Click on the Wireshark icon to open Wireshark Network Protocol Analyzer.
-
Wireshark Network Analyzer will be opened. On the "Capture" option of the main window, select the Local Area Connection that was created by the Kinetis Protocol Analyzer, in this example, Kinetis Protocol Analyzer created "Local Area Connection 2", then click "Start" button.
-
"Capture" window will be opened.
-
Select the desired advertising channel to scan in the Kinetis Protocol Analyzer Adapter window. In this guide, we are going to select All option to start sniffing on all advertising channels (37, 38 and 39). However, you could select different advertising channels of interest to sniff.
-
Address Filter is selected in this guide, hence, only data upcoming from the specified address will be displayed on the "Capture" window. If you are not interested on following any specific address, you can provide a Hopping interval to sniff any device in the advertising channels.
-
USB-KW40Z will start to sniff and upcoming data will be displayed in the "Capture" window of the Wireshark Network Protocol Analyzer.
-
Refer to the "Kinetis Protocol Analyzer Adapter User's Guide" for more information about how to enable other features of your USB-KW40Z sniffer. Document can be found in the next path:
\Kinetis Protocol Analyzer Adapter\Kinetis Protocol Analyzer Adapter User's Guide.pdf
Programming the USB-KW40Z using J-Link
This document describes how to update or program a new application in the USB-KW40Z using J-Link debugger.
USB-KW40Z contains two MCUs that need to be programmed depending on the desired use case. Hence, USB-KW40Z contains two connectors to program the board. These connectors are shown in the figure 1 as "SWD MKW40Z" and "JTAG MK22F".
Figure 1. USB-KW40Z Hardware
When an application needs to be programmed in the MK22FN512 MCU, "JTAG MK22F" connector is used. Different from this, "SWD MKW40Z" connector is used when programming KW40Z device. In order to be able to program an application to the USB-KW40Z using JLink, ".bin" files are needed because it is the format that JLink application requires in order to be able to program a board. Please, follow the next steps to program USB-KW40Z.
-
Locate the .bin file that need to be programmed in the USB-KW40Z. In this case, this file is the one downloaded from the "Getting Started" web page.
-
Go to JLink installation path. (i.e. " C:\Program Files (x86)\SEGGER\JLink_V502")
-
Copy and paste the ".bin" file into the JLink installation path. Just as an example, in this document, a file called "usb-kw40z_cmsis-dap.bin" for the MK22FN512 MCU will be used.
-
Make sure that Jlink debugger is connected to the corresponding JTAG MK22F connector (J6) in the USB-KW40Z.
Figure 2. JLink debugger connected to JTAG MK22F connector
-
Go the JLink installation path, and then open the application "JLink". Windows shown in figure 3 will be displayed.
Figure 3. JLink application
-
Call the next instructions in next order:
-
unlock kinetis
-
device mk22fn512xxx12
-
loadbin usb-kw40z_cmsis-dap.bin 0
-
-
One important thing to note in the step 6 is the "loadbin" command. The name of the file to be programmed in the MCU is specified in this command. In this case, "usb-kw40z_cmsis-dap.bin" is used as an example for this document.
-
A success or "O.K." message should be displayed in the window once the binary file is downloaded.
-
Disconnect and reconnect the board.
-
Now, an application to the K22F MCU was successfully downloaded.