APPROTECT and DAP

RE: APPROTECT and DAP

Eric Stutzenberger — Fri, 29 Sep 2017 16:57:04 GMT

In our factory programming script, we do the following with via JLink:

//Clear App Protect and Erase All
SWDSelect //Selects the SWD Interface
SWDWriteDP 1 0x50000000 //Enables power
SWDWriteDP 2 0x01000000 //Selects the 0x01XXXXXX Access Port and 0xXXXX00XX Register bank in the access port
SWDWriteAP 1 0x00000001 //CTRL-AP Bank 0, register offset 1 (ERASEALL 0x004): Erase all command
sleep 1000 
SWDReadAP 2 //CTRL-AP Bank 0, register offset 2 (ERASEALL 0x008): Erase all command status
SWDReadAP 2 //Second read returns the value
SWDWriteAP 0 0x00000001 
SWDWriteAP 0 0x00000000 
SWDWriteAP 1 0x00000000 
SWDReadAP 3 //CTRL-AP Bank 0, register offset 3 (APPROTECTSTATUS 0x00C): Access port protection status
SWDReadAP 3 //Second read returns the value: 0: enabled 1: not enabled

HTH,

Eric

RE: APPROTECT and DAP

Michael — Fri, 29 Sep 2017 07:47:21 GMT

Hi Eric!

Did you find a solution for your problem? I get the same ERROR when trying to erase the chip with the JLink Commander.

RE: APPROTECT and DAP

Eric Stutzenberger — Tue, 22 Mar 2016 16:58:11 GMT

JLink Erase script for locked NRF52: http://pastebin.com/zChcyMtN

RE: APPROTECT and DAP

Eric Stutzenberger — Tue, 22 Mar 2016 16:55:58 GMT

I figured out the solution:

You cannot ask JLink Commander to connect to the device after APPROTECT is set. This causes commander to switch to some state where SWDWriteDP/SWDReadDP always fails with an error. I don't fully understand what state the connect command causes in JLink Commander. Instead, after starting JLInk Commander send only the SWDSelect command.

Start JLink Commander
SWDSelect -> Selects SWD Interface
SWDWriteDP 1 0x50000000 -> Enable power (as suggested by Segger response)
SWDWriteDP 2 0x01000000 -> Seleect CTRL-AP Bank 0
SWDWriteAP 1 0x00000001 -> Full Chip Erase
SWDReadAP 2 -> Repeat until 0
SWDReadAP 3 -> Two reads show 0x00000001 meaning protection cleared

Thanks for the help.

RE: APPROTECT and DAP

Eric Stutzenberger — Thu, 17 Mar 2016 18:48:18 GMT

Hi RK, thanks for the comments.

Since I have many eval board around for our module, I was able to lock one of them for this testing. After enabling APPROTECT the SWDWriteDP, SWDWriteAP, and their respective read commands all return something in the form of Write DP Register x = <data> ***ERROR or Read AP register x = ERROR. The erase command returns ERROR: Erase returns with error code -1..

I know it is possible to recover devices using nrfjprog but that doesn't help me in this case since I am trying to support many different system types. Since there isn't an answer from Nordic here, I will ask them directly and post back with the result.

Thanks again for the help so far.

RE: APPROTECT and DAP

RK — Sat, 12 Mar 2016 03:31:19 GMT

Did it work?

RE: APPROTECT and DAP

RK — Fri, 11 Mar 2016 01:29:23 GMT

DAP isn't memory-mapped (well it's allowed to be but it's implementation defined if it is or not). You use the JLink SWDReadDP/AP SWDWriteDP/AP commands to read and write the coresight registers. The nrf51 data sheet isn't going to help you there, you need to read the ARM v7m reference manual and the ARM ADIv5 manual to get very far.

I hadn't looked at the nRF52 CTRL-AP, a quick poke around with JLink and some notes I made after reading the ADIv5 manual last year seems to indicate it's a second AP entirely and doesn't show up in the ROM table ... I guess it wouldn't if the DAP is disabled, not going to disable mine to work it out. The following, checking register 0x0FC of AP number 1 (normal DP is number 0) seems to give the correct AP ID, ie the one in the manual 0x02880000

SWDWriteDP 2 0x010000f0
SWDReadAP 3
SWDReadAP 3

note the double-read as data is returned on the second one.

So if that's the right AP, APPPROTECTSTATUS is at 0x00C, reading that on mine with the following

SWDWriteDP 2 0x01000000
SWDReadAP 3
SWDReadAP 3

gives

Read AP register 3 = 0x00000001

which seems correct as indeed protection is off on my chip, you should get 0x00000000

keeping going .. reading the ERASEALLSTATUS just requires reading register 0x008

SWDReadAP 2
SWDReadAP 2

Read AP register 2 = 0x00000000

seems right, the chip isn't erasing currently

Resetting the chip you want to write 0x00000001 to 0x000

SWDWriteAP 0 0x00000001

That reset the chip for me and held the thing in reset and then I failed to get much done after that, I think I needed to switch back to port 0 but didn't and upset JLink .. power cycle.

So to erase everything it seems you should write 0x00000001 to register 0x004 which would be

SWDWriteAP 1 0x00000001

and I'm not going to try that myself, but I'd love to hear how you got on :)

Note all those SWDReadAP and SWDWriteAP commands for 0x000 to 0x00C registers are predicated on your having written the DP port to the correct value with that

SWDWriteDP 2 0x01000000

command which I executed before reading the APPPROTECTSTATUS. It's sticky so you don't have to keep doing it.

Usually you don't have to muck about like that, Segger usually implements this stuff, so did you just try the JLink erase command to see if it's CTRL-AP aware? If not, it's a good question for their forums, and would be a good thing for them to implement.