This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

MCUboot DFU failed

Hi team,

I have 2 Thingy:91s, 1 is maybe new, not sure if I have used it before and 2 has been used before and reprogrammed over SWD many times before.

I wanted to test the MCUboot update method found here to update the nRF9160 application and modem core: https://infocenter.nordicsemi.com/topic/ug_nc_programmer/UG/nrf_connect_programmer/ncp_programming_thingy91.html 

Here are the results from testing on the two Thingys:

  1. I used the MCUboot update method and everything worked as expected. I updated the modem firmware and then was able to reprogram the application. I followed the steps in the link above.
  2. I tried to use the MCUboot update method but kept getting the following error: "MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again." I am using the latest version of the tools and had the "Enable MCUboot" box checked. What should be done if this error is reached? I tried multiple times to put the device into MCUboot mode by holding SW3 while turning on the Thingy:91. Finally, I had to reprogram the application core using SWD and was able to then use the MCUboot method. Is there an alternative aside from updating the device using SWD if we are getting MCUboot issues?

Another question, the nRF9160 does not have USB, so these updates are going through the nRF52840?

Regards,

Akash Patel

Parents
  • Hi!

    My guess is that the Thingy:91 was running a FW that didn't have MCUBoot (for example the AT client sample). In that case, there is no other way to fix it, other than flashing a new FW with MCUBoot included, over debug probe.

     

    Another question, the nRF9160 does not have USB, so these updates are going through the nRF52840?

    Yes, the updates go through the nRF52840 running the usb-uart bridge.

    Best regards,

    Heidi

Reply
  • Hi!

    My guess is that the Thingy:91 was running a FW that didn't have MCUBoot (for example the AT client sample). In that case, there is no other way to fix it, other than flashing a new FW with MCUBoot included, over debug probe.

     

    Another question, the nRF9160 does not have USB, so these updates are going through the nRF52840?

    Yes, the updates go through the nRF52840 running the usb-uart bridge.

    Best regards,

    Heidi

Children
No Data
Related