JLINKARM_DLL_ERROR (ffffff9a)

[Akash Patel]

Hello,

I am trying to program my nRF9160 DK v0.9.0 with mfw v1.1.4 but I am getting an error "Modem DFU failed with error: Error: Error occured when program. Errorcode: CouldNotCallFunction (0x9) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)". I am also sometimes having issues programming the application core. I have the VDD_IO set to 1.8V and programming switch to nRF91. 

I am using the latest version of nrfjprog and JLink. This was also happening on JLink v6.88.

nrfjprog version: 10.12.1
JLinkARM.dll version: 7.20a

As you can see in the log below, it surprisingly detects the device as "NRF9160_xxAA_REV2" even though there is a Rev 1 (B0) on this DK. Perhaps that is the problem?

Log for modem update : 

Fullscreen 2465.2021-05-07T23_19_33.033Z-log.txt Download

2021-05-07T23:19:33.426Z INFO Application data folder: C:\Users\Akash\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-05-07T23:19:33.551Z DEBUG App pc-nrfconnect-programmer v1.4.8 official
2021-05-07T23:19:33.551Z DEBUG App path: C:\Users\Akash\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-05-07T23:19:33.551Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-05-07T23:19:33.551Z DEBUG nRFConnect path: C:\Users\Akash\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-05-07T23:19:33.551Z DEBUG HomeDir: C:\Users\Akash
2021-05-07T23:19:33.552Z DEBUG TmpDir: C:\Users\Akash\AppData\Local\Temp
2021-05-07T23:19:33.577Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-05-07T23:19:34.428Z VERBOSE Could not fetch serial number for serial port at COM3
2021-05-07T23:19:36.246Z INFO Using nrfjprog to communicate with target
2021-05-07T23:19:36.971Z INFO Using J-Link Software version 7.20
2021-05-07T23:19:37.463Z INFO Segger serial:  960056967
2021-05-07T23:19:37.463Z INFO Segger speed:  2000  kHz
2021-05-07T23:19:37.463Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
2021-05-07T23:19:37.464Z INFO Core probed: 960056967
2021-05-07T23:19:37.464Z INFO Core RAM: 256KiB
2021-05-07T23:19:37.464Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-05-07T23:19:37.818Z INFO Model: NRF9160_xxAA_REV2.
2021-05-07T23:19:38.657Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-05-07T23:19:39.302Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-05-07T23:19:50.081Z INFO Modem DFU starts to write...
2021-05-07T23:19:50.081Z INFO Writing C:\Users\Akash\Documents\Nordic\nRF9160\Modem_Firmware\Public\1.1.4\mfw_nrf9160_1.1.4.zip to device 960056967
2021-05-07T23:19:51.184Z INFO Checking for newer bootloader.
2021-05-07T23:19:51.188Z INFO Newer bootloader discovered, re-initializing.
2021-05-07T23:19:51.353Z INFO Programming file 0 of 2 files.
2021-05-07T23:19:51.367Z INFO Programming 1 of 1 segments.
2021-05-07T23:19:51.433Z INFO Programming finished.

2021-05-07T23:19:51.436Z INFO Programming file 1 of 2 files.
2021-05-07T23:19:52.495Z INFO Programming 1 of 32 segments.
2021-05-07T23:19:53.150Z INFO Programming 2 of 32 segments.
2021-05-07T23:19:54.563Z INFO Programming 3 of 32 segments.
2021-05-07T23:19:59.854Z ERROR Modem DFU failed with error: Error: Error occured when program. Errorcode: CouldNotCallFunction (0x9)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

I am also getting an error (sometimes) when trying to update the application: 7041.log.log

Regards,

Akash Patel

[Håkon Alseth]

Hi,

 

As you can see in the log below, it surprisingly detects the device as "NRF9160_xxAA_REV2" even though there is a Rev 1 (B0) on this DK. Perhaps that is the problem?

This is a clear bug from the recognition. B0 is rev 1, as you mention.

 

You are able to successfully connect and read the device, which is good.

However, the log shows this line, which indicates that the debugger itself lost the connection:

[2021-May-07 16:24:20] [ info] [  JLink] - [Info    ] [JLink     ]    ***** Error: Connection to emulator lost! 

 

Could this be due to a marginal usb cable? Have you tried to use another usb cable, or do the update procedure on another computer?

 

Kind regards,

Håkon

  

[Akash Patel]

Hi Håkon,

I am now using a nRF9160 DK v0.15.0 and am often times getting errors when trying to program an application. See the log for a successful erase, successful program, successful erase, and then finally an unsuccessful program: /cfs-file/__key/communityserver-discussions-components-files/4/1362.log.log

I have tried with 4 USB cables and all of the USB ports on my computer. Do you think this could be an issue with the Segger OB chip?

Regards,

Akash

[Håkon Alseth]

Hi Akash,

 

You are still getting this error, indicating that the usb device loses its connection to your computer:

***** Error: Connection to emulator lost! 

 

Could you try the DK on another PC, or try updating your PC's chipset drivers to see if this helps?

 

Kind regards,

Håkon

[Akash Patel]

Hi Håkon,

I updated to J-Link V7.20b an hour ago and haven't seen the issue since then. Hopefully it is resolved but will let you know if I see the error again. 

Looking at the release notes, the issue could have been related to #3 or #5:

3. ARMv8-AR: No reset was performed. Fixed.

5. Under certain circumstances the calculated SWO Speed may exceed the CPU clock speed causing issues on some target devices. Fixed.

Regards,

Akash

[Håkon Alseth]

Hi Akash,

 

Im glad to hear that its more stable on your end now.

Those two changes is highly not related to the issue you've been seeing. ARMv8-M is the arch that is used on the nRF91 and nRF53-series, and SWO isn't used for programming (its a kind of UART print for the debugger)

 

Kind regards,

Håkon

[Akash Patel]

Hi Håkon,

Unfortunately the latest update was premature as I am still seeing the issue. I will hopefully be getting a new DK soon and will see if the same problem occurs on there.

Regards,

Akash