@@ -38,6 +38,7 @@ The example supports:
38
38
The supported boards are:
39
39
40
40
- ` rd_rw612_bga `
41
+ - ` frdm_rw612 `
41
42
42
43
<a name =" building " ></a >
43
44
@@ -51,23 +52,23 @@ Prerequisites:
51
52
- Follow instruction from [ BUILDING.md] ( ../../../../docs/guides/BUILDING.md )
52
53
to setup the Matter environment
53
54
- Follow instruction from
54
- [ Getting Started Guide] ( https://docs.zephyrproject.org/3.7 .0/develop/getting_started/index.html )
55
+ [ Getting Started Guide] ( https://docs.zephyrproject.org/4.0 .0/develop/getting_started/index.html )
55
56
to setup a Zephyr workspace, however, the west init command to use is as
56
57
follows:
57
58
58
59
``` shell
59
- $ west init zephyrproject -m https://github.com/nxp-zephyr/nxp-zsdk.git --mr nxp-v3.7 .0
60
+ $ west init zephyrproject -m https://github.com/nxp-zephyr/nxp-zsdk.git --mr nxp-v4.0 .0
60
61
```
61
62
62
63
> ** Note** : While some of NXP platforms are supported in Zephyr upstream, we
63
64
> recommend using nxp-zsdk downstream to get access to all NXP features that are
64
65
> not upstream yet. While you can decide to use nxp-zsdk top of tree, we
65
66
> recommend using a proper release tag delivered by NXP. This will ensure a
66
67
> certain level of quality of the nxp-zsdk in use. Currently, we highly
67
- > recommend using the ` nxp-v3.7 .0 ` tag, based on Zephyr 3.7 LTS release. Reach
68
- > to your NXP contact for more details.
68
+ > recommend using the ` nxp-v4.0 .0 ` tag, based on Zephyr 4.0 release. Reach to
69
+ > your NXP contact for more details.
69
70
70
- Steps to build the example, targeting ` rd_rw612_bga ` board :
71
+ Steps to build the example:
71
72
72
73
1 . Activate your Matter env:
73
74
@@ -84,7 +85,13 @@ source <path to zephyr repo>/zephyr-env.sh
84
85
3 . Run west build command:
85
86
86
87
``` shell
87
- west build -b rd_rw612_bga -p auto -d build_zephyr < path to example folder>
88
+ west build -b < board> -p auto -d build_zephyr < path to example folder>
89
+ ```
90
+
91
+ As an example with the ` frdm_rw612 ` board:
92
+
93
+ ``` shell
94
+ west build -b frdm_rw612 -p auto -d build_zephyr examples/all-clusters-app/nxp/zephyr
88
95
```
89
96
90
97
A folder ` build_zephyr ` will be created in the same folder you run the command
@@ -102,7 +109,7 @@ You can get more details on `west build` with
102
109
103
110
### Flashing without debugging
104
111
105
- ` west ` can be used to flash a target, as an example for ` rd_rw612_bga ` board :
112
+ ` west ` can be used to flash a target:
106
113
107
114
``` shell
108
115
west flash -i < J-Link serial number>
@@ -132,30 +139,30 @@ To debug a Matter with Zephyr application, you could use several methods:
132
139
NXP Zephyr examples are not using factory data support by default. Please refer
133
140
the the section below to build with factory data.
134
141
135
- You may refer to ` src/platform/nxp/zephyr/boards/ <board>/<board> .overlay` file
136
- to obtain the memory region used by this partition.
142
+ You may refer to ` <board>.overlay ` file in each examples boards folder to obtain
143
+ the memory region used by this partition.
137
144
138
- For example, the factory data partition on ` rd_rw612_bga ` is reserved in the
139
- last sector of the ` flexspi ` flash of ` RD BGA ` board , at ` 0x1BFFF000 ` .
145
+ For example, the factory data partition on ` frdm_rw612 ` is reserved in the last
146
+ sector of the ` flexspi ` flash, at ` 0x1BFFF000 ` .
140
147
141
148
```
142
- &flexspi {
143
- status = "okay";
149
+ w25q512jvfiq: w25q512jvfiq@0 {
150
+ status = "okay";
151
+
152
+ partitions {
153
+ ...
154
+ factory_partition: partition@3FFF000 {
155
+ label = "factory-data";
156
+ reg = <0x03FFF000 DT_SIZE_K(4)>;
157
+ };
144
158
145
- mx25u51245g: mx25u51245g@0 {
146
- ...
147
- factory_partition: partition@3FFF000 {
148
- label = "factory-data";
149
- reg = <0x03FFF000 DT_SIZE_K(4)>;
150
- };
151
- };
159
+ };
152
160
};
153
161
```
154
162
155
- > ** Note** : You may also refer to
156
- > ` src/platform/nxp/zephyr/boards/<board>/<board>.overlay ` file to check other
157
- > memory partitions used by the platform, such as the file system partition
158
- > mentioned with the ` storage ` label.
163
+ > ** Note** : You may also refer to ` <board>.overlay ` file in each NXP Zephyr
164
+ > examples folder to check other memory partitions used by the platform, such as
165
+ > the file system partition mentioned with the ` storage ` label.
159
166
160
167
### Build with factory data support
161
168
@@ -165,7 +172,7 @@ To build the example with factory data support, you can add
165
172
Example:
166
173
167
174
``` bash
168
- west build -b rd_rw612_bga -p < path to example folder> -- -DFILE_SUFFIX=fdata
175
+ west build -b < board > -p < path to example folder> -- -DFILE_SUFFIX=fdata
169
176
```
170
177
171
178
` prj_fdata.conf ` configuration file will enable ` CONFIG_CHIP_FACTORY_DATA `
@@ -233,13 +240,14 @@ configured for the example. The binding `zephyr,console` is used to print the
233
240
logs, while the binding ` zephyr,shell-uart ` is used for the CLI. If the logs and
234
241
the CLI are split among two serial interfaces, you will have to open both ports.
235
242
236
- As an example, the Matter CLI on ` rd_rw612_bga ` is configured to be output on
243
+ As an example, the Matter CLI on ` frdm_rw612 ` is configured to be output on
237
244
` flexcomm3 ` with a baudrate of ` 115200 ` . The logs are configured to be output on
238
245
` flexcomm0 ` with a baudrate of ` 115200 ` .
239
246
240
- > ** Note** : ` flexcomm3 ` is wired to the USB ` FTDI ` port of the ` RD BGA ` board by
241
- > default. ` flexcomm0 ` is wired to ` GPIO2 ` (RX) and ` GPIO3 ` (TX). Those pins are
242
- > accessible on ` HD2 ` pin header.
247
+ > ** Note** : ` frdm_rw612 ` and ` frdm_rw612``flexcomm3 ` is wired to the USB
248
+ > ` MCULINK ` port of the board by default. ` rd_rw612_bga ` ` flexcomm0 ` is wired to
249
+ > ` GPIO2 ` (RX) and ` GPIO3 ` (TX). Those pins are accessible on ` HD2 ` pin header.
250
+ > ` frdm_rw612 ` ` flexcomm0 ` is wired to RX and TX pins located at ` J5 mikroBUS ` .
243
251
244
252
To access the CLI console, use a serial terminal emulator of your choice, like
245
253
Minicom or GNU Screen. Use the baud rate set to ` 115200 ` .
0 commit comments