EVK-NINA-B5-MCXW716C
Overview
The EVK-NINA-B5 is a compact and scalable development board for rapid prototyping of the NINA-B5 wireless module. It offers easy evaluation of the NINA-B5’s multiprotocol wireless support for Bluetooth LE, Zigbee, Thread and Matter. The board includes an on-board J-link-Link debugger and industry standard headers for easy access to the MCU’s I/Os.
The NINA-B5 module is built on the MCX W71x 96 MHz Arm® Cortex®-M33 from NXP.
Hardware
MCXW71 Arm Cortex-M33 microcontroller running up to 96 MHz
1MB on-chip Flash memory unit
128 KB TCM RAM
On-board MCU-Link debugger with CMSIS-DAP
For more information about the NINA-B5 module and EVK-NINA-B5 board, see:
Supported Features
The ubx_evkninab5 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, ubx_evkninab5 requires fetching binary blobs, which can be achieved by running the following command:
west blobs fetch hal_nxp
Note: The EVK-NINA-B5 is preflashed with NBU files.
Programming and Debugging
The ubx_evkninab5 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 MCU-Link CMSIS-DAP Onboard Debug Probe.
Using J-Link
The onboard debug circuit is a Segger J-Link debugger
The second option is to attach a J-Link External Debug Probe to the 10-pin SWD connector (J12) of the board.
For both options use the -r jlink option with west to use the jlink runner.
west flash -r jlink
Configuring a Console
Connect a USB cable from your PC to the USB port, 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
# From the root of the zephyr repository
west build -b ubx_evkninab5 samples/basic/button
Application Flashing
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b ubx_evkninab5 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! ubx_evkninab5
Debugging
Here is an example for the Hello World application.
# From the root of the zephyr repository
west build -b ubx_evkninab5 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! ubx_evkninab5
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 Flashingsection above.To flash the
NBU Flashing, follow the instructions below in the NINA-B5 system integration manual available on the NINA-B5 product page [1].
The NBU files can be found in : <zephyr workspace>/modules/hal/nxp/zephyr/blobs/mcxw71/ folder.
For more details: