Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

bbslhb — Wed, 29 Apr 2020 06:55:01 GMT

nRF connect for Desktop v3.3.3 and command line tools 10.8.0 seemed OK.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

anicare-tero — Tue, 28 Apr 2020 10:37:19 GMT

Hi Øyvind,

I noticed that too and tried and it seems to be working.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

Øyvind — Tue, 28 Apr 2020 09:54:40 GMT

anicare-tero and @bbslhb,

nRF Connect for Desktop was just released in v3.3.3, and nRF Command Line tools are at v10.8.0. Please update both and let me know if that solved the issue.

I apologize for the inconvenience.

Kind regards,

Øyvind

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

anicare-tero — Wed, 15 Apr 2020 10:07:56 GMT

I moved back to v.3.3.0 because it's working and I want to use the Programmer tool. I have used a lot of different .hex files with my custom board but not that much with nRF9160 DK.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

bbslhb — Wed, 15 Apr 2020 10:03:46 GMT

D:\ncs\nrf\samples\nrf9160\gps

NCS 1.2.0

Modem Firmware V1.1.1

I only changed some uart pins, based on orignal code.

My programmer and nrfjprog is a mass now.

But if you use nrf connect v3.3.1 and programmer 1.4.1 and GPS.hex, you probally can see the issue.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

Øyvind — Wed, 15 Apr 2020 09:37:30 GMT

Please try nrfjprog -f nrf91 -e

Have you tried with other .hex files? What is GPS.hex?

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

anicare-tero — Wed, 15 Apr 2020 08:59:06 GMT

I take my words back. V3.3.2 worked for a while but now I'm getting some HighLevel errors again. So I couldn't try to flash your GPS.hex on nRF Connect v3.3.2.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

Øyvind — Wed, 15 Apr 2020 08:54:39 GMT

I was able to reproduce the issue on my computer. Using the programmer app and the hex file you provided, the issue presented itself here as well. Trying to erase device with nrfjprog in the command line gave me the same error as you described.

I was able to fix the issue with doing nrfjprog -f nrf91 -e, and updating the nrf connect for desktop app to 3.3.2. This will install latest Jlink driver 6.70.

Let me know how it goes.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

bbslhb — Wed, 15 Apr 2020 08:16:37 GMT

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

bbslhb — Wed, 15 Apr 2020 07:53:01 GMT

Hi, ziirou:

Thanks for your help.

I updated my nrf connect to v3.3.2 but bug still exist.

You can try my GPS.hex on nrf connect v3.3.2.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

anicare-tero — Wed, 15 Apr 2020 06:33:05 GMT

Hi bbslhb,

I had the similar problem with nRF Connect v3.3.1 programmer but it seems that v3.3.2 fixed the problem. There was a VCOM bug fix in the release notes so I think that was my problem in my case.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

bbslhb — Wed, 15 Apr 2020 02:03:50 GMT

devzone.nordicsemi.com/.../GPS.hex

I used only one nRF9160DK to flash my nRF9160.

Can you please try to flash GPS.hex with Programmer? My Programmer version is v1.4.1

Issue will 100% happen when I flash GPS.hex with programmer v1.4.1

GPS.hex is based on NCS 1.2.0 and modem v1.1.1

My new nRF9160 chip silk is SICA B0 191601

My older nRF9160 chip is OK, no this issue.

Older nRF9160 silk is BAA-E 2.1.8 12147

I think the issue only happen on new nRF9160 chip.

I think the issue will accur more if the latest nRF9160 chip shiped to more customers.

So please verify the issue on nRF9160 SICA B0 191601.

RE: Bug while using nRF-Command-Line-Tools_10_7_0(nrfjprog 10.7.0)

Øyvind — Tue, 14 Apr 2020 13:01:03 GMT

Hello,

I tested with v10.7.0, and had no issues.

I have only one board connected to my computer. If you have more than one, please make sure to add -f / --family to ensure the correct board is selected.

Edit: I tested using nRF Connect for Desktop v3.3.1 - Programmer, and finished without any issues.

Kind regards,
Øyvind