Matter samples wont boot on nRF52840-DK with SDK 2.6.0

[trehvis]

Im using nRF Connect for VSCode on a Mac, creating a new application from any of the Matter samples works great with SDK 2.5.2.

However when using SDK 2.6.0 again creating a new application from the Matter samples they will compile and flash to my nRF528040-DK successfully but they don't seem to boot.

I don't get any logs whatsoever, no blinking leds, the board just seems to hang. The primary sample Im trying is the Light Bulb sample though from what I can tell the same thing happens with all the Matter samples. No problems with the other non Matter samples and tutorials on 2.6.0 just the Matter stuff.

Is there something Im missing here for 2.6.0?

[Marte Myrvold]

Hi,

I was not able to reproduce the issue on my side, and it should be working out of the box.

Did you update the nRF Connect SDK version from v2.5.2 to v2.6.0, or did you install v2.6.0 as a new SDK?
Do you see this issue when building the sample directly as well, or only when you create a new application from the sample?
Just to verify, did you create the new application based on the sample in v2.6.0, or was the application created based on the sample in v2.5.2?

Best regards,
Marte

[trehvis]

Hi Marte,

2.6.0 was installed fresh and was the first nRF SDK I had installed on this machine. It was installed using VSCode and the command prompt along with the toolchain. I then also installed 2.5.2 the same way after having the issues described with 2.6.0. I have since tried the process on a second laptop and the same issue occurs (matter samples work fine when using 2.5.2 but dont boot when using 2.6.0).

Building the sample directly from the path .../ncs/v2.6.0/nrf/samples/matter/light_bulb instead of creating a new application results in the same thin: build and flash are successful but boot is not.

To confirm, to run my sets I will set the active toolchain and then set the active sdk and then create a new application copying from the Matter Light bulb sample, then create the build config for my board nrf52840dk_nrf52840, then build, then flash. I have confirmed that the correct version of the sample is being build for the appropriate active SDK version.

What I just noticed is that when I debug the application it seems to hit a FIH_PANIC in the function context_boot_go on line 2324 of .../ncs/v2.6.0/bootloader/mcuboot/boot/bootutil/src/loader.c

Thanks,
Travis 

[Marte Myrvold]

Hi Travis,

Thank you for clarifying. I will look more into this and get back to you tomorrow.
In the meantime, can you check which version of the nRF52840 DK you have? There should be a sticker on the DK itself with the version.

Best regards,
Marte

[trehvis]

Thanks Marte, the version on the sticker is 3.0.2, let me know if there's anything else you need.

[Marte Myrvold]

Hi,

This could be related to an issue that causes the QSPI NOR flash driver to not be successfully initialized when the flash chip is configured to work in non-Quad I/O mode, which might affect new DKs. This has been fixed in v2.6.1 of the SDK that was released yesterday. Please try updating and see if it works with this version. See the nRF Connect SDK v2.6.1 Release Notes for more information.

Best regards,
Marte

[trehvis]

Hi Marte,

I can confirm that v2.6.1 has resolved the issue and the samples work! Not sure it matters at this point but I'll also add that I tried a nRF5340-DK (v2.0.2) and the same issue with SDK 2.6.0 and the same resolution with SDK 2.6.1 occurred.

Thanks for the speedy fix!
Travis