BLE Mesh Sample using HCI SPI controller #76170

matt-wood-ct · 2024-07-08T17:23:55Z

matt-wood-ct
Jul 8, 2024

Describe the bug
So I am attempting to validate using a NRF52832 SOC as an external BLE controller for use in a BLE Mesh application and I am struggling to get BLE Mesh to work using a BLE controller connected via SPI.

Test setup
I have two NRF52DK kits with the following jumper connections:

Host	Controller	Function
P0.03	P0.21*	Reset
P0.04	P0.04	IRQ
P0.28	P0.28	SPI_SCK
P0.29	P0.29	SPI_MOSI
P0.30	P0.30	SPI_MISO
P0.31	P0.31	SPI_CS

* P0.21 functions as the HW RST on these dev kits

To Reproduce
Using_SPI_HCI_for_mesh_and_beacon_samples.patch

Add custom board overlay files to the hci_spi and mesh samples (see attached patch file)
Adjust prj.conf files as per the bluetooth architecture pages instructions for HCI (see attached patch file)
Build and flash as normal

Expected behavior
Mesh sample to run as it does with a combined host and controller build on a single dev kit

Impact

Showstopper for using mesh on an external BLE controller

Logs and console output
Host:

*** Booting Zephyr OS build v3.7.0-rc2-188-gdcfc3e787254 ***
Initializing...
Bluetooth initialized
Mesh initialized

Controller (log level increased as it ordinarily would say nothing):

*** Booting Zephyr OS build v3.7.0-rc2-188-gdcfc3e787254 ***
[00:00:00.269,744] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
--- 46 messages dropped ---
[00:00:00.281,707] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 14 bytes
--- 57 messages dropped ---
[00:00:00.289,672] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.289,703] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 6
[00:00:00.289,733] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.289,794] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 6
[00:00:00.290,679] <dbg> hci_spi: bt_tx_thread: buf 0x20009018 type 0 len 3
[00:00:00.290,710] <dbg> bt_hci_raw: bt_send: buf 0x20009018 len 3
[00:00:00.290,710] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.290,740] <dbg> bt_ctlr_hci: le_read_supp_states: states: 0x000003ffff3fffff
[00:00:00.290,771] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 14 bytes
[00:00:00.290,802] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 14
[00:00:00.290,832] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.290,863] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 14
[00:00:00.291,839] <dbg> hci_spi: bt_tx_thread: buf 0x20009018 type 0 len 11
[00:00:00.291,870] <dbg> bt_hci_raw: bt_send: buf 0x20009018 len 11
[00:00:00.291,870] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.291,900] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.291,931] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 6
[00:00:00.291,961] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.292,022] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 6
[00:00:00.292,938] <dbg> hci_spi: bt_tx_thread: buf 0x20009018 type 0 len 11
[00:00:00.292,968] <dbg> bt_hci_raw: bt_send: buf 0x20009018 len 11
[00:00:00.292,968] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.292,999] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.293,029] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 6
[00:00:00.293,060] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.293,121] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 6
[00:00:00.566,986] <dbg> hci_spi: bt_tx_thread: buf 0x20009018 type 0 len 3
[00:00:00.567,016] <dbg> bt_hci_raw: bt_send: buf 0x20009018 len 3
[00:00:00.567,016] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.567,047] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 12 bytes
[00:00:00.567,047] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 12
[00:00:00.567,077] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.567,138] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 12
[00:00:00.572,967] <dbg> hci_spi: bt_tx_thread: buf 0x20009018 type 0 len 28
[00:00:00.572,967] <dbg> bt_hci_raw: bt_send: buf 0x20009018 len 28
[00:00:00.572,998] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.573,028] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.573,028] <dbg> bt_hci_raw: bt_hci_recv: buf 0x200093f8 len 6
[00:00:00.573,059] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.573,120] <dbg> hci_spi: spi_send: buf 0x200093f8 type 1 len 6

Although the logs look like it is doing something, there is nothing futher after those messages and I am unable to see any mesh advertisements using the NRF connect app or the NRF mesh app.

Environment (please complete the following information):

Windows
Zephyr SDK 0.16.3
Zephyr dcfc3e7 (main at time of posting)

Additional context
I did validate my device tree and configurations using a simple BLE beacon sample, this operated without fault and proved the connections are correct.

matt-wood-ct · 2024-07-09T16:10:57Z

matt-wood-ct
Jul 9, 2024
Author

@henrikbrixandersen @PavelVPV Is there anyway we can get this looked at fairly quickly as I have a rather large hardware design decision hanging on this capability, sorry to chase

0 replies

aescolar · 2024-07-09T16:14:32Z

aescolar
Jul 9, 2024
Collaborator

CC @jhedberg

0 replies

cvinayak · 2024-07-10T10:20:45Z

cvinayak
Jul 10, 2024
Collaborator

@matt-wood-ct Please add the below to prj.conf of your hci_spi sample, so that it periodically logs the thread program stack usage (also, acts as a heart beat assuring the Controller is alive).

CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_AUTO_INTERVAL=5
CONFIG_THREAD_NAME=y

Do provide the log here...

0 replies

matt-wood-ct · 2024-07-10T11:04:36Z

matt-wood-ct
Jul 10, 2024
Author

@matt-wood-ct Please add the below to prj.conf of your hci_spi sample, so that it periodically logs the thread program stack usage (also, acts as a heart beat assuring the Controller is alive).
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_AUTO_INTERVAL=5
CONFIG_THREAD_NAME=y
Do provide the log here...

@cvinayak

Added that config to both side, just in case, can confirm both sides are running
See logs below:

Host:

Log:

*** Booting Zephyr OS build v3.7.0-rc2-188-gdcfc3e787254 ***
Initializing...
Thread analyze:
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 44 %
      : Total CPU cycles used: 369
 BT LW WQ            : STACK: unused 1168 usage 176 / 1344 (13 %); CPU: 0 %
      : Total CPU cycles used: 0
 sysworkq            : STACK: unused 1872 usage 176 / 2048 (8 %); CPU: 0 %
      : Total CPU cycles used: 1
 idle                : STACK: unused 272 usage 48 / 320 (15 %); CPU: 0 %
      : Total CPU cycles used: 0
 main                : STACK: unused 696 usage 328 / 1024 (32 %); CPU: 21 %
      : Total CPU cycles used: 454
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
Bluetooth initialized
Mesh initialized
Thread analyze:
 BT Mesh settings workq: STACK: unused 720 usage 176 / 896 (19 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200019a0          : STACK: unused 296 usage 344 / 640 (53 %); CPU: 0 %
      : Total CPU cycles used: 153
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 1 %
      : Total CPU cycles used: 3156
 BT LW WQ            : STACK: unused 640 usage 704 / 1344 (52 %); CPU: 0 %
      : Total CPU cycles used: 71
 sysworkq            : STACK: unused 1040 usage 1008 / 2048 (49 %); CPU: 5 %
      : Total CPU cycles used: 9507
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 91 %
      : Total CPU cycles used: 153933
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
Thread analyze:
 BT Mesh settings workq: STACK: unused 720 usage 176 / 896 (19 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200019a0          : STACK: unused 296 usage 344 / 640 (53 %); CPU: 0 %
      : Total CPU cycles used: 153
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 1 %
      : Total CPU cycles used: 5643
 BT LW WQ            : STACK: unused 640 usage 704 / 1344 (52 %); CPU: 0 %
      : Total CPU cycles used: 71
 sysworkq            : STACK: unused 1040 usage 1008 / 2048 (49 %); CPU: 2 %
      : Total CPU cycles used: 9507
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 94 %
      : Total CPU cycles used: 317774
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
Thread analyze:
 BT Mesh settings workq: STACK: unused 720 usage 176 / 896 (19 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200019a0          : STACK: unused 296 usage 344 / 640 (53 %); CPU: 0 %
      : Total CPU cycles used: 153
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 1 %
      : Total CPU cycles used: 8131
 BT LW WQ            : STACK: unused 640 usage 704 / 1344 (52 %); CPU: 0 %
      : Total CPU cycles used: 71
 sysworkq            : STACK: unused 1040 usage 1008 / 2048 (49 %); CPU: 1 %
      : Total CPU cycles used: 9507
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 96 %
      : Total CPU cycles used: 481615
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
Thread analyze:
 BT Mesh settings workq: STACK: unused 720 usage 176 / 896 (19 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200019a0          : STACK: unused 296 usage 344 / 640 (53 %); CPU: 0 %
      : Total CPU cycles used: 153
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 1 %
      : Total CPU cycles used: 10618
 BT LW WQ            : STACK: unused 640 usage 704 / 1344 (52 %); CPU: 0 %
      : Total CPU cycles used: 71
 sysworkq            : STACK: unused 1040 usage 1008 / 2048 (49 %); CPU: 1 %
      : Total CPU cycles used: 9507
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 96 %
      : Total CPU cycles used: 645456
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
Thread analyze:
 BT Mesh settings workq: STACK: unused 720 usage 176 / 896 (19 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200019a0          : STACK: unused 296 usage 344 / 640 (53 %); CPU: 0 %
      : Total CPU cycles used: 153
 BT RX WQ            : STACK: unused 2448 usage 176 / 2624 (6 %); CPU: 0 %
      : Total CPU cycles used: 0
 thread_analyzer     : STACK: unused 544 usage 480 / 1024 (46 %); CPU: 1 %
      : Total CPU cycles used: 13108
 BT LW WQ            : STACK: unused 640 usage 704 / 1344 (52 %); CPU: 0 %
      : Total CPU cycles used: 71
 sysworkq            : STACK: unused 1040 usage 1008 / 2048 (49 %); CPU: 1 %
      : Total CPU cycles used: 9507
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 97 %
      : Total CPU cycles used: 809297
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)

Controller:

Log:

Thread analyze:
 bt_tx_thread        : STACK: unused 784 usage 240 / 1024 (23 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 1
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 576 usage 448 / 1024 (43 %); CPU: 0 %
      : Total CPU cycles used: 193
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 0
 logging             : STACK: unused 136 usage 632 / 768 (82 %); CPU: 1 %
      : Total CPU cycles used: 9786
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 97 %
      : Total CPU cycles used: 483029
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 36
 ISR0                : STACK: unused 1824 usage 224 / 2048 (10 %)
*** Booting Zephyr OS build v3.7.0-rc2-188-gdcfc3e787254 ***
[00:00:00.267,608] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
--- 25 messages dropped ---
[00:00:00.279,815] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 14 bytes
--- 39 messages dropped ---
[00:00:00.288,482] <dbg> bt_hci_raw: bt_hci_recv: buf 0x20009b78 len 14
[00:00:00.288,513] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.289,581] <dbg> bt_hci_raw: bt_send: buf 0x20009798 len 3
[00:00:00.289,581] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.289,611] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 9 bytes
[00:00:00.289,642] <dbg> bt_hci_raw: bt_hci_recv: buf 0x20009b78 len 9
[00:00:00.289,672] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.290,679] <dbg> bt_hci_raw: bt_send: buf 0x20009798 len 3
[00:00:00.290,710] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
--- 16 messages dropped ---
[00:00:00.294,250] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.294,281] <dbg> bt_hci_raw: bt_hci_recv: buf 0x20009b78 len 6
[00:00:00.294,311] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 5 %
      : Total CPU cycles used: 166
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 576 usage 448 / 1024 (43 %); CPU: 0 %
      : Total CPU cycles used: 19
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 152 usage 616 / 768 (80 %); CPU: 90 %
      : Total CPU cycles used: 2766
 idle                : STACK: unused 272 usage 48 / 320 (15 %); CPU: 0 %
      : Total CPU cycles used: 0
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 3 %
      : Total CPU cycles used: 100
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)
[00:00:00.571,685] <dbg> bt_hci_raw: bt_send: buf 0x20009798 len 3
[00:00:00.571,716] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.571,746] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 12 bytes
[00:00:00.571,777] <dbg> bt_hci_raw: bt_hci_recv: buf 0x20009b78 len 12
[00:00:00.571,807] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
[00:00:00.577,697] <dbg> bt_hci_raw: bt_send: buf 0x20009798 len 28
[00:00:00.577,697] <dbg> bt_ctlr_hci_driver: hci_driver_send: enter
[00:00:00.577,728] <dbg> bt_ctlr_hci_driver: cmd_handle: Replying with event of 6 bytes
[00:00:00.577,728] <dbg> bt_hci_raw: bt_hci_recv: buf 0x20009b78 len 6
[00:00:00.577,758] <dbg> bt_ctlr_hci_driver: hci_driver_send: exit: 0
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 0 %
      : Total CPU cycles used: 181
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 552 usage 472 / 1024 (46 %); CPU: 0 %
      : Total CPU cycles used: 78
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 128 usage 640 / 768 (83 %); CPU: 5 %
      : Total CPU cycles used: 9116
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 94 %
      : Total CPU cycles used: 157459
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 106
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 0 %
      : Total CPU cycles used: 181
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 552 usage 472 / 1024 (46 %); CPU: 0 %
      : Total CPU cycles used: 133
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 128 usage 640 / 768 (83 %); CPU: 3 %
      : Total CPU cycles used: 11956
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 96 %
      : Total CPU cycles used: 318460
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 106
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 0 %
      : Total CPU cycles used: 181
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 552 usage 472 / 1024 (46 %); CPU: 0 %
      : Total CPU cycles used: 188
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 128 usage 640 / 768 (83 %); CPU: 2 %
      : Total CPU cycles used: 14802
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 96 %
      : Total CPU cycles used: 479455
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 106
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 0 %
      : Total CPU cycles used: 181
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 552 usage 472 / 1024 (46 %); CPU: 0 %
      : Total CPU cycles used: 243
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 128 usage 640 / 768 (83 %); CPU: 2 %
      : Total CPU cycles used: 17650
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 97 %
      : Total CPU cycles used: 640448
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 106
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)
Thread analyze:
 bt_tx_thread        : STACK: unused 512 usage 512 / 1024 (50 %); CPU: 0 %
      : Total CPU cycles used: 181
 BT RX               : STACK: unused 408 usage 360 / 768 (46 %); CPU: 0 %
      : Total CPU cycles used: 2
 BT RX pri           : STACK: unused 96 usage 352 / 448 (78 %); CPU: 0 %
      : Total CPU cycles used: 1
 thread_analyzer     : STACK: unused 552 usage 472 / 1024 (46 %); CPU: 0 %
      : Total CPU cycles used: 298
 sysworkq            : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 logging             : STACK: unused 128 usage 640 / 768 (83 %); CPU: 2 %
      : Total CPU cycles used: 20497
 idle                : STACK: unused 256 usage 64 / 320 (20 %); CPU: 97 %
      : Total CPU cycles used: 801443
 main                : STACK: unused 32 usage 480 / 512 (93 %); CPU: 0 %
      : Total CPU cycles used: 106
 ISR0                : STACK: unused 1820 usage 228 / 2048 (11 %)

0 replies

matt-wood-ct · 2024-07-10T11:26:23Z

matt-wood-ct
Jul 10, 2024
Author

To make mesh on HCI work do I need CONFIG_BT_HCI_MESH_EXT enabled?
I just tried to turn it on but it has a dependency I can't resolve, it wants CONFIG_BT_LL_SW_SPLIT=n but that can never be the case because if you are a Bluetooth controller you are required to have a BT_LL_CHOICE and BT_LL_SW_SPLIT is the only choice...

Ok more investigation, I forced CONFIG_BT_HCI_MESH_EXT on by changing the dependencies and discovered that that then tries to include a file (ll_sw/ll_mesh.h) which doesn't even exist any more, so I that that config is likely left over from an older implementation (circa 2018/19)

0 replies

matt-wood-ct · 2024-07-10T14:46:33Z

matt-wood-ct
Jul 10, 2024
Author

FYI I did also try using nordics hci_lpuart sample in conjunction with the same beacon and mesh samples configured for H4 HCI rather then SPI on the NRF52832 ICs and found the same result, beacon works, mesh does not appear to work.
Note, I don't have logs for this since the NRF52832 only has one UART so I had to use that for the interchip comms. In principle you could get RTT up and running but I was just trying to do a quick and dirty test so I used minimal overlays and confs.

0 replies

PavelVPV · 2024-07-10T19:00:15Z

PavelVPV
Jul 10, 2024
Collaborator

Hi @matt-wood-ct, I'm on a leave atm and can't try the sample at my desk, but the first thing comes up to my mind when trying to build mesh separately of controller is misconfiguration of host and controller. Though IIRC you should have had an error when host and controller are misconfigured, it is worth comparing bluetooth configuration (CONFIG_BT_* Kconfigs from .config file in build folder) of single image build (when host and controller are built together) and multi image build (the one you have).

0 replies

matt-wood-ct · 2024-07-11T11:11:56Z

matt-wood-ct
Jul 11, 2024
Author

Hi @PavelVPV, thank you for your time,
I have extracted those configs
and I am going through the differences now, will probably take me a few hours to go through (I'm having a busy day) so in the mean time here are the 3 files.

Controller.txt
Host.txt
Combined.txt

0 replies

jori-nordic · 2024-07-22T10:22:59Z

jori-nordic
Jul 22, 2024
Collaborator

Controller is missing CONFIG_BT_EXT_ADV=y.
Reproduced the issue on my (and a colleague's) desk. Added config, and it works as you can see from the video. We're able to provision and have two DKs control each other's LED.
it-werks.webm

Here's the exact branch I used: jori-nordic@bfb3e30

0 replies

matt-wood-ct · 2024-07-22T10:27:12Z

matt-wood-ct
Jul 22, 2024
Author

Controller is missing CONFIG_BT_EXT_ADV=y. Reproduced the issue on my (and a colleague's) desk. Added config, and it works as you can see from the video. We're able to provision and have two DKs control each other's LED. it-werks.webm

@jori-nordic Thank you so much for this I will retest soon to make sure but it looks like you've cracked it 😄

This is a really important proving exercise for the project I am working on

0 replies

jori-nordic · 2024-07-22T10:35:27Z

jori-nordic
Jul 22, 2024
Collaborator

No problem :)

Feel free to review and +1 the doc change if the instructions work for you: #76161

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

BLE Mesh Sample using HCI SPI controller #76170

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 11 comments

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

BLE Mesh Sample using HCI SPI controller #76170

matt-wood-ct Jul 8, 2024

Replies: 11 comments

matt-wood-ct Jul 9, 2024 Author

aescolar Jul 9, 2024 Collaborator

cvinayak Jul 10, 2024 Collaborator

matt-wood-ct Jul 10, 2024 Author

matt-wood-ct Jul 10, 2024 Author

matt-wood-ct Jul 10, 2024 Author

PavelVPV Jul 10, 2024 Collaborator

matt-wood-ct Jul 11, 2024 Author

jori-nordic Jul 22, 2024 Collaborator

matt-wood-ct Jul 22, 2024 Author

jori-nordic Jul 22, 2024 Collaborator

matt-wood-ct
Jul 8, 2024

matt-wood-ct
Jul 9, 2024
Author

aescolar
Jul 9, 2024
Collaborator

cvinayak
Jul 10, 2024
Collaborator

matt-wood-ct
Jul 10, 2024
Author

matt-wood-ct
Jul 10, 2024
Author

matt-wood-ct
Jul 10, 2024
Author

PavelVPV
Jul 10, 2024
Collaborator

matt-wood-ct
Jul 11, 2024
Author

jori-nordic
Jul 22, 2024
Collaborator

matt-wood-ct
Jul 22, 2024
Author

jori-nordic
Jul 22, 2024
Collaborator