This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

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

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

  • 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

Reply
  • 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

Children
Related