Skip to content

Commit c002e78

Browse files
yeaissadleach02
authored andcommitted
drivers: bt_nxp: delete non monolithic support
Current code does no longer support the non monolithic feature. Hence, removing unnecessary code. Signed-off-by: Yassine El Aissaoui <[email protected]>
1 parent 906a5ec commit c002e78

File tree

3 files changed

+6
-29
lines changed

3 files changed

+6
-29
lines changed

boards/nxp/frdm_rw612/doc/index.rst

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -154,20 +154,9 @@ Bluetooth
154154
BLE functionality requires to fetch binary blobs, so make sure to follow
155155
the ``Fetch Binary Blobs`` section first.
156156

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.
171160

172161
Resources
173162
=========

boards/nxp/rd_rw612_bga/doc/index.rst

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -211,20 +211,9 @@ Bluetooth
211211
BLE functionality requires to fetch binary blobs, so make sure to follow
212212
the ``Fetch Binary Blobs`` section first.
213213

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.
228217

229218
Board variants
230219
**************

drivers/bluetooth/hci/Kconfig

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,6 @@ config BT_NXP
136136
default y
137137
depends on DT_HAS_NXP_HCI_BLE_ENABLED
138138
select BT_HCI_SETUP
139-
select USE_DT_CODE_PARTITION if !NXP_MONOLITHIC_BT
140139
help
141140
NXP HCI bluetooth interface
142141

0 commit comments

Comments
 (0)