EVK-IRIS-W106-RW612
Overview
The EVK-IRIS-W10x evaluation kit enables stand-alone use of the IRIS-W10 series module. This guide provides details about the hardware functionality of the EVK-IRIS-W10 board and includes setup instructions for starting development.
All pins and interfaces supported on IRIS-W10 series modules are easily accessible from the evaluation board. Simple USB connections serve as the physical interfaces for power, programming COM ports, debugging, and USB peripheral connectors. Additionally, the board features other interfaces like Ethernet RJ45 and an SDIO header. The EVK-IRIS-W10 board is equipped with a Reset button, Boot button, and two user-configurable buttons. Current sense resistors are incorporated for accurate current measurement within the module.
For flexible use, GPIO signals are accessible through headers and are complemented by four mikroBUS™ standard slots for convenient utilization of Click boards™. Each Click board can be seamlessly plugged into an available mikroBUS™ slot to facilitate effortless hardware expansion with a variety of standardized compact add-on boards. Click boards are designed to accommodate a diverse range of electronic modules, including sensors, transceivers, displays, encoders, motor drivers, connection ports, and more. For further information about the Click boards, visit the MIKROE website.
Hardware
260 MHz ARM Cortex-M33, tri-radio cores for Wi-Fi 6 + BLE 5.3 + 802.15.4
1.2 MB on-chip SRAM
EVK-IRIS-W101 evaluation board with IRIS-W101 module. Dual-band PCB antenna for WLAN with 100 mm coaxial cable and U.FL connector
EVK-IRIS-W106 evaluation board with IRIS-W106 module. Dual-band integrated PCB trace antenna (external antenna not supplied)
Flash Memory Configuration
The IRIS-W1 board uses different flash vendors depending on revision:
@macronix: Module build up to 2023 week 45@fidelix: Module build 2023 week 46 (2346) onward
To build for a specific flash version:
west build -b ubx_evk_iris_w1@macronix
west build -b ubx_evk_iris_w1@fidelix
Supported Features
The ubx_evk_iris_w1 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.
Basic functionality like UART (default on FC3), GPIOs (I²C, SPI), and the on-board RGB LEDs is supported.
Programming and Debugging
The ubx_evk_iris_w1 board supports the runners and associated west commands listed below.
| flash | debug |
|---|
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 firmware.
Configuring a Console
Connect a USB cable from your PC to USB3, 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
Flashing
Here is an example for the hello_world application.
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 v4.1.0-2794-g6463c68bc394 ****
Hello World ! ubx_evk_iris_w1/rw612
Wireless Connectivity Support
Fetch Binary Blobs
To support Bluetooth or Wi-Fi, ubx_evk_iris_w1 requires fetching binary blobs. This can be
achieved by running the following command:
west blobs fetch hal_nxp
Bluetooth
BLE functionality requires fetching binary blobs, so make sure to follow the “Fetch Binary Blobs” section first.
The required binary blob
<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin will be linked
with the application image directly, forming a single monolithic image.
Wi-Fi
Wi-Fi functionality also requires fetching binary blobs, so make sure to follow the “Fetch Binary Blobs” section first.
The required binary blob
<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_wifi_a2.bin will be linked
with the application image directly, forming a single monolithic image.