OpenThread + MCUBoot broken with nRF Connect SDK 1.8 on nRF5340 ?

[Louis]

OpenThread and MCUBoot don't play well together anymore of the nRF5340 with the release 1.8 of the nRF Connect SDK. Flashing :

west build -p always -b nrf5340dk_nrf5340_cpuapp nrf/samples/openthread/cli/ -- -DCONFIG_XOROSHIRO_RANDOM_GENERATOR=y -DCONFIG_BOOTLOADER_MCUBOOT=y

results in the bootloop with I assume is caused by a Flash overflow somewhere which goes through silently. nRF52840DK appears to be OK, same with the nRF5340DK on the previous release (1.7).

However, the matter (which includes OpenThread) reference lock design appears to behave fine after I enable the bootloader support

west build -b nrf5340dk_nrf5340_cpuapp nrf/samples/matter/lock/ -- -DBUILD_WITH_DFU=1

[Edvin]

Hello,

Sorry for the late reply.

I see that this is the case, and I am able to reproduce this on my nRF5340DK. I saw that if I add the option CONFIG_NRF53_UPGRADE_NETWORK_CORE=n makes the issue disappear, but I am not sure exactly why. I will have to forward this to our Openthread team. I will get back to you when I know more.

Best regards,

Edvin

[Louis]

Thanks,

On a related topic, the matter lock sample doesn't play well with the ADC driver, regardless of the board:

west build -p always -b nrf5340dk_nrf5340_cpuapp nrf/samples/matter/lock -- -DCONFIG_ADC=y

fails with:

/opt/nrfconnect-sdk/zephyr/drivers/adc/adc_shell.c:41:2: error: #error No known devicetree compatible match for ADC shell
   41 | #error No known devicetree compatible match for ADC shell

The other matter samples are compiling just fine with it, including the light bulb which looks very similar. I tried to break/repair one sample vs the other in order to find the breaking change without any success so far.