boards: rd_rw612_bga: Update board documentation

Add information about BLE.

Signed-off-by: Yassine El Aissaoui <yassine.elaissaoui@nxp.com>
This commit is contained in:
Yassine El Aissaoui 2024-05-29 18:01:47 +02:00 committed by Anas Nashif
commit cb85932488

View file

@ -66,6 +66,8 @@ Supported Features
| PM | on-chip | power management; uses SoC Power |
| | | Modes 1 and 2 |
+-----------+------------+-----------------------------------+
| BLE | on-chip | Bluetooth |
+-----------+------------+-----------------------------------+
The default configuration can be found in the defconfig file:
@ -73,6 +75,16 @@ The default configuration can be found in the defconfig file:
Other hardware features are not currently supported
Fetch Binary Blobs
******************
To support Bluetooth, rd_rw612_bga requires fetching binary blobs, which can be
achieved by running the following command:
.. code-block:: console
west blobs fetch hal_nxp
Programming and Debugging
*************************
@ -134,6 +146,26 @@ should see the following message in the terminal:
***** Booting Zephyr OS zephyr-v3.6.0 *****
Hello World! rd_rw612_bga
Bluetooth
=========
BLE functionality requires to fetch binary blobs, so make sure to follow
the ``Fetch Binary Blobs`` section first.
Those binary blobs can be used in two different ways, depending if :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT`
is enabled or not:
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is enabled (default):
The required binary blob will be linked with the application image directly, forming
one single monolithic image.
The user has nothing else to do other than flashing the application to the board.
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is disabled:
In this case, the BLE blob won't be linked with the application, so the user needs to manually
flash the BLE binary blob to the board at the address ``0x18540000``.
The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin``
Resources
=========