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

Trying to update modem SW on a brand new Thingy 91 board. MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again. None of answered questions fixed issue.

Windows 10 USB link. NRF connect 3.6. Followed recommended instruction on extracting firmware. Pressed switch 3 in middle of board on power up. Device showed up in window. Clicked enable MCU boot.  Got error: MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again.    You can see the file version I was trying to load below.   Sorry, I can't tell what serial number the board is. But it says: PCA20035   1.4.0   2020.22  I noted that several people have posted about this, but did not see any solutions in the threads.   I do not have a segger debugger.

Thanks

Jim

20:26:17.108
Modem DFU starts to write...
20:26:17.108
Writing C:\Users\jimdo\OneDrive\Nordic\thingy91_fw_2020-10-30_5522ca2b (1)\mfwnrf9160122.zip to device
20:26:29.566
MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again.
Parents Reply Children
  • Ok, got it loaded and running.  Started by trying to upload the bin file for the N52.  Attached Thingy in program mode by turning on with button pushed.

    Got this encouraging message: but upload did not proceed...

    C:\Go\mynewt-mcumgr-cli-master\mcumgr>mcumgr --conntype=serial --connstring=COM3 image upload connectivity.bin
    0 B / 280.36 KiB [-------------------------------------------------------------------------------------------] 0.00%

    Programming tool said that the device was connected by both COM3 and COM4.  I tried both, neither worked.

    So then I tried the upload serial reset command just to see if there were any signs of life..

    C:\Go\mynewt-mcumgr-cli-master\mcumgr>mcumgr>mcumgr>mcumgr>mcumgr --conntype=serial --connstring=COM3 reset
    Error: NMP timeout

    Got the time out error.

    Any other suggestions? I am beginning to think the unit is bad....

    Thx

    Jim

  • Could you try from a Linux VM or computer?

    It might "just" be a known problem with the Windows drivers. If so, it should work from Linux. And, once you have upgraded the 52 to a newer version, it should work on Windows as well.

  • Hi Didrik,   I have it working now.  Here is the secret.  Don't turn the unit off and on by hot switching the USB cable.   Use the on-off switch.  Then it started behaving and I was able to upload SW using mcumgr.  I need to go back and test the USB.  Yes, customers can do the strangest things......

    Thanks for all of your help, I will close the ticket.

Related