Error 3 from newtmgr

jrychter

It seems that newtmgr runs, uploads something (the progress bar advances until almost the very end), and then produces an “Error: 3”. Quick search didn’t produce useful clues, so I’m asking for help.

[13:34] jwr-macbook-pro:/opt/nordic/ncs/v1.5.0/nfed/samples/blinky>~/nordic/nrf9160-tools/newtmgr -c serial image upload build/zephyr/app_update.bin 63.70 KiB / 65.69 KiB [===================================================================================================================================================================================>-----] 96.98% 15.82 KiB/s Error: 3

This is on a Mac (11.4), I tried with ncs 1.6.0 and then downgraded to 1.5.0. I did install the serial driver and gave the kext permission to load.

I should probably mention that this is the first time I’m actually bringing up the board, so whatever bootloader is on it is likely quite old.

jaredwolff

jrychter is this a V1 board? (Should have a BRD-0015-01 on the back) The bootloader that was shipped with V1 may not work with the latest SDK. You may have to upgrade to the latest with a programming cable or downgrade SDK version.

I highlighted some reasons for this error here: https://docs.jaredwolff.com/nrf9160-troubleshooting.html#error-3-from-newtmgr

jrychter

jaredwolff Yes, it’s a V1 that has spent a while in the drawer, but its time has finally come! Thanks for the hint, I’m ashamed to admit I haven’t found and read the troubleshooting page.

I’ll rewrite the bootloader, so happy to see you used a Tag-Connect pinout on the board.

Thanks!

jaredwolff

jrychter I’m ashamed to admit I haven’t found and read the troubleshooting page.

No worries. I added the entry related to this just this morning. 😄 It is a very common issue I should have documented a while back so sorry that you’re running into it!

jrychter I’ll rewrite the bootloader, so happy to see you used a Tag-Connect pinout on the board.

That’s fantastic. Some people don’t like the Tag Connect but I feel like once you get one and you use it, it’s hard to go back!

Hit me up if you need anything else.

jrychter

jaredwolff Well, as it turns out, this might take a while, because it turned out that my ancient J-Link V8 does not support Cortex-M33, so I have no way of reprogramming the board without the bootloader. But, I guess it was time to upgrade the J-Link to a newer version anyway…

jaredwolff

jrychter if you don’t feel like springing for the full official J-Link you can grab the nRF53 DK which can do the job as well.

jonathanberi

I ran into the same issue! And I have loads of nRF52840-DKs, which are too old for the M33. Looks like another Amazon order is in store…

jaredwolff

Agghh. Yea nRF53 DK is the most economical solution jonathanberi I have tons of nRF52s here as well. Bummed they don’t work!

jrychter

Nah, I feel like it’s time I paid some money to Segger anyway, a newer J-Link will come in useful in a number of projects.

(side rant: why does anything having to do with debug probes always have to be a total mess? I mean, does segger really need ELEVEN versions of the J-Link?)

jaredwolff

jrychter side rant: why does anything having to do with debug probes always have to be a total mess? I mean, does segger really need ELEVEN versions of the J-Link?)

One for every day of the week and hen some! 😁 im looking forward to more open source DAPlink based debuggers. Segger is going to have issues once people stop buying into their madness!

jrychter

Just to follow up — the new J-Link whatever arrived, I was able to reprogram the bootloader, and now newtmgr works just fine and loads the examples as expected.

jaredwolff

Thats awesome. Thanks for the update @jrychter