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

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

Louis — Mon, 14 Feb 2022 13:49:29 GMT

On my side, I got it working using the external flash.

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

Edvin — Mon, 14 Feb 2022 13:46:47 GMT

Hello,

Speaking to our OpenThread team, they said that the reason it isn't working in NCSv1.8.0 is that it isn't tested. Partly because there is no room in flash for an extra application, and partly because it is lacking the transport method for the new application at this point in time. Do you have any plans on overcoming this?

Best regards,

Edvin

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

Louis — Tue, 08 Feb 2022 14:55:45 GMT

For the ADC support, the issue was simply the device tree overlay which disabled the adc controller.

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

Louis — Tue, 08 Feb 2022 01:23:01 GMT

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.

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

Edvin — Mon, 07 Feb 2022 20:50:22 GMT

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