Mesh and peripheral coexistence nRF5340

[Fluke]

I need help with the example "ble_peripheral_lbs_coex "from the sdk-nrf V2.4.0 for the nRF5340.
I just added a hci_rpmsg.conf file in the child_image folder. with follow content:

# Copy controller configuration from prj.conf
CONFIG_BT_CTLR_DATA_LENGTH_MAX=37

# Disable unused Bluetooth features
CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
CONFIG_BT_CTLR_CHAN_SEL_2=n
CONFIG_BT_CTLR_MIN_USED_CHAN=n
CONFIG_BT_CTLR_PRIVACY=n

The output is as follows:

---

Initializing...
[00:00:00.259,216] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.259,216] <inf> fs_nvs: alloc wra: 0, fa8
[00:00:00.259,246] <inf> fs_nvs: data wra: 0, 6c
[00:00:00.285,675] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.285,705] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.285,736] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 224.11902 Build 2231721665
[00:00:00.286,285] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.515,808] <inf> bt_hci_core: Identity: E9:9B:27:0A:4F:67 (random)
[00:00:00.515,838] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
[00:00:00.515,869] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2077
Mesh initialized
Created a new identity for LBS: 1
ASSERTION FAIL @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:330
[00:00:10.534,912] <err> os: r0/a1: 0x00000003 r1/a2: 0x20002b50 r2/a3: 0x20002b50
[00:00:10.534,912] <err> os: r3/a4: 0x20003bd0 r12/ip: 0x00000003 r14/lr: 0x00006f7d
[00:00:10.534,942] <err> os: xpsr: 0x61000000
[00:00:10.534,942] <err> os: Faulting instruction address (r15/pc): 0x00006f88
[00:00:10.534,973] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.535,003] <err> os: Current thread: 0x20002b50 (unknown)
�*** Booting Zephyr OS build v3.3.99-ncs1 ***ng system

---

Apparently a timeout occurs in hci_core.c:
BT_ASSERT_MSG(err == 0, "command opcode 0x%04x timeout with err %d", opcode, err);

Can anyone please make the example compatible for the nrf5340? 

Thank you in advance, for your assistance.

Fluke

[Fluke]

now I have added this to the conf file of the net core: CONFIG_BT_EXT_ADV_MAX_ADV_SET=6

the hci_rpmsg.conf now:

# Copy controller configuration from prj.conf
CONFIG_BT_BUF_ACL_RX_SIZE=73
CONFIG_BT_BUF_ACL_TX_SIZE=37
CONFIG_BT_CTLR_DATA_LENGTH_MAX=37

CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
CONFIG_BT_CTLR_CHAN_SEL_2=n
CONFIG_BT_CTLR_MIN_USED_CHAN=n
CONFIG_BT_CTLR_PRIVACY=n

# 5 sets are used by Bluetooth mesh, 1 is needed for the sample advs.
CONFIG_BT_EXT_ADV_MAX_ADV_SET=6

then I get the following output with errors:

---

Bluetooth initialized
[00:00:00.516,357] <inf> bt_hci_core: Identity[0]: CD:DF:93:AB:12:3E (random)
[00:00:00.516,510] <inf> bt_hci_core: Identity[1]: F3:B9:D5:9D:A2:D9 (random)
[00:00:00.516,540] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2077, manufacturer 0x0059
[00:00:00.516,540] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2077
Mesh initialized
Recovered identity for LBS: 1
Advertising successfully started
[00:00:00.619,720] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:00:00.619,781] <err> bt_adv: Failed to start advertiser
[00:00:00.619,781] <err> bt_mesh_adv_ext: Advertising failed: err -5

---

If I understand corectly, Bluetooth mesh uses the advertiser as its main channel of communication.
So I need  to enable the extended advertising with two simultaneous advertising sets.
BLE-Mesh is on the top of Bluetooth V4. I guess that Mesh uses the legacy advertising and normal BLE-Services use the extended advertising feature of Bluetooth V5?

Why in the sample the CONFIG_BT_EXT_ADV_MAX_ADV_SET is set to 6 and not 2 sets?

It seems that only one advertising channel can be started successfully.
Is there any conflict with the netcore?


Kind regards
Fluke