|
| 1 | +.. zephyr:board:: ubx_evk_iris_w1 |
| 2 | +
|
| 3 | +Overview |
| 4 | +******** |
| 5 | + |
| 6 | +The EVK-IRIS-W10x evaluation kit enables stand-alone use of the IRIS-W10 series module. This guide |
| 7 | +provides details about the hardware functionality of the EVK-IRIS-W10 board and includes setup |
| 8 | +instructions for starting development. |
| 9 | + |
| 10 | +All pins and interfaces supported on IRIS-W10 series modules are easily accessible from the |
| 11 | +evaluation board. Simple USB connections serve as the physical interfaces for power, programming |
| 12 | +COM ports, debugging, and USB peripheral connectors. Additionally, the board features other |
| 13 | +interfaces like Ethernet RJ45 and an SDIO header. The EVK-IRIS-W10 board is equipped with a Reset |
| 14 | +button, Boot button, and two user-configurable buttons. Current sense resistors are incorporated for |
| 15 | +accurate current measurement within the module. |
| 16 | + |
| 17 | +For flexible use, GPIO signals are accessible through headers and are complemented by four |
| 18 | +mikroBUS™ standard slots for convenient utilization of Click boards™. Each Click board can be |
| 19 | +seamlessly plugged into an available mikroBUS™ slot to facilitate effortless hardware expansion with |
| 20 | +a variety of standardized compact add-on boards. Click boards are designed to accommodate a |
| 21 | +diverse range of electronic modules, including sensors, transceivers, displays, encoders, motor |
| 22 | +drivers, connection ports, and more. For further information about the Click boards, visit the MIKROE |
| 23 | +website. |
| 24 | + |
| 25 | +Hardware |
| 26 | +******** |
| 27 | + |
| 28 | +- 260 MHz ARM Cortex-M33, tri-radio cores for Wi-Fi 6 + BLE 5.3 + 802.15.4 |
| 29 | +- 1.2 MB on-chip SRAM |
| 30 | +- EVK-IRIS-W101 evaluation board with IRIS-W101 module. Dual-band PCB antenna for WLAN |
| 31 | + with 100 mm coaxial cable and U.FL connector |
| 32 | +- EVK-IRIS-W106 evaluation board with IRIS-W106 module. Dual-band integrated PCB trace |
| 33 | + antenna (external antenna not supplied) |
| 34 | + |
| 35 | + |
| 36 | +Flash Memory Configuration |
| 37 | +========================== |
| 38 | + |
| 39 | +The IRIS-W1 board uses different flash vendors depending on revision: |
| 40 | + |
| 41 | +- ``@macronix``: Module build up to 2023 week 45 |
| 42 | +- ``@fidelex``: Module build 2023 week 46 (2346) onward |
| 43 | + |
| 44 | +To build for a specific flash version: |
| 45 | + |
| 46 | +.. code-block:: bash |
| 47 | +
|
| 48 | + west build -b ubx_evk_iris_w1@macronix |
| 49 | + west build -b ubx_evk_iris_w1@fidelex |
| 50 | +
|
| 51 | +Supported Features |
| 52 | +================== |
| 53 | + |
| 54 | +.. zephyr:board-supported-hw:: |
| 55 | +
|
| 56 | +Basic functionality like UART (default on FC3), GPIOs (I²C, SPI), and the on-board RGB LEDs is supported. |
| 57 | + |
| 58 | +Programming and Debugging |
| 59 | +************************* |
| 60 | + |
| 61 | +.. zephyr:board-supported-runners:: |
| 62 | +
|
| 63 | +
|
| 64 | +Configuring a Debug Probe |
| 65 | +========================= |
| 66 | + |
| 67 | +A debug probe is used for both flashing and debugging the board. This board is |
| 68 | +configured by default to use the J-Link firmware. |
| 69 | + |
| 70 | +Configuring a Console |
| 71 | +===================== |
| 72 | + |
| 73 | +Connect a USB cable from your PC to USB3, and use the serial terminal of your choice |
| 74 | +(minicom, PuTTY, etc.) with the following settings: |
| 75 | + |
| 76 | +- Speed: 115200 |
| 77 | +- Data: 8 bits |
| 78 | +- Parity: None |
| 79 | +- Stop bits: 1 |
| 80 | + |
| 81 | +Flashing |
| 82 | +======== |
| 83 | + |
| 84 | +Here is an example for the ``hello_world`` application. |
| 85 | + |
| 86 | +Open a serial terminal, reset the board (press the RESET button), and you should |
| 87 | +see the following message in the terminal: |
| 88 | + |
| 89 | +.. code-block:: console |
| 90 | +
|
| 91 | + **** Booting Zephyr OS build v4.1.0-2794-g6463c68bc394 **** |
| 92 | + Hello World ! ubx_evk_iris_w1/rw612 |
| 93 | +
|
| 94 | +Wireless Connectivity Support |
| 95 | +***************************** |
| 96 | + |
| 97 | +Fetch Binary Blobs |
| 98 | +================== |
| 99 | + |
| 100 | +To support Bluetooth or Wi-Fi, ``ubx_evk_iris_w1`` requires fetching binary blobs. This can be |
| 101 | +achieved by running the following command: |
| 102 | + |
| 103 | +.. code-block:: console |
| 104 | +
|
| 105 | + west blobs fetch hal_nxp |
| 106 | +
|
| 107 | +Bluetooth |
| 108 | +========= |
| 109 | + |
| 110 | +BLE functionality requires fetching binary blobs, so make sure to follow |
| 111 | +the "Fetch Binary Blobs" section first. |
| 112 | + |
| 113 | +The required binary blob |
| 114 | +``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin`` will be linked |
| 115 | +with the application image directly, forming a single monolithic image. |
| 116 | + |
| 117 | +Wi-Fi |
| 118 | +===== |
| 119 | + |
| 120 | +Wi-Fi functionality also requires fetching binary blobs, so make sure to follow |
| 121 | +the "Fetch Binary Blobs" section first. |
| 122 | + |
| 123 | +The required binary blob |
| 124 | +``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_wifi_a2.bin`` will be linked |
| 125 | +with the application image directly, forming a single monolithic image. |
| 126 | + |
| 127 | +Resources |
| 128 | +********* |
| 129 | + |
| 130 | +- `EVK-IRIS-W1 Website <https://www.u-blox.com/en/product/evk-iris-w1>`_ |
| 131 | +- `EVK-IRIS-W1 GitHub <https://github.com/u-blox/u-blox-sho-OpenCPU/tree/master/MCUXpresso/IRIS-W1>`_ |
| 132 | +- `EVK-IRIS-W1 User Guide <https://content.u-blox.com/sites/default/files/documents/EVK-IRIS-W1_UserGuide_UBX-23007837.pdf>`_ |
0 commit comments