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 <yassine.elaissaoui@nxp.com>
This commit is contained in:
parent
906a5ec37b
commit
c002e7880a
3 changed files with 6 additions and 29 deletions
|
@ -154,20 +154,9 @@ Bluetooth
|
|||
BLE functionality requires to fetch binary blobs, so make sure to follow
|
||||
the ``Fetch Binary Blobs`` section first.
|
||||
|
||||
Those binary blobs can be used in two different ways, depending if :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT`
|
||||
is enabled or not:
|
||||
|
||||
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is enabled (default):
|
||||
|
||||
The required binary blob will be linked with the application image directly, forming
|
||||
one single monolithic image.
|
||||
The user has nothing else to do other than flashing the application to the board.
|
||||
|
||||
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is disabled:
|
||||
|
||||
In this case, the BLE blob won't be linked with the application, so the user needs to manually
|
||||
flash the BLE binary blob to the board at the address ``0x18540000``.
|
||||
The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin``
|
||||
frdm_rw612 platform supports the monolithic feature. The required binary blob
|
||||
``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin`` will be linked
|
||||
with the application image directly, forming one single monolithic image.
|
||||
|
||||
Resources
|
||||
=========
|
||||
|
|
|
@ -211,20 +211,9 @@ Bluetooth
|
|||
BLE functionality requires to fetch binary blobs, so make sure to follow
|
||||
the ``Fetch Binary Blobs`` section first.
|
||||
|
||||
Those binary blobs can be used in two different ways, depending if :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT`
|
||||
is enabled or not:
|
||||
|
||||
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is enabled (default):
|
||||
|
||||
The required binary blob will be linked with the application image directly, forming
|
||||
one single monolithic image.
|
||||
The user has nothing else to do other than flashing the application to the board.
|
||||
|
||||
- :kconfig:option:`CONFIG_NXP_MONOLITHIC_BT` is disabled:
|
||||
|
||||
In this case, the BLE blob won't be linked with the application, so the user needs to manually
|
||||
flash the BLE binary blob to the board at the address ``0x18540000``.
|
||||
The binary blob will be located here: ``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x/rw61x_sb_ble_a2.bin``
|
||||
rd_rw612_bga platform supports the monolithic feature. The required binary blob
|
||||
``<zephyr workspace>/modules/hal/nxp/zephyr/blobs/rw61x_sb_ble_a2.bin`` will be linked
|
||||
with the application image directly, forming one single monolithic image.
|
||||
|
||||
Board variants
|
||||
**************
|
||||
|
|
|
@ -136,7 +136,6 @@ config BT_NXP
|
|||
default y
|
||||
depends on DT_HAS_NXP_HCI_BLE_ENABLED
|
||||
select BT_HCI_SETUP
|
||||
select USE_DT_CODE_PARTITION if !NXP_MONOLITHIC_BT
|
||||
help
|
||||
NXP HCI bluetooth interface
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue