Getting Started with the FRDM-KW36

GFSK - IAR Embedded Workbench IDE

These steps show how to:

1. Load and build the demo application in IAR Embedded Workbench.

2. 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.

Load and build the application demo

1. Navigate to the Connectivity Test IAR workspace located at <install_dir> </install_dir>

2. After the workspace is open, select the project.

   

3. Click the Make button to build the project.

   

Download and Run the application demo

1. Connect your FRDM-KW36 board to your PC.

2. Click on the Download and Debug button (green arrow located on the toolbar).

   

3. Once the project has loaded, the debugger should stop at main(). Open a Terminal Emulator program and open a session to your FRDM-KW36 COM port.
   Configure the terminal with these settings:

   • 115200 baud rate
   • No parity
   • 8 data bits
   • 1 stop bit

4. Click the Go button to resume operation.

   

5. The following output will be displayed in the serial terminal.

   

   If you don't see this output, verify your terminal settings and connections.

6. Refer to “ <install_dir>\docs\wireless\GENFSK\Generic FSK Link Layer Quick Start Guide.pdf – "Kinetis MKW35A/MKW36A/MKW35Z/MKW36Z Generic FSK Link Layer Software" document for more information on this demo application. </install_dir>

GFSK - Running a demo using MCUXpresso IDE

These steps show how to:

1. Load and build the demo application in MCUXpresso IDE.

2. 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.

Load and build the application demo

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-KW36 SDK (unzipped) 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:

   

Build an Example Application

The following steps will guide you through opening the Generic FSK example.

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

   

2. Then click on Import SDK examples(s)

   

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

   

4. In the search text box, type “conn_test” to filter the example projects. Use the arrow button to expand the list and locate the “conn_test” project (wireless_examples → genfsk → conn_test), then, select the freertos version of the project and click “Finish”.

   

5. Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.

   

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

   

7. Now that the project has been compiled, you can now flash it to the board and run it.

8. Make sure the FRDM-KW36 board is plugged in, and click in the Quickstart Panel click on Debug.

   

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

   

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

    

11. Once the project has loaded, the debugger should stop at main(). Open a Terminal Emulator program and open a session to your FRDM-KW36 COM port. Configure the terminal with these settings:

    • 115200 baud rate
    • No parity
    • 8 data bits
    • 1 stop bit.

12. Click the “Run” button to resume operation.

    

13. The following output will be displayed in the serial terminal.

    
Refer to “ <install_dir>\docs\wireless\GENFSK\Generic FSK Link Layer Quick Start Guide.pdf” – "Kinetis MKW35A/MKW36A/MKW35Z/MKW36Z Generic FSK Link Layer Software" document for more information on this demo application.<install_dir>

Bluetooth LE - Running a demo using MCUXpresso IDE

These steps show how to:

1. Load and build the demo application in MCUXpresso IDE.

2. 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.

Load and build the application demo

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-KW36 SDK (unzipped) 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:

   

Build an Example Application

The following steps will guide you through opening and running the Heart Rate Sensor example.

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

   

2. Then click on Import SDK examples(s)

   

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

   

4. In the search text box, type “hrs” to filter the example projects. Use the arrow button to expand the list and locate the “hrs” project (wireless_examples → bluetooth → hrs), then, select the freertos version of the project and click “Finish”.

   

5. Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.

   

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

7. Now that the project has been compiled, you can now flash it to the board and run it.

8. Make sure the FRDM-KW36 board is plugged in, and click in the Quickstart Panel click on Debug.

   

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

   

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

    

11. Click the “Stop” button to stop debugging the application. The Heart Rate Sensor demo enables low power by default, so, the debug pins are disabled to save power.

    

12. Open the NXP IoT Toolbox application on your mobile device and click on the “Heart Rate”.

    

13. Reset the FRDM-KW36 by pressing “SW1” button and press “SW3” to start advertising. Verify that the device is listed in the IoT Toolbox as shown in the next picture.

    

14. Select the listed device to make a connection. The IoT Toolbox should display the information of the Heart Rate Sensor.

    

15. Refer to “ <sdk_dir>\docs\wireless\Bluetooth\BLE Demo Applications User's Guide.pdf” – " Bluetooth® Low Energy Demo Applications User’s Guide" document for more information on this demo application. <sdk_dir>

These steps show how to:

1. Load and build the demo application in MCUXpresso IDE.

2. 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.

Load and build the application demo

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-KW36 SDK (unzipped) 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:

   

Build an Example Application

The following steps will guide you through opening and running the Heart Rate Sensor example.

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

   

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

   

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

   

4. In the search text box, type “hrs” to filter the example projects. Use the arrow button to expand the list and locate the “hrs” project (wireless_examples → bluetooth → hrs), then, select the freertos version of the project and click “Finish”.

   

5. Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.

   

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

7. Now that the project has been compiled, you can now flash it to the board and run it.

8. Make sure the FRDM-KW36 board is plugged in, and click in the Quickstart Panel click on Debug.

   

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

   

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

    

11. Click the “Stop” button to stop debugging the application. The Heart Rate Sensor demo enables low power by default, so, the debug pins are disabled to save power.

    

12. Open the NXP IoT Toolbox application on your mobile device and click on the “Heart Rate”.

    

13. Reset the FRDM-KW36 by pressing “SW1” button and press “SW3” to start advertising. Verify that the device is listed in the IoT Toolbox as shown in the next picture.

    

14. Select the listed device to make a connection. The IoT Toolbox should display the information of the Heart Rate Sensor.

    

15. Refer to “ <sdk_dir>\docs\wireless\Bluetooth\BLE Demo Applications User's Guide.pdf” – " Bluetooth® Low Energy Demo Applications User’s Guide" document for more information on this demo application. <sdk_dir>

Hybrid (Gen FSK + Bluetooth LE) - Running a demo using IAR Embedded Workbench IDE

These steps show how to:

1. Load and build the demo application in IAR Embedded Workbench.

2. Download and run the demo application.

The example used below is for the Hybrid Bluetooth LE Generic FSK Advertising demo, but these steps can be applied to any of the Wireless Connectivity demo applications. This demo requires two FRDM-KW36 boards. One known as “Transmitter” which transmits Bluetooth LE and Generic FSK packets. The other known as a “Receiver” which receives Bluetooth LE and Generic FSK packets.

Load and build the application demo

1. Navigate to the Hybrid Bluetooth LE Generic FSK Advertising demo (ble_gfsk_adv) IAR workspace located the next path:“ <sdk_dir> \boards\frdmkw36\wireless_examples\hybrid\ble_gfsk_adv\freertos\iar” <sdk_dir>

   

2. After the workspace is open, select the project.

   

3. Click the Make button to build the project.

   

Download and Run the application demo

1. Connect the first FRDM-KW36 board to your PC.

2. Click on the Download and Debug button (green arrow located on the toolbar).

   

3. Once the project has loaded, the debugger should stop at main().

4. Click the “Stop” button to stop debugging the application. At this point, we have programmed one board.

   

5. Connect the second FRDM-KW36 board to your PC and download the same project as in the previous board.

   

6. At this point, you have programmed two FRDM-KW36 boards with the ble_gfsk_adv demo.

7. Open a Terminal Emulator program and open a session to one of the FRDM-KW36 COM ports.

   • 115200 baud rate
   • No parity
   • 8 data bits
   • 1 stop bit

8. Open a second Terminal Emulator program and open a session to the other FRDM-KW36 COM port using the same port configuration.

9. Press the reset button on both boards.

10. The next menu should be displayed in both terminals.

    

11. Board 1: Start transmitting advertisements. Press SW2 button in one of the FRDM-KW36 boards. The serial terminal connected to the board should display the following text

    This will be the “transmitter” board.

12. Board 2: Start scanning packets. Press SW3 button on the second FRDM-KW36 board. This is to set the board in receiver or scanning mode. Then, press SW2 button to start the application and display the received packets in the serial terminal connected to this board. Bluetooth LE and Generic FSK packets should be displayed as shown in the next image.

13. Refer to “ <sdk_dir>docs\wireless\Bluetooth\BLE Demo Applications User's Guide.pdf”– " Bluetooth® Low Energy Demo Applications User’s Guide" document for detailed instructions about the available Bluetooth LE demo applications.<sdk_dir>

Hybrid (Gen FSK + Bluetooth LE) - Running a demo using MCUXpresso IDE

These steps show how to:

1. Load and build the demo application in MCUXpresso IDE.

2. Download and run the demo application.

The example used below is for the Hybrid Bluetooth LE Generic FSK Advertising demo, but these steps can be applied to any of the Wireless Connectivity demo applications. This demo requires two FRDM-KW36 boards. One known as “Transmitter” which transmits Bluetooth LE and Generic FSK packets. The other known as a “Receiver” which receives Bluetooth LE and Generic FSK packets.

Load and build the application demo

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-KW36 SDK (unzipped) 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:

   

Build an Example Application

The following steps will guide you through opening and running the Hybrid Bluetooth LE Generic FSK Advertising example.

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

   

2. Then click on Import SDK examples(s)

   

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

   

4. In the search text box, type “ble_gfsk_adv” to filter the example projects. Use the arrow button to expand the list and locate the “ble_gfsk_adv” project (wireless_examples → hybrid → ble_gfsk_adv), then, select the freertos version of the project and click “Finish”.

   

5. Now build the project by clicking on the project name and then in the Quickstart Panel click on Build.

   

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

7. Now that the project has been compiled, you can now flash it to the board and run it.

8. Make sure the FRDM-KW36 board is plugged in, and click in the Quickstart Panel click on Debug.

   

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

   

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

    

11. Click the “Stop” button to stop debugging the application. At this point, we have programmed one board.

    

12. Connect the second FRDM-KW36 board to your PC and download the same project as in the previous board.

13. At this point, you have programmed two FRDM-KW36 boards with the ble_gfsk_adv demo.

14. Open a Terminal Emulator program and open a session to one of the FRDM-KW36 COM ports.

    • 115200 baud rate
    • No parity
    • 8 data bits
    • 1 stop bit

15. Open a second Terminal Emulator program and open a session to the other FRDM-KW36 COM port using the same port configuration.

16. Press the reset button on both boards.

17. The next menu should be displayed in both terminals.

    

18. Board 1: Start transmitting advertisements. Press SW2 button in one of the FRDM-KW36 boards. The serial terminal connected to the board should display the following text

    This will be the “transmitter” board.

19. Board 2: Start scanning packets. Press SW3 button on the second FRDM-KW36 board. This is to set the board in receiver or scanning mode. Then, press SW2 button to start the application and display the received packets in the serial terminal connected to this board. Bluetooth LE and Generic FSK packets should be displayed as shown in the next image.

20. Refer to “ <sdk_dir>\docs\wireless\Bluetooth\BLE Demo Applications User's Guide.pdf”–" Bluetooth® Low Energy Demo Applications User’s Guide" document for detailed instructions about the available Bluetooth LE demo applications.<sdk_dir>

1. Open the MCUXpresso IDE.
2. Click Import SDK Example(s) from the QuickStart Panel.
3. Select the FRDM-KW36 board in the Import Wizard. Then, select Next.
4. 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.
5. 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.
6. Click on the “led_output” project in the Project Explorer View and build, compile, and run the demo as described previously.
7. You should see a red LED blinking on the board.
8. 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 an example project” radio button and click on Next.
3. 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.
4. 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.
5. 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.
6. You should see a red LED blinking on the board.
7. Terminate the debug session.

1. Open MCUXpresso Config Tools
2. 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.
3. Select the SDK top-level folder from your file system. Select OK.
4. 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.
5. Search for the led_output example by typing “led” in the search bar. Select the led_output example and press Finish.
6. Open the pins tool by selecting Tools->Pins from the toolbar.
7. The pins tool should now display the pin configuration for the led_output project.
8. 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.
9. 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
10. 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.
11. 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.
12. 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.

13. 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.

    

14. 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.

    
15. Click Yes to replace the existing pin_mux.c and pin_mux.h files.
16. 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).
17. Change the defines for BOARD_LED_GPIO to the “GPIOA” and the BOARD_LED_GPIO_PIN to “18”
18. Build and download the project as done in the previous section.
19. Run the application. You should now see the blue LED blinking!
20. Terminate the debug session.

1. Open MCUXpresso Config Tools.
2. Open the Clocks tool from the toolbar: Tools → Clocks.
3. The clock configuration for the “led_output” project will appear in the clocks tool:
4. Switch to the Clocks Diagram view by clicking the tab in the upper left corner, and ensure that the BOARD_BootClockRUN clock mode is being displayed by clicking the tab in the lower left corner.
5. Change the core clock frequency by clicking in the Core Clock field and typing “10 MHz”. You’ll see all the associated clock frequencies automatically change as well then.
6. Now open the “Sources” tab and export the clock_config.c and clock_config.h files.

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

   
8. Press Yes to replace the existing clock_config.c and clock_config.h files.
9. Now open the led project in your IDE, and build, download, and run the project as you did before.
10. The blue LED should now be blinking at a much slower rate