Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

sreehari410 — Fri, 29 Dec 2017 11:17:48 GMT

@Vladimir did you find a solution to the above problem?

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

MartinBL — Mon, 04 Jul 2016 08:31:28 GMT

The issue is fixed in Command-Line-Tools V9.0.0

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

MartinBL — Mon, 04 Jul 2016 08:30:26 GMT

The issue is fixed in Command-Line-Tools V9.0.0

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Sat, 11 Jun 2016 11:26:39 GMT

At least command parameter to new nrfjprog doesn't change - it still --recover. I hope that in release notes for new version they will post some additional info.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

RK — Sat, 11 Jun 2016 00:03:30 GMT

That's rather worrying - since all nrfjprog does it send a sequence out of the JLink, what extra above what's documented is now required to get the chip out of protected mode. I just checked that Rigado uses the same sequence I pasted in their unlocker, would be helpful to know what's changed and is needed now.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Fri, 10 Jun 2016 12:18:25 GMT

My PCA10040 works again. Person from nordic's support gave me preliminary verstion of nrfjprog, which helped with this problem.

So if anyone have same problem - do not hesitate to open a support request on mypage

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Fri, 10 Jun 2016 09:11:30 GMT

Just opened the case on mypage. If we will find any solution I'll post it here.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

MartinBL — Fri, 10 Jun 2016 08:46:15 GMT

Hi. If you are still struggling with this, can you please open a support request on mypage?

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Thu, 09 Jun 2016 13:15:02 GMT

Without -if swd and -device lines and with SWD commands above - the same result. I too think, that it is hardware issue. Thanks anyway, RK.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

RK — Thu, 09 Jun 2016 13:04:13 GMT

I've looked at the register sequence again - they still look correct - so perhaps you have an actual hardware issue on the chip or on the JLink. I have this in a repository, let me just cut and paste it instead of typing it in, although I think it's exactly the same

SWDSelect 
SWDWriteDP 1 0x50000000
SWDWriteDP 2 0x01000000
SWDWriteAP 1 0x00000001
sleep 500
SWDReadAP 3
SWDReadAP 3

ok that's pasted right out of the git repo I used, it looks the same to me. If that doesn't work, I have no more ideas left. You probably don't even need the -if swd and -device lines on the JLink command, but since it's not actually connecting yet .. shouldn't make a difference. But try without them.

Then I really AM out of ideas.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Thu, 09 Jun 2016 12:57:11 GMT

J-Link>SWDSelect

    Select SWD by sending SWD switching sequence.
    Found SWD-DP with ID 0x2BA01477
    J-Link>SWDWriteDP 1, 0x50000000
    Write DP register 1 = 0x50000000
    J-Link>SWDWriteDP 2, 0x01000000
    Write DP register 2 = 0x01000000
    J-Link>SWDWriteAP 1, 0x00000001
    Write AP register 1 = 0x00000001
    J-Link>SWDReadAP 2
    Read AP register 2 = 0x00000000
    J-Link>SWDReadAP 3
    Read AP register 3 = 0x00000001
    J-Link>SWDReadAP 3
    Read AP register 3 = 0x00000000
    J-Link>SWDReadAP 3
    Read AP register 3 = 0x00000000

After that, readback is still on. More then this - firmware in the board is still working - I can see my ble services.

After first call SWDReadAP 3 returns 1, after second and third - it returns 0.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

RK — Thu, 09 Jun 2016 12:44:53 GMT

well that's the reset sequence and I've had it work, you can if you like add onto the end

SWDReadAP 2

and repeat that until you get '0' which says it's finished clearing memory and at that point

SWDReadAP 3

should return 1 (you have to do it twice) showing protection is disabled. The output above looks right to me, incluidng the SWD-DP id so you definitely found it.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Thu, 09 Jun 2016 12:38:53 GMT

C:\Program Files (x86)\SEGGER\JLink_V512f>Jlink -if swd -device nrf52 SEGGER J-Link Commander V5.12f (Compiled May 17 2016 16:04:09) DLL version V5.12f, compiled May 17 2016 16:03:35

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 15 2016 18:03:17
Hardware version: V1.00
S/N: <my serial number>
VTref = 3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>SWDSelect
Select SWD by sending SWD switching sequence.
Found SWD-DP with ID 0x2BA01477
J-Link>SWDWriteDP 1, 0x50000000
Write DP register 1 = 0x50000000
J-Link>SWDWriteDP 2, 0x01000000
Write DP register 2 = 0x01000000
J-Link>SWDWriteAP 1, 0x00000001
Write AP register 1 = 0x00000001
J-Link>^C
C:\Program Files (x86)\SEGGER\JLink_V512f>

After that, device unfortunately is sill has readback protection and I can't disable it.

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

RK — Thu, 09 Jun 2016 12:14:51 GMT

You could try doing it manually using JLink from the command line, connect with

JLink -if swd -device nrf52

or on OSX it's JLinkExe. Then

SWDSelect
SWDWriteDP 1, 0x50000000
SWDWriteDP 2, 0x01000000
SWDWriteAP 1, 0x00000001

That should clear the app protection and entirely erase the chip and allow JLink to connect to the chip again. I have actually done this myself and it did work for me (on a module which came factory locked).

RE: Unable to recover PCA10040 after writing 0xFFFFFF00 to APPROTECT register.

Vladimir — Thu, 09 Jun 2016 11:50:08 GMT

Just found out - it is the same problem as here: devzone.nordicsemi.com/.../ But with different version of nrfjprog.