Programming nRF9160 with DAPLink programmer

[beethoven62]

I am attempting to program/debug an nRF9160 with a CMSIS-DAP programming adapter (not a Segger JLink adapter). Debugging seems to be fully functional. However, any attempts at programming the device are unsuccessful and the tools I use are ARM Cortex M33/ARMv8 aware. I've tried using Keil's Mbed (uVision) and pyOCD. Both debug with full functionality. In terms of programming the device, neither tool works. I have been able to erase the chip by manually manipulating the correct registers. I've also been on the pyOCD forum and I'm told that the algorithm used by Nordic to erase/program the nRF9160 may be the problem. 

I've attempted these activities on three boards: nRF9160DK, Thingy:91, my own board.

Please advise.

Thanks,

Johnas

[Michal]

Hello again,

I have now added it to the backlog, however I cannot promise when a possible fix will be released.

Just as an extra information, version 8.44.1 is from some time ago, you can download the newest version here.

From the changelog it does not look like there have been any changes to the flashing algorithm, but it shouldn't hurt to try at the very least.

Best regards,

Michal

[crflit]

(Just so everything is clear here…) The link provided above is to a zip with device headers and CMSIS startup source files; it does include .flm flash algorithms.

The release we're talking about is the CMSIS Device Family Pack (DFP). The latest version listed at https://developer.arm.com/tools-and-software/embedded/cmsis/cmsis-packs is 8.44.1. This page is automatically updated based on releases from silicon partners, so it is indeed the case that version 8.44.1 is the most recent DFP release from Nordic.

The DFP also contains device support files like register headers, startup files, etc. So there might need to be further updates to the DFP to include the latest versions of these files from the nRF_MDK release? I don't need them for pyOCD, but other users might need them for MDK or Keil Studio.

Anyway, thanks again for your help!

[Michal]

You have to choose "pack" in the drop-down menu first. From what I can see, they do include the flashing algorithms.

Best regards,

Michal

[Mark Olsson]

I also have this issue, and have sniffed the SWD traffic. From what I understand, it writes 0x1 to 0x5003950c and then waits for 0x50039400 to equal 0. This is where it hangs. I'm guessing that the chip stops responding after erasing all.

[crflit]

Michal,

My apologies!

In that case, could you please open a ticket to update the DFP available on the official CMSIS-Pack list? (Viewable with the link I provided above.) This will allow the latest version to be accessible automatically from within all tools that use CMSIS-Packs. Thanks!

[crflit]

That matches what I saw debugging pyocd, where the device stops responding after the erase.

[Michal]

Hello,

I will try to get it done.

Best regards,

Michal