This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf9160 flash an erased board

Hi, currently I use nRF Connect v3.0.0 to flash my nrf9160-DK. With the Segger Studio from Nordic I am able to generate the merged.hex but now my problem: I erased the chip with the "Erase all" button from nRF Connect and any time I try to flash it, it seems like it worked but the LED3 wont start to blink. If I try some AT Commands in the Link Monitor I just get an "Error:'AT+CFUN?' timed out".

I tried to flash the at_client but if I open the Link Monitor and reset the board, everytime it ends up in an error: 

SPM: NS image at 0xc000


SPM: NS MSP at 0x20023b68


SPM: NS reset vector at 0xe325


SPM: prepare to jump to Non-Secure image.


bsdlib irrecoverable error: 3


ASSERTION FAIL [0] @ ../src/main.c:23


***** Kernel Panic! *****


Current thread ID = 0x20021a80


Faulting instruction address = 0x217c8

I'm grateful for any help, thanks.

  • Hi Sebastian,

    Thanks for your time last Friday. 

    This issue has been discovered that affects modem f/w programming of devices with nrfjprog/nRF Connect Programmer. The modem is vulnerable to file system corruption during a time window in the update process, and unfortunately, the nrfjprog issues a reset that sometimes hits this window. This can cause memory corruption of the file system. 

    -. We will release new version(10.3.0) of nrfjprog 'soon' that does not issue the reset. 

    -. And also we will make a modem f/w image that repairs the broken file system on affected devices 'later'.

    I will let you know when the 10.3.0 is officially released on our web page.

    Thanks for your patience.

    BR,

    Brian

  • Hi Brian,

    No problem, thanks for your time too.

    Good to hear that the issue is discovered and that there will be a solution soon.

    I am looking forward to hearing from you.

    BR,

    Sebastian

  • Hi Sebastian,

    I confirmed your board was successfully recovered with our solution.

    The new version 10.3.0 will protect this kind of issue. Once it happened before installing 10.3.0, our support team will guide how to fix it on our devzone. 

    Thank you for your patience and providing the kit. It was very useful.!

    BR,

    Brian

Related