1- .. _frdm_rw612 :
2-
3- NXP FRDM_RW612
4- ##############
1+ .. zephyr :board :: frdm_rw612
52
63 Overview
74********
@@ -55,13 +52,23 @@ Supported Features
5552+-----------+------------+-----------------------------------+
5653| CTIMER | on-chip | counter |
5754+-----------+------------+-----------------------------------+
55+ | SCTIMER | on-chip | pwm |
56+ +-----------+------------+-----------------------------------+
5857| MRT | on-chip | counter |
5958+-----------+------------+-----------------------------------+
6059| OS_TIMER | on-chip | os timer |
6160+-----------+------------+-----------------------------------+
6261| PM | on-chip | power management; uses SoC Power |
6362| | | Modes 1, 2 and 3 |
6463+-----------+------------+-----------------------------------+
64+ | BLE | on-chip | Bluetooth |
65+ +-----------+------------+-----------------------------------+
66+ | ADC | on-chip | adc |
67+ +-----------+------------+-----------------------------------+
68+ | DAC | on-chip | dac |
69+ +-----------+------------+-----------------------------------+
70+ | ENET | on-chip | ethernet |
71+ +-----------+------------+-----------------------------------+
6572
6673The default configuration can be found in the defconfig file:
6774
@@ -105,7 +112,7 @@ Connect a USB cable from your PC to J10, and use the serial terminal of your cho
105112Flashing
106113========
107114
108- Here is an example for the :ref : `hello_world ` application. This example uses the
115+ Here is an example for the :zephyr:code-sample : `hello_world ` application. This example uses the
109116:ref: `jlink-debug-host-tools ` as default.
110117
111118.. zephyr-app-commands ::
@@ -124,7 +131,7 @@ see the following message in the terminal:
124131 Debugging
125132=========
126133
127- Here is an example for the :ref : `hello_world ` application. This example uses the
134+ Here is an example for the :zephyr:code-sample : `hello_world ` application. This example uses the
128135:ref: `jlink-debug-host-tools ` as default.
129136
130137.. zephyr-app-commands ::
@@ -146,20 +153,9 @@ Bluetooth
146153BLE functionality requires to fetch binary blobs, so make sure to follow
147154the ``Fetch Binary Blobs `` section first.
148155
149- Those binary blobs can be used in two different ways, depending if :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT `
150- is enabled or not:
151-
152- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is enabled (default):
153-
154- The required binary blob will be linked with the application image directly, forming
155- one single monolithic image.
156- The user has nothing else to do other than flashing the application to the board.
157-
158- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is disabled:
159-
160- In this case, the BLE blob won't be linked with the application, so the user needs to manually
161- flash the BLE binary blob to the board at the address ``0x18540000 ``.
162- The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin ``
156+ frdm_rw612 platform supports the monolithic feature. The required binary blob
157+ ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin `` will be linked
158+ with the application image directly, forming one single monolithic image.
163159
164160RTC Sub-Second Counter
165161======================
0 commit comments