NCS v2.7.0 Matter samples with nRF5340-DK and nRF7002-DK don't work

[boz]

SDK v2.7.0

nRF5340-DK with nRF7002-EK

Matter samples (e.g. light bulb)

Extra CMake arguments: -DSHIELD=nrf7002ek

Use sysbuild

uart:~$ *** Booting My Application v2.7.0 - unknown commit ***
*** Using nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: 205 [DL]BLE address: D6:07:18:E7:02:AB
E: Endpoint binding failed with -11
E: HCI driver open failed (-11)
E: 1216 [DL]BLEManager initialization failed: 200000b
E: PlatformMgr().InitChipStack() failed [Error: 0]
E: Exited with code 200000b

Tested with v2.6.2 (no sysbuild), and it works. Seems to be an issue with v2.7.0.

[Marte Myrvold]

Hi,

Can you share how you program the device and which version of nrfjprog you have installed? You can find the version by running the command nrfjprog --version in a terminal.

I get the same error as you if I only program the merged.hex file and not the merged_CPUNET.hex in addition (tested with the nRF Programmer app). If you program the device using the VS Code extension or west flash on the command line, both images should be included.

Best regards,
Marte

[boz]

I am using the VS Code extension for the whole process. CPUNET image seems to be programmed too. Flash task output (redacted because trying to post the whole thing gives an unknwon error):

 *  Executing task: nRF Connect: Flash: light_bulb/build_nrf5340dk_nrf7002ek (active)

Flashing build_nrf5340dk_nrf7002ek to 1050043654

WARNING: Specifying runner options for multiple domains is experimental.
If problems are experienced, please specify a single domain using '--domain <domain>'
-- west flash: using runner nrfjprog
-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: merged_CPUNET.hex
[ #################### ]  12.836s | Erase file - Done erasing                                                          
[ #################### ]   1.405s | Program file - Done programming                                                    
[ #################### ]   1.417s | Verify file - Done verifying                                                       
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050043654 flashed successfully.
-- west flash: using runner nrfjprog
-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: merged.hex
[ #################### ]  43.346s | Erase file - Done erasing                                                          
[ #################### ]   6.546s | Program file - Done programming                                                    
[ #################### ]   6.635s | Verify file - Done verifying                                                       
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050043654 flashed successfully.
 *  Terminal will be reused by tasks, press any key to close it.

[boz]

Unfortunately I'm getting the same error with SB_CONFIG_WIFI_NRF700X=y added to sysbuild.conf.

[Kenneth]

Hello,

I believe v2.8.0 was just released, can you try the approach suggested by Marte for v2.8.0?

Kenneth

[zpm1066]

Folks, I opened a ticket for the same issue to do with same "experimental feature" that generates warning below and BT driver failures.

For both NCS v2.8.0 (and v2.7.0),  "no-sysbuild" builds work fine with BT. However, "sysbuild" generates the errors below.

WARNING: Specifying runner options for multiple domains is experimental.
If problems are experienced, please specify a single domain using '--domain <domain>'

00> rtt:~$ [00:00:01.036,773] <err> bt_hci_driver: Endpoint binding failed with -11
00> rtt:~$ [00:00:01.036,804] <err> bt_hci_core: HCI driver open failed (-11)
00> rtt:~$ Bluetooth init failed (err -11)

You can see the details in the ticket below.
 nRF Connect SDK v2.8.0 - Experimental option for multiple domains causes flashing issues on Thingy:53, resulting in bt_hci_driver failure 

I do have a "workaround" as per the warning suggestion to specify a single domain using "--domain".

for example, 

west flash -d build_vsc_ncs280/thingy53_ns --domain thingy53_sensor_hub_v3

However, I'm looking for a proper solution with help from the Support team.

Regards,
Ravi

[zpm1066]

Hello,

I have a solution for the BT driver not being included and the 'Specifying runner options for multiple domains is experimental.' warning message.

Please see my comments in the following ticket

https://devzone.nordicsemi.com/f/nordic-q-a/117227/nrf-connect-sdk-v2-8-0---experimental-option-for-multiple-domains-causes-flashing-issues-on-thingy-53-resulting-in-bt_hci_driver-failure


It turns out that the nRF Connect SDK build system defaults to using SB_CONFIG_NETCORE_EMPTY configuration, leading to the BT driver not being included in the NET Core Image and generating BT drive failure. 

The addition of SB_CONFIG_NETCORE_HCI_IPC to sysbuild.conf resolves the sysbuild for NCS v2.8.0 and NCS 2.7.0.

Regards,
Ravi

[boz]

This workaround indeed resolves the issue. Thanks for cross posting your discovery to this ticket.

I marked the ticket answered but it is obviously still an open issue.