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.

RE: 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.

Jimbrookline — Tue, 24 Nov 2020 13:23:21 GMT

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.

RE: 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.

Didrik Rokhaug — Tue, 24 Nov 2020 09:59:42 GMT

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.

RE: 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.

Jimbrookline — Mon, 23 Nov 2020 20:26:17 GMT

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

RE: 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.

Jimbrookline — Mon, 23 Nov 2020 13:58:00 GMT

THX!

RE: 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.

Didrik Rokhaug — Mon, 23 Nov 2020 13:55:57 GMT

Ah, it seems like you do not have Git installed. You can get it from here: https://git-scm.com/

If I remember correctly, there should be a 'Add to Path' checkbox somewhere in the install wizard.

In addition, you probably have to open a new cmd window for it to find Git.

RE: 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.

Jimbrookline — Mon, 23 Nov 2020 13:52:14 GMT

It was suggested that I try c:Go\bin also, but this does not work. For clarity this is the error I get:

C:\Go>go get github.com/apache/mynewt-mcumgr-cli/mcumgr
go: missing Git command. See https://golang.org/s/gogetcmd
package github.com/apache/mynewt-mcumgr-cli/mcumgr: exec: "git": executable file not found in %PATH%

Can you confirm that the file exists at this path in Github?

And can you confirm the syntax you are suggesting? i.e. %user----\bin?

RE: 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.

Didrik Rokhaug — Mon, 23 Nov 2020 10:40:15 GMT

Have you installed Go?

As C:\Go is the default install path, I assume you have, but it never hurts to make sure.

Next, could you check if 'C:\Go\bin' is in your Path?

For me, it is in the system Path, and not my user's Path, so you might have to check both. If it is not there, try to add it to your (user's) Path, and see if that helps.

You might also have to add '%USERPROFILE%\go\bin' to your path, to let cmd find mcumgr.

RE: 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.

Jimbrookline — Fri, 20 Nov 2020 16:56:08 GMT

Getting stuck again. Trying to down load

go get github.com/apache/mynewt-mcumgr-cli/mcumgr from C:\Go but keeps returning an error that executable file not found in path...
II am sure this is a dumb syntax error somewhere, I can see the file on github. Sorry to hit you with these rookie things.

RE: 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.

Didrik Rokhaug — Fri, 20 Nov 2020 16:55:52 GMT

[quote user="Jimbrookline"]Failed with same error "Make sure device is in MCU Boot Mode" Just to be sure I did this right. I powered up device, pushing small button" I loaded connectivity bridge into File section in Hex format. MCU Boot checkbox on. and hit Write.[/quote]

Sounds like you did it correctly.

[quote user="Jimbrookline"]Onto try mcumgr. Just a question. I have a Win10 machine, do not have linux loaded. If I follow the instructions in the guide will that run as a VM on the Win10 machine?[/quote]

No, if you just follow the instructions, you will not use a Linux VM.

You will need to set up a Linux VM yourself first. But the instructions in the guide should work the same on any OS.

Just a quick note, the guide tells you to compile the application for the nrf9160_pca20035ns board, but it has changed name to thingy91_nrf9160ns in newer NCS versions. However, you do not need to compile anything at all, as you can use the pre-compiled .bin files.

RE: 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.

Jimbrookline — Fri, 20 Nov 2020 16:06:10 GMT

Failed with same error "Make sure device is in MCU Boot Mode" Just to be sure I did this right. I powered up device, pushing small button" I loaded connectivity bridge into File section in Hex format. MCU Boot checkbox on. and hit Write.

Onto try mcumgr. Just a question. I have a Win10 machine, do not have linux loaded. If I follow the instructions in the guide will that run as a VM on the Win10 machine?

RE: 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.

Didrik Rokhaug — Fri, 20 Nov 2020 15:38:18 GMT

I recommend using the connectivity_bridge, as that one have more features.

You should not need to change the position of the switch, as the switch is only used to route the 10-pin header used for debugging or programming with an external programmer.

RE: 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.

Jimbrookline — Fri, 20 Nov 2020 15:25:19 GMT

Would I be loading: thingy91_nrf52_usb_uart_bridge_2020-10-30_5522ca2b.hex or thingy91_nrf52_connectivity_bridge_2020-10-30_5522ca2b.hex And I assume programming switch moves to N52 correct?

RE: 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.

Didrik Rokhaug — Fri, 20 Nov 2020 12:10:22 GMT

Hi,

Could you try to update the nRF52840 first?

To set the nRF52840 in bootloader mode, you must use the small white button next to the nRF9160, not the "main" button.

If that also does not work when you use the Programmer app, you can try to use the command line tool mcumgr from a Linux machine/VM.

This guide explains how to install and use mcumgr: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot

Best regards,

Didrik