Thingy:91 | Building and flashing from the command line

RE: Thingy:91 | Building and flashing from the command line

Øyvind — Tue, 21 Sep 2021 10:23:40 GMT

Hey,

Happy to hear we found the solution!

[quote user="Tim Visser"]Just out of curiosity;
Is there any special reason why the CLI command require a .BIN file, while the nRF Connect Programmer needs a .HEX file? I'd expect the nRF Connect Programmer to run a very similar command to the CLI command I'm using now, is that not the case? [/quote]

No other than simplicity is what I'm informed.

Kind regards,
Øyvind

RE: Thingy:91 | Building and flashing from the command line

Tim Visser — Mon, 20 Sep 2021 19:49:56 GMT

Hi Øyvind,

Thanks for your answer!

I had issues getting `mcumgr` to work (it only spits out segfault errors, even without any commands/arguments 🤷).

But I read that mcumgr is a wrapper for newtmgr, which I was able to install without any problems.

And since their commands are pretty much analogous, I was able to use your example script with newtmgr to flash my Thingy:91.

I've been successful in flashing my device by running this code:

newtmgr --conntype=serial --connstring='dev=/dev/tty.usbserial,baud=115200' image upload -e build/zephyr/app_update.bin
newtmgr --conntype=serial --connstring='dev=/dev/tty.usbserial,baud=115200' reset

It seems noticeably slower than flashing with the nRF Connect Programmer application, but it's consistent and works great, so I'm very thankful for your help. (slow speeds might be related to this GitHub issue)

Just out of curiosity;
Is there any special reason why the CLI command require a .BIN file, while the nRF Connect Programmer needs a .HEX file? I'd expect the nRF Connect Programmer to run a very similar command to the CLI command I'm using now, is that not the case?

Thanks again for your assistance, I'm very glad I'm finally able to flash the device from the CLI!

RE: Thingy:91 | Building and flashing from the command line

Øyvind — Mon, 20 Sep 2021 13:19:13 GMT

Hello,

The Thingy:91 does not have an onboard debugger as the nRF9160DK does. This is why it relies on using the debugger from the nRF9160DK or mcuboot serial recovery. Have a look at this blog post on how the Thingy:91 was programmed earlier.

Below is an example of how a script could handle this for you.

echo "Please set child_image/mcuboot.conf CONFIG_MCUBOOT_SERIAL=y and CONFIG_BOOT_SERIAL_DETECT_PIN to a corresponding button on your development kit!"
echo "Hold down the button you chose, then reset the nRF to enter mcuboot serial recovery mode"

mcumgr --conntype=serial --connstring='dev=/dev/ttyACM2,baud=115200' image upload -e build/zephyr/app_update.bin
mcumgr --conntype=serial --connstring='dev=/dev/ttyACM2,baud=115200' reset

Kind regards,
Øyvind