FRDM-MCXW72

Overview

The FRDM-MCXW72

The MCX W72x family features a 96 MHz Arm® Cortex®-M33 core coupled with a multiprotocol radio subsystem supporting Matter, Thread, Zigbee and Bluetooth LE. The independent radio subsystem, with a dedicated core and memory, offloads the main CPU, preserving it for the primary application and allowing firmware updates to support future wireless standards.

Hardware

  • MCXW72 Arm Cortex-M33 microcontroller running up to 96 MHz

  • 2MB on-chip Flash memory unit

  • 256 KB TCM RAM

  • On-board MCU-Link debugger with CMSIS-DAP

For more information about the MCXW72 SoC and FRDM-MCXW72 board, see:

Supported Features

The frdm_mcxw72 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

Fetch Binary Blobs

To support Bluetooth, frdm_mcxw72 requires fetching binary blobs, which can be achieved by running the following command:

west blobs fetch hal_nxp

Programming and Debugging

The frdm_mcxw72 board supports the runners and associated west commands listed below.

flash debug

Build and flash applications as usual (see Building an Application and Run an Application for more details).

Configuring a Debug Probe

A debug probe is used for both flashing and debugging the board. This board is configured by default to use the J-Link Onboard Debug Probe.

Using LinkServer

The onboard debug circuit can be updated with Linkserver firmware by following the instructions in MCU-Link CMSIS-DAP Onboard Debug Probe. To be able to program the firmware, you need to put the board in DFU mode by shortening the jumper JP5.

Use the -r linkserver option with west to use the linkserver runner.

west flash -r linkserver

Configuring a Console

Connect a USB cable from your PC to J14, and use the serial terminal of your choice (minicom, putty, etc.) with the following settings:

  • Speed: 115200

  • Data: 8 bits

  • Parity: None

  • Stop bits: 1

Application Building

Openthread applications

# From the root of the zephyr repository
west build -b frdm_mcxw72 samples/net/sockets/echo_server -- -DEXTRA_CONF_FILE=overlay-ot.conf

# From the root of the zephyr repository
west build -b frdm_mcxw72 samples/net/sockets/echo_client -- -DEXTRA_CONF_FILE=overlay-ot.conf

Application Flashing

Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b frdm_mcxw72 samples/hello_world
west flash

Open a serial terminal, reset the board (press the RESET button), and you should see the following message in the terminal:

*** Booting Zephyr OS build v3.7.0-xxx-xxxx ***
Hello World! frdm_mcxw72

Debugging

Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b frdm_mcxw72 samples/hello_world
west debug

Open a serial terminal, step through the application in your debugger, and you should see the following message in the terminal:

*** Booting Zephyr OS build v3.7.0-xxx-xxxx ***
Hello World! frdm_mcxw72

Entering ISP Mode

To boot the MCU in ISP mode, follow these steps:

  • Disconnect the FRDM-MCXW72 board from all power sources.

  • Keep the SW3 button on the board pressed, while connecting the board to the host computer USB port.

  • Release the SW3 button. The MCXW72 MCU boots in ISP mode.

  • Reconnect any external power supply, if needed.

Flashing with Low Power Mode

When running an application with low power mode enabled (CONFIG_PM=y), flashing via the standard debug probe (MCU-Link or J-Link) may fail. This is because the MCU enters low power states where the SWD debug interface becomes unresponsive.

To flash a board running a low power image, enter ISP mode (see Entering ISP Mode).

NBU Flashing

BLE functionality requires to fetch binary blobs, so make sure to follow the Fetch Binary Blobs section first.

Two images must be written to the board: one for the host (CM33) and one for the NBU (CM3).

  • To flash the application (CM33) refer to the Application Flashing section above.

  • To flash the NBU Flashing, follow the instructions below:

    • Install blhost from NXP’s website. This is the tool that will allow you to flash the NBU.

    • Enter ISP mode (see Entering ISP Mode).

    • Use the following command to flash NBU file:

Flash Dynamic NBU (BLE + 15.4) on Windows
blhost.exe -p COMxx flash-erase-all 0
blhost.exe -p COMxx flash-erase-all 2
blhost.exe -p COMxx write-memory 0x48800000 <nbu-firmware.bin>

Please consider changing COMxx on Windows or ttyxx on Linux to the serial port used by your board.

The NBU files can be found in : <zephyr workspace>/modules/hal/nxp/zephyr/blobs/mcxw72/ folder.

Troubleshooting

Using Segger SystemView and RTT

Note that when using SEGGER SystemView or RTT with this SOC, the RTT control block address must be set manually within SystemView or the RTT Viewer. The address provided to the tool should be the location of the _SEGGER_RTT symbol, which can be found using a debugger or by examining the zephyr.map file output by the linker.

The RTT control block address must be provided manually because this SOC supports ECC RAM. If the SEGGER tooling searches the ECC RAM space for the control block a fault will occur, provided that ECC is enabled and the RAM segment being searched has not been initialized to a known value.

Support Resources for Zephyr

References