Getting Started with FRDM-KW41Z
Contents of this document
-
Plug It In
-
Get Software
-
Build, Run
-
Create
Sign in to save your progress. Don't have an account? Create one.
Purchase your FRDM-KW41Z | KW41Z/31Z/21Z | Wireless
1. Plug It In
Let's take your FRDM-KW41Z 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
1.2 Run the Out-of-Box Demo
Your FRDM-KW41Z comes loaded with a demo that flashes the multicolored LEDs when you connect the board. If you do not see the LEDs flashing, first unplug and replug in the board. If that does not resolve the issue, try contacting us through the NXP Community.
2. Get Software
2.1 Choose a Development Path
Kinetis Software Development Kit (SDK) + Integrated Development Environment (IDE)
- True debug support via SWD and JTAG
- High software flexibility
- Full set of peripheral drivers with source
- Application examples and project files
Zephyr™ OS
- A scalable, open source real-time operating system (RTOS)
- Supports multiple hardware architectures
- Optimized for resource constrained devices
- Built with security in mind
Arm mbed Online Development Site
- Online compiler, no SWD, or JTAG debug
- Simple, heavily abstracted programming interface
- Useful but limited drivers with source
- Community-submitted examples
2.2 Installing Software for the FRDM-KW41Z
2.3 Download MCUXpresso SDK with Connectivity Software
MCUXpresso SDK for the FRDM-KW41Z includes all the wireless connectivity stacks required to develop your solution using Thread, IEEE 802.15.4, Generic FSK, and Bluetooth Low Energy.
Click below to download a preconfigured SDK release for the FRDM-KW41Z that includes all the wireless connectivity stacks for the KW41Z.
You can also use the online SDK Builder to create a custom SDK package for the FRDM-KW41Z using the SDK builder.
2.4 Install Your Toolchain
NXP offers a complimentary toolchain called MCUXpresso IDE.
Want to use a different toolchain?
No problem! MCUXpresso SDK connectivity stack software also supports IAR .
2.5 MCUXpresso Config Tools
The MCUXpresso Config Tool is an integrated suite of configuration tools that guides users in creating new MCUXpresso SDK projects, and also provides pin and clock tools to generate initialization C code for custom board support.
3. Build, Run
The KW41Z Wireless Connectivity software comes with a list of demo applications and driver examples ready to be compiled and run for each connectivity stack.
Select the Connectivity Stack that you want to explore.
Build and Run Connectivity Demos on the FRDM-KW41Z
3.1 Explore the Connectivity Example Codes
SMAC
The KW41Z Wireless Connectivity Software package comes with a long list of demo applications for the
SMAC protocol. To see what's available, browse to the 'examples' folder (
If you are interested in running the preprogrammed Connectivity Test Application that comes with your board, Click here.
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 from the Wireless Connectivity Stacks in the MCUXpresso IDE or IAR Embedded Workbench IDE.
GFSK - IAR Embedded Workbench IDE
These steps show how to:
-
Load and build the demo application in IAR Embedded Workbench.
-
Download and run the demo application.
The example used below is for the Generic FSK Connectivity Test demo, but these steps can be applied to any of the Wireless Connectivity demo applications.
1. Load and build the application demo
-
Navigate to the Connectivity Test IAR workspace (located at
\boards\frdmkw41z\wireless_examples\genfsk\connectivity_test_genfsk\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 your FRDM-KW41Z board to your PC.
-
Click on the Download and Debug button (green arrow located on the toolbar).
-
Once the project has loaded, the debugger should stop at main(). Open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port.
Configure the terminal with these settings:- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Click the Go button to resume operation.
-
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
\docs\wireless\GENFSK\Generic FSK Link Layer Quick Start Guide.pdf – "Kinetis MKW41Z Generic FSK Link Layer Software" document for more information on this demo application.
GFSK - 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 FRDM-KW41Z SDK (unzipped) file 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 an Example Application
The following steps will guide you through opening the GenFSK example.
-
Find the Quickstart Panel in the lower left-hand corner
-
Then click on Import SDK examples(s)…
-
Click on the frdmKW41Z board to select that you want to import an example that can run on that board, and then click on Next.
-
Use the arrow button to expand the wireless_examples category, and then under the genfsk category expand the connectivity_test project and select the freertos version of project. To use the UART for printing (instead of the default semihosting), clear the “Enable semihost” checkbox under the project options. Then, click on Next.
-
On the Advanced Settings wizard, clear the checkbox “Redirect SDK “PRINTF” to C library “printf”“ in order to use the MCUXpresso SDK console functions for printing instead of generic C library ones. Then click on Finish.
-
Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.
-
You can see the status of the build in the Console tab.
3. Run an Example Application
-
Now that the project has been compiled, you can now flash it to the board and run it.
-
Make sure that the FRDM-KW41Z board is plugged in, and click in the Quickstart Panel click on Debug ‘frdmkw41z_wireless_examples_genfsk_connectivity_test_freertos’ [Debug]
-
MCUXpresso IDE will probe for connected boards and should find the JLink debug probe that is part of the integrated OpenSDA circuit on the FRDM-KW41Z. Click on OK to continue.
-
You may see the following message if this is your first debug with JLink of the day. Click on the checkbox at the bottom not to display the message again, and then click on Accept
-
The firmware will be downloaded to the board and the debugger started
-
Hit the terminate icon to stop the debugger.
-
Now disconnect the board, and connect the second FRDM-KW41Z board. Follow the same debugger steps to flash the connectivity software to that board so that both boards have the same firmware on them.
-
Now with both boards connected, open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port for each board.
Configure the terminal with these settings:- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Hit the reset button on both boards
-
The following output will be displayed in each of the two serial terminals.
-
Refer to
\docs\wireless\GENFSK\Generic FSK Link Layer Quick Start Guide.pdf – "Kinetis MKW41Z Generic FSK Link Layer Software" document for more information on this demo application.
SMAC - IAR Embedded Workbench IDE
These steps show how to:
- Load and build the demo application in IAR Embedded Workbench.
- 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. Load and build the application demo
-
Navigate to the Connectivity Test IAR workspace (located at
\boards\frdmkw41z\wireless_examples\smac\connectivity_test\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 your FRDM-KW41Z board to your PC.
-
Click on the Download and Debug button (green arrow located on the toolbar).
-
Once the project has loaded, the debugger should stop at main(). Open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port.
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Click the Go button to resume operation.
-
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
\docs\wireless\SMAC\MKW41Z SMAC Demo Applications User's Guide.pdf – "MKW41Z SMAC Demo Applications User's Guide" document for instructions on how to run all the demo applications.
SMAC - 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 FRDM-KW41Z SDK (unzipped) file 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 an Example Application
The following steps will guide you through opening the SMAC example.
-
Find the Quickstart Panel in the lower left-hand corner
-
Then click on Import SDK examples(s)…
-
Click on the frdmKW41Z board to select that you want to import an example that can run on that board, and then click on Next.
-
Use the arrow button to expand the wireless_examples category, and then under the SMAC category expand the connectivity_test project and select the freertos version of project. To use the UART for printing (instead of the default semihosting), clear the “Enable semihost” checkbox under the project options. Then, click on Next.
-
On the Advanced Settings wizard, clear the checkbox “Redirect SDK “PRINTF” to C library “printf”“ in order to use the MCUXpresso SDK console functions for printing instead of generic C library ones. Then click on Finish.
-
Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.
-
You can see the status of the build in the Console tab.
3. Run an Example Application
-
Now that the project has been compiled, you can now flash it to the board and run it.
-
Make sure that the FRDM-KW41Z board is plugged in, and click in the Quickstart Panel click on Debug ‘frdmkw41z_wireless_examples_smac_connectivity_test_freertos’ [Debug]
-
MCUXpresso IDE will probe for connected boards and should find the JLink debug probe that is part of the integrated OpenSDA circuit on the FRDM-KW41Z. Click on OK to continue.
-
You may see the following message if this is your first debug with JLink of the day. Click on the checkbox at the bottom not to display the message again, and then click on Accept
-
The firmware will be downloaded to the board and the debugger started
-
Hit the terminate icon to stop the debugger.
-
Now disconnect the board, and connect the second FRDM-KW41Z board. Follow the same debugger steps to flash the connectivity software to that board so that both boards have the same firmware on them.
-
Now with both boards connected, open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port for each board.
Configure the terminal with these settings:- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Hit the reset button on both boards
-
The following output will be displayed in each of the two serial terminals.
If you don’t see this output, verify your terminal settings and connections.
-
Refer to
\docs\wireless\SMAC\MKW41Z SMAC Demo Applications User's Guide.pdf – "MKW41Z SMAC Demo Applications User's Guide" document for instructions on how to run all the demo applications.
Bluetooth Low Energy + Thread - IAR Embedded Workbench IDE
The following steps will guide you through creating a simple Thread network.. A hybrid Bluetooth Low Energy+Thread project will be loaded onto the 1st board so that the board can be controlled via a Bluetooth smartphone application, while a Thread-only project will be loaded onto the 2nd board and controlled via a serial terminal.
1. Build a Hybrid Bluetooth Low Energy+Thread Application
-
Navigate to the Hybrid Bluetooth Low Energy Thread Router workspace (located at
\boards\frdmkw41z\wireless_examples\hybrid\ble_thread_router_wireless_uart\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 FRDM-KW41Z board to your PC.
-
Click on the Download and Debug button (green arrow located on the toolbar).
-
You may see the following message if this is your first debug with JLink of the day. Click on the checkbox at the bottom not to display the message again, and then click on Accept
-
The firmware will be downloaded to the board and the debugger started.
-
Right now we only want to load the firmware to the first board, so hit the terminate icon to stop the debugger.
3. Download the Thread router application demo to 2nd board
The Hybrid board needs a Thread node to communicate with, so Thread firmware needs to be loaded onto the second board. The Router Eligible End Device project will be loaded onto board #2.
-
Unplug the first FRDM-KW41Z board and plug-in the second FRDM-KW41Z board to your PC
-
Navigate to the Router Eligible End Device project workspace (located at
\boards\frdmkw41z\wireless_examples\thread\router_eligible_device\freertos\iar) 
-
Build and flash the Router Eligible End Device demo using the same steps as before so that the 2nd FRDM-KW41Z has the thread_router firmware loaded onto it.
-
Stop the debugger.
4. Run the hybrid demo
-
Open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port that has the thread_router_eligible project firmware on it (board #2)
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Hit the Reset button on board #2, which can be found near where the USB cable is plugged in. You should see the following on the terminal:
-
Plug-in board #1 that has the Hybrid Bluetooth Low Energy+Thread firmware loaded on it, so that both boards are now connected.
-
Open the Kinetis Bluetooth Low Energy Toolbox application on your mobile device and click on the Thread Shell function.
-
The Kinetis Bluetooth Low Energy Toolbox application should start scanning and find the FRDM-KW41Z board (NXP_THR). Select the NXP_THR device
-
The Kinetis Bluetooth Low Energy Toolbox should now be connected to the device. Using the keyboard on your mobile app that appears, you can type commands to the FRDM-KW41Z device. Type “help” to see the list of possible commands. Outputs from the FRDM-KW41Z board should appear in the app as well.
-
Start a new Thread network by typing “thr create” or by selecting that command in the Shortcuts menu
-
Inside the TeraTerm connectionto the second board (that is just running Thread), join this new network by typing “thr join”.
-
Take note of the ML64 address listed in the terminal for R2 by typing “ifconfig”
-
Inside the smartphone app terminal, type in the command to toggle the LED.
“coap CON POST
/led toggle” 
-
Refer to
\docs\wireless\Thread\Kinetis Thread Stack Demo Applications User's Guide.pdf document for more information on this demo application.
Bluetooth Low Energy + Thread - Running a demo using MCUXpresso IDE
The following steps will guide you through creating a simple Thread network.. A hybrid Bluetooth Low Energy+Thread project will be loaded onto the 1st board so that the board can be controlled via a Bluetooth smartphone application, while a Thread-only project will be loaded onto the 2nd board and controlled via a serial terminal.
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 FRDM-KW41Z SDK (unzipped) file 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 Hybrid Bluetooth Low Energy+Thread 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 frdmKW41Z board to select that you want to import an example that can run on that board, and then click on Next.
-
Use the arrow button to expand the wireless_examples category, and then under the hybrid category expand the ble_thread_router_wireless_uart project and select the freertos version of project. To use the UART for printing (instead of the default semihosting), clear the “Enable semihost” checkbox under the project options. Then, click on Next.
-
On the Advanced Settings wizard, clear the checkbox “Redirect SDK “PRINTF” to C library “printf”“ in order to use the MCUXpresso SDK console functions for printing instead of generic C library ones. Then click on Finish.
-
Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.
-
You can see the status of the build in the Console tab.
3. Download the hybrid application demo to the 1st board
-
Now that the project has been compiled, you can now flash it to the board and run it.
-
Make sure that the FRDM-KW41Z board is plugged in, and click in the Quickstart Panel click on Debug ‘frdmkw41z_wireless_examples_hybrid_ble_thread_router_wireless_uart_freertos’ [Debug]
-
MCUXpresso IDE will probe for connected boards and should find the JLink debug probe that is part of the integrated OpenSDA circuit on the FRDM-KW41Z. Click on OK to continue.
-
You may see the following message if this is your first debug with JLink of the day. Click on the checkbox at the bottom not to display the message again, and then click on Accept
-
The firmware will be downloaded to the board and the debugger started
-
Right now we only want to load the firmware to the first board, so hit the terminate icon to stop the debugger.
4. Download the Thread router application demo to 2nd board
The Hybrid board needs a Thread node to communicate with, so Thread firmware needs to be loaded onto the second board. The Router Eligible End Device project will be loaded onto board #2.
-
Unplug the first FRDM-KW41Z board and plug-in the second FRDM-KW41Z board to your PC
-
Import the wireless_demos->thread->router_eligible_device->freertos demo using the same steps as you did for the hybrid demo.
-
Build and load the end device demo using the same steps as before so that the 2nd FRDM-KW41Z has the thread_router firmware on it.
-
Stop the debugger.
5. Run the hybrid demo
-
Open a Terminal Emulator program and open a session to your FRDM-KW41Z COM port that has the thread_router_eligible project firmware on it (board #2)
Configure the terminal with these settings:
- 115200 baud rate
- No parity
- 8 data bits
- 1 stop bit
-
Hit the Reset button on board #2, which can be found near where the USB cable is plugged in. You should see the following on the terminal:
-
Plug-in board #1 that has the Hybrid Bluetooth Low Energy+Thread firmware loaded on it, so that both boards are now connected.
-
Open the Kinetis Bluetooth Low Energy Toolbox application on your mobile device and click on the Thread Shell function.
-
The Kinetis Bluetooth Low Energy Toolbox application should start scanning and find the FRDM-KW41Z board (NXP_THR). Select the NXP_THR device
-
The Kinetis Bluetooth Low Energy Toolbox should now be connected to the device. Using the keyboard on your mobile app that appears, you may type commands to the FRDM-KW41Z device. Type “help” to see the list of possible commands. Outputs from the FRDM-KW41Z board should appear in the app as well.
-
Start a new Thread network by typing “thr create” or by selecting that command in the Shortcuts menu
-
Inside the TeraTerm connectionto the second board (that is just running Thread), join this new network by typing “thr join”.
-
Take note of the ML64 address listed in the terminal for R2 by typing “ifconfig”
-
Inside the smartphone app terminal, type in the command to toggle the LED.
“coap CON POST/led toggle” 
-
Refer to
\docs\wireless\Thread\Kinetis Thread Stack Demo Applications User's Guide.pdf document for more information on this demo application.
3.1 Explore the Connectivity Example Code
The KW41Z Wireless Connectivity Software package comes with the Connectivity Test demo application
for Generic FSK protocol. To see what's available, browse to the 'examples'
folder (
3.2 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 from the Wireless Connectivity Stacks in the MCUXpresso IDE or IAR Embedded Workbench IDE.
Two accordions left HERE
4. Create
4.1 Clone an Example Project from MCUXpresso SDK
Option A: Use the MCUXpresso IDE to clone an example project.
Use MCUXpresso IDE
- Open the MCUXpresso IDE.
-
Click Import SDK Examples from the QuickStart Panel.
-
Select the FRDM-KW41Z board in the Import Wizard. Then, select Next.
-
Type "LED" into the search bar, and select the "led_output" project
under the GPIO driver example. Then, select Next. This will create a
new standalone copy of this LED project and put it into the
MCUXpresso workspace. To use the UART for printing (instead of the
default semihosting), clear the "Enable semihost" checkbox under the
project options. Then, click on Next.
-
On the Advanced Settings wizard, clear the checkbox "Redirect SDK"
"PRINTF" to C library "printf" in order to use the MCUXpresso SDK
console functions for printing instead of generic C library ones.
Then click on Finish.
-
Click on the "led_output" project in the Project Explorer View and
build, compile, and run the demo as described previously.
- You should see a red LED blinking on the board.
- Terminate the debug session.
Option B: Use the MCUXpresso Config Tool to clone an existing MCUXpresso SDK example for use with third-party IDEs.
USE MCUxpresso Config Tool
- Open the MCUXpresso Config Tool.
-
In the wizard that comes up, browse to the place where the
MCUXpresso SDK was unzipped, and then select the "Clone an example
project" radio button and click on Next.
-
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. Then click on
Next.
-
Then select the directory you want to place the cloned project, give
it a name, and select the IDE to use. Note that only IDEs that were
selected in the online SDK builder when the SDK was built will be
available. Then click on Finish.
- After cloning go to the directory you selected and open up the project for your IDE. Import, compile, and run the project as done in previous sections.
- You should see a red LED blinking on the board.
- Terminate the debug session.
4.2 Use the Pins Tool
Now, let's use the Pins tool that is part of the MCUXpresso Config Tool to show how to add a new GPIO pin to your project to blink an LED.
Use Pins Tool
-
Open MCUXpresso Config Tools
-
The wizard will ask if you want to start development with or without
an SDK. Choose to start development with the SDK and that we want to
create a new configuration. Use the "Browse" button to navigate to
the location of your unzipped SDK installation.
-
Select the SDK top-level folder from your file system. Select OK.
-
The wizard asks to create a new configuration or clone an example
project. We will Create a new configuration that will be based on
the "led_output" project settings from the SDK. Select Next to
continue.
-
Search for the led_output example by typing "LED" in the search bar.
Select the led_output example and press Finish.
-
Open the pins tool by selecting Tools->Pins from the toolbar.
-
The pins tool should now display the pin configuration for the
led_output project.
-
In the Pins view, click the "Show Routed/All Pins" checkbox to see
all the routed pins. Routed pins have a check in a green box next to
the pin name. The functions selected for each routed pin are
highlighted in green in the table.
- In the current configuration, PTC1 is routed as a GPIO to toggle the red LED. Let's disable PTC1, and change the MUX setting of PTA18 to use its GPIO functionality to drive the blue LED
-
Disable PTC1 (Red LED) as a GPIO by clicking the "PTC1" field under
the GPIO column. The pin will then be disabled (pin will no longer
have check in box) and thus disappear from the list.
-
Now, route PTA18 as a GPIO. First, deselect the "Show Routed
All/Pins" so that all the pins are displayed again. Then, search
PTA18 in the pins view. Finally, click the box under the GPIO
column. The box will highlight in green, and a check will appear
next to the pin.
-
The updated view will appear as below once you clear the filtered
text. Note that PTB21 also appears in the Routed Pins tab and PTB22
has been removed. The pin_mux.c file has been updated to reflect the
change as well.
-
Now export the pin_mux.c and pin_mux.h files by clicking on the Sources tab on the right side to get to the Sources view, and selecting the export icon.
-
Select the directory to export the pin_mux.c and pin_mux.h files. In this example export to the "board" folder in the led_output project in the workspace that was created in the previous section.
(i.e. C:\nxp_workspace\frdmkw41z_driver_examples_gpio_led_output\board). Select Finish.
-
Click Yes to replace the existing pin_mux.c and pin_mux.h files.
-
We'll use MCUXpresso IDE for the rest of the instructions but the
same steps can be done in other 3rd party IDEs. Under the
"led_output" project, double-click the gpio_led_output.c file in the
source folder to display the file in the editor. Notice that the
macros used in the GPIO driver functions refer to the BOARD_LED
(i.e. red LED).
-
Change the defines for BOARD_LED_GPIO to the "GPIOA" and the
BOARD_LED_GPIO_PIN to "18"
- Build and download the project as done in the previous section.
- Run the application. You should now see the blue LED blinking!
- Terminate the debug session.
4.3 Use the Clocks Tool
Next use the Clocks tool that is part of the MCUXpresso Config Tool to change the clock settings and change the rate that the LED blinks.
Use the Clocks Tool
-
Open MCUXpresso Config Tools
-
The wizard will ask if you want to start development with or without
an SDK. Choose to start development with the SDK and that we want to
create a new configuration. Use the "Browse" button to navigate to
the location of your unzipped SDK installation.
-
Select the SDK top-level folder from your file system. Select OK.
-
The wizard asks to create a new configuration or clone an example
project. We will Create a new configuration that will be based on
the "led_output" project settings from the SDK. Select Next to
continue.
-
Search for the led_output example by typing "LED" in the search bar.
Select the led_output example and press Finish.
-
Open the pins tool by selecting Tools->Pins from the toolbar.
-
The pins tool should now display the pin configuration for the
led_output project.
-
In the Pins view, click the "Show Routed/All Pins" checkbox to see
all the routed pins. Routed pins have a check in a green box next to
the pin name. The functions selected for each routed pin are
highlighted in green in the table.
- In the current configuration, PTC1 is routed as a GPIO to toggle the red LED. Let's disable PTC1, and change the MUX setting of PTA18 to use its GPIO functionality to drive the blue LED
-
Disable PTC1 (Red LED) as a GPIO by clicking the "PTC1" field under
the GPIO column. The pin will then be disabled (pin will no longer
have check in box) and thus disappear from the list.
-
Now, route PTA18 as a GPIO. First, deselect the "Show Routed
All/Pins" so that all the pins are displayed again. Then, search
PTA18 in the pins view. Finally, click the box under the GPIO
column. The box will highlight in green, and a check will appear
next to the pin.
-
The updated view will appear as below once you clear the filtered
text. Note that PTB21 also appears in the Routed Pins tab and PTB22
has been removed. The pin_mux.c file has been updated to reflect the
change as well.
-
Now export the pin_mux.c and pin_mux.h files by clicking on the Sources tab on the right side to get to the Sources view, and selecting the export icon.
-
Select the directory to export the pin_mux.c and pin_mux.h files. In this example export to the "board" folder in the led_output project in the workspace that was created in the previous section.
(i.e. C:\nxp_workspace\frdmkw41z_driver_examples_gpio_led_output\board). Select Finish.
-
Click Yes to replace the existing pin_mux.c and pin_mux.h files.
-
We'll use MCUXpresso IDE for the rest of the instructions but the
same steps can be done in other 3rd party IDEs. Under the
"led_output" project, double-click the gpio_led_output.c file in the
source folder to display the file in the editor. Notice that the
macros used in the GPIO driver functions refer to the BOARD_LED
(i.e. red LED).
-
Change the defines for BOARD_LED_GPIO to the "GPIOA" and the
BOARD_LED_GPIO_PIN to "18"
- Build and download the project as done in the previous section.
- Run the application. You should now see the blue LED blinking!
- Terminate the debug session.
4.4 Success
With the application modified, you will see the FRDM-KW41Z's blue LED slowly blinking. You can also view terminal output using the terminal program.
Projects and Tutorials
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 its 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
Design Resources
Learn
IoT Modular Gateway
The NXP modular IoT Gateway reference design enables large node networks (LNNs) with preintegrated, tested, and RF certified support for a wide array of wireless communications protocols including: Thread, ZigBee, and Wi-Fi. This range of capability allows developers to easily build gateways based on this solution, using their choice of wireless protocols for end-to-end wireless communications in LNN configurations with supporting cloud options such as Amazon Web Services (AWS).
Thread
Thread is an IPv6-based mesh networking protocol developed by industry leading technology companies, like NXP®, for connecting products around the home and in buildings to each other, to the internet and to the cloud. Thread networks are simple to install, highly secure, scalable to hundreds of devices, and developed to run on low-power IEEE 802.15.4 chipsets. Thread Networking Protocol and Thread Group.
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 Sensors
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 NFC - Near Field Communication
Kinetis and Wireless Connectivity Communities
Connect with other engineers and get expert advice on designing with Kinetis MCUs and Wireless Connectivity software. Join the community discussion in one of our two dedicated communities: Kinetis MCU Community or Wireless Connectivity Community
On this page
- 2.1
Choose a Development Path
- 2.2
Installing Software for the FRDM-KW41Z
- 2.3
Download MCUXpresso SDK with Connectivity Software
- 2.4
Install Your Toolchain
- 2.5
MCUXpresso Config Tools
- 3.1
Explore the Connectivity Example Code
- 3.2
3.2 Build, Run, and Debug Wireless Connectivity Examples