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

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

boz — Tue, 17 Dec 2024 10:21:24 GMT

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.

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

zpm1066 — Fri, 13 Dec 2024 18:02:29 GMT

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

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

zpm1066 — Fri, 13 Dec 2024 02:39:17 GMT

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

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

Kenneth — Thu, 14 Nov 2024 12:13:41 GMT

Hello,

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

Kenneth

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

boz — Mon, 11 Nov 2024 11:10:30 GMT

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

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

Marte Myrvold — Fri, 08 Nov 2024 10:16:26 GMT

Hi,

In v2.7.0 you need to manually set SB_CONFIG_WIFI_NRF700X=y, either in sysbuild.conf or in the build command:

west build -b nrf5340dk/nrf5340/cpuapp -- -DSB_CONFIG_WIFI_NRF700X=y

This seems to be due to sysbuild, as sysbuild cannot make an "if-statement" based on shields, only based on the SoC. Since the nRF5340 is used for both Thread and Wi-Fi, SB_CONFIG_WIFI_NRF700X=y cannot automatically be set in this case.

In future versions (v2.8.0) you do not need to include this, but you must specify the shield with -D<app>_SHIELD=... instead of simply SHIELD, for example:

west build -b nrf5340dk/nrf5340/cpuapp -- -Dlock_SHIELD=nrf7002ek

This is only the case for the Matter samples, and not for samples that are Wi-Fi only.

Please note that some of the Matter samples do not support the nRF7002 EK out of the box. You can see if a sample supports it in the requirement section of the sample's documentation.

Best regards,
Marte

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

Marte Myrvold — Tue, 05 Nov 2024 14:53:24 GMT

Hi,

I was able to reproduce the issue with the nRF5340 DK and nRF7002 EK. I am still investigating this and will get back to you.

Best regards,
Marte

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

boz — Wed, 30 Oct 2024 10:21:17 GMT

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.

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

boz — Wed, 30 Oct 2024 10:17:48 GMT

nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.94e

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

Marte Myrvold — Wed, 30 Oct 2024 09:56:39 GMT

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