Skip to content

Commit 38131af

Browse files
decsnykartben
authored andcommitted
boards: frdm_rw612: Document SRAM partitions
Add comment to DTS file about SRAM partitions similar to the RTXXX series has comments. Add also a doc section to the frdm_rw612 about this. Also fix the section hierarchy of the frdm_rw612 doc, the header levels were wrong since the wifi and bluetooth, and reference sections were under the debugging section. Group all the wireless connectivity info together. Signed-off-by: Declan Snyder <[email protected]>
1 parent b361c95 commit 38131af

File tree

2 files changed

+34
-11
lines changed

2 files changed

+34
-11
lines changed

boards/nxp/frdm_rw612/doc/index.rst

Lines changed: 29 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -76,16 +76,6 @@ The default configuration can be found in the defconfig file:
7676

7777
Other hardware features are not currently supported
7878

79-
Fetch Binary Blobs
80-
******************
81-
82-
To support Bluetooth or Wi-Fi, frdm_rw612 requires fetching binary blobs, which can be
83-
achieved by running the following command:
84-
85-
.. code-block:: console
86-
87-
west blobs fetch hal_nxp
88-
8979
Programming and Debugging
9080
*************************
9181

@@ -147,6 +137,34 @@ should see the following message in the terminal:
147137
***** Booting Zephyr OS zephyr-v3.6.0 *****
148138
Hello World! frdm_rw612
149139
140+
SRAM Bus Access Partitioning
141+
****************************
142+
143+
RW612 supports shared access of the SRAM from both the code bus and data bus.
144+
The bus used to access the SRAM is determined using two separate memory mapped address spaces.
145+
The application can configure the partitioning of the SRAM access regions by a devicetree overlay.
146+
For example, below is part of an overlay to change the whole SRAM to be used for data.
147+
148+
.. code-block:: devicetree
149+
150+
&sram_data {
151+
reg = <0x0 DT_SIZE_K(1216)>;
152+
};
153+
154+
155+
Wireless Connectivity Support
156+
*****************************
157+
158+
Fetch Binary Blobs
159+
==================
160+
161+
To support Bluetooth or Wi-Fi, frdm_rw612 requires fetching binary blobs, which can be
162+
achieved by running the following command:
163+
164+
.. code-block:: console
165+
166+
west blobs fetch hal_nxp
167+
150168
Bluetooth
151169
=========
152170

@@ -168,7 +186,7 @@ frdm_rw612 platform supports the monolithic feature. The required binary blob
168186
with the application image directly, forming one single monolithic image.
169187

170188
Resources
171-
=========
189+
*********
172190

173191
.. _RW612 Website:
174192
https://www.nxp.com/products/wireless-connectivity/wi-fi-plus-bluetooth-plus-802-15-4/wireless-mcu-with-integrated-tri-radiobr1x1-wi-fi-6-plus-bluetooth-low-energy-5-3-802-15-4:RW612

dts/arm/nxp/nxp_rw6xx_common.dtsi

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,11 @@
7575
#address-cells = <1>;
7676
#size-cells = <1>;
7777

78+
/* RW6XX SRAM can be access by either code or data bus, determined
79+
* by the address used to access the memory.
80+
* Applications can override the reg properties of either
81+
* sram_data or sram_code nodes to change the balance of SRAM access partitioning.
82+
*/
7883
sram_data: memory@40000 {
7984
compatible = "mmio-sram";
8085
reg = <0x40000 DT_SIZE_K(960)>;

0 commit comments

Comments
 (0)