File tree Expand file tree Collapse file tree 3 files changed +6
-29
lines changed Expand file tree Collapse file tree 3 files changed +6
-29
lines changed Original file line number Diff line number Diff line change @@ -154,20 +154,9 @@ Bluetooth
154
154
BLE functionality requires to fetch binary blobs, so make sure to follow
155
155
the ``Fetch Binary Blobs `` section first.
156
156
157
- Those binary blobs can be used in two different ways, depending if :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT `
158
- is enabled or not:
159
-
160
- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is enabled (default):
161
-
162
- The required binary blob will be linked with the application image directly, forming
163
- one single monolithic image.
164
- The user has nothing else to do other than flashing the application to the board.
165
-
166
- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is disabled:
167
-
168
- In this case, the BLE blob won't be linked with the application, so the user needs to manually
169
- flash the BLE binary blob to the board at the address ``0x18540000 ``.
170
- The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin ``
157
+ frdm_rw612 platform supports the monolithic feature. The required binary blob
158
+ ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin `` will be linked
159
+ with the application image directly, forming one single monolithic image.
171
160
172
161
Resources
173
162
=========
Original file line number Diff line number Diff line change @@ -211,20 +211,9 @@ Bluetooth
211
211
BLE functionality requires to fetch binary blobs, so make sure to follow
212
212
the ``Fetch Binary Blobs `` section first.
213
213
214
- Those binary blobs can be used in two different ways, depending if :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT `
215
- is enabled or not:
216
-
217
- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is enabled (default):
218
-
219
- The required binary blob will be linked with the application image directly, forming
220
- one single monolithic image.
221
- The user has nothing else to do other than flashing the application to the board.
222
-
223
- - :kconfig:option: `CONFIG_NXP_MONOLITHIC_BT ` is disabled:
224
-
225
- In this case, the BLE blob won't be linked with the application, so the user needs to manually
226
- flash the BLE binary blob to the board at the address ``0x18540000 ``.
227
- The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin ``
214
+ rd_rw612_bga platform supports the monolithic feature. The required binary blob
215
+ ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin `` will be linked
216
+ with the application image directly, forming one single monolithic image.
228
217
229
218
Board variants
230
219
**************
Original file line number Diff line number Diff line change @@ -136,7 +136,6 @@ config BT_NXP
136
136
default y
137
137
depends on DT_HAS_NXP_HCI_BLE_ENABLED
138
138
select BT_HCI_SETUP
139
- select USE_DT_CODE_PARTITION if !NXP_MONOLITHIC_BT
140
139
help
141
140
NXP HCI bluetooth interface
142
141
You can’t perform that action at this time.
0 commit comments