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

[bbslhb]

Hello:

    I am using nRF Connect v3.3.1 programmer to flash nRF9160 and got an error.

    

    Silk on nRF9160 is: nRF9160 SICA B0 191601

    Programmer can't recognize nRF9160 after error.

    I tried nrfjprog -e to erase but failed:

    

    I tried older nrfjprog and successed to erase the nRF9160:

    

    So is there a bug on nRFjprog_10_7_0?

[anicare-tero]

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.

[bbslhb]

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.

[anicare-tero]

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.

[Øyvind]

Please try nrfjprog -f nrf91 -e

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

[bbslhb]

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.

[anicare-tero]

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.

[Øyvind]

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