nrfjprog program fail in JlinkARM.dll

RE: nrfjprog program fail in JlinkARM.dll

Chris — Thu, 16 Mar 2017 03:00:10 GMT

Right, sheesh, this was hard to track down.

GPIO P0.21 (/RESET!) was going via an LED to VCC.

In the makefiles (like most peoples) this is defined CONFIG_GPIO_AS_PINRESET for C and ASM for Bootloader AND Application

This was causing it to get stuck in a state that I couldn't then access it as I configured that pin as an output to drive LED.

Disconnected and left floating and no problem getting in with the debugger.

Making the change to makefiles that should resolve.

RE: nrfjprog program fail in JlinkARM.dll

Chris — Wed, 15 Mar 2017 22:42:05 GMT

Same thing is happening to me but only on our new boards with use the NRF52 in the wafer scale package (super small and amazing tho!)

I flashed one board, was happy that new board was working, then tried to reflash it with new code (and pin layouts) and it wouldn't connect.

Swapped to another fresh board, flashed it, happy that it worked (Led lit up) and then went to reflash it and again, couldn't connect.

I'm going to run out of boards at this rate!

JLinkExe -if swd -device nrf52
SEGGER J-Link Commander V6.12j (Compiled Feb 15 2017 18:03:21)
DLL version V6.12j, compiled Feb 15 2017 18:03:08

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 14 2016 16:58:29
Hardware version: V1.00
S/N: 682322937
VTref = 3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF52" selected.


Found SWD-DP with ID 0x2BA01477
Found SWD-DP with ID 0x2BA01477
AP-IDR: 0x24770011, Type: AHB-AP
AHB-AP ROM: 0xE00FF000 (Base addr. of first ROM table)

****** Error: DAP error while reading AIRCR / CPUID register
Communication timed out: Requested 20 bytes, received 0 bytes !
Could not read hardware status!
Cannot connect to target.
J-Link>

Bit annoying any stopping us at the moment. Note that I do create a combined bootloader/SD/app and prefix some special settings for registers as a hex file. But this never caused a problem on the standard package boards.

I get the feeling I'm turning on some protection mode....

RE: nrfjprog program fail in JlinkARM.dll

Petter Myhre — Fri, 02 Dec 2016 11:02:07 GMT

Great! Thanks for answering.

RE: nrfjprog program fail in JlinkARM.dll

gillwei7 — Fri, 02 Dec 2016 10:35:41 GMT

@Petter Thanks for your reply, I have found the root cause, the fail issue happen because I erase and program immediately, so when I change to flow: Erase -> Reset -> Program, the issue not happens any more

RE: nrfjprog program fail in JlinkARM.dll

Petter Myhre — Wed, 23 Nov 2016 11:37:39 GMT

Have you used the programmer to program other nRF52s? So you have made the board yourself? Have you tested the programmer on more than one board? Could you try to flash something else? Like this SoftDevice, do an erase first.

RE: nrfjprog program fail in JlinkARM.dll

gillwei7 — Wed, 23 Nov 2016 01:20:50 GMT

OK I'm using Jlink Plus programmer on nRF52832 custom board, I try Jlink.exe and sometimes with the error

J-Link: Flash download: Restarting flash programming due to program error (possibly skipped erasure of half-way erased sector).
J-Link: Flash download: Skip optimizations disabled for second try.

Or the below error ****** Error: Verification failed @ address 0x00000000 Error while programming flash: Verify failed. But not happen every time, anyone with idea? Thanks!

RE: nrfjprog program fail in JlinkARM.dll

Petter Myhre — Tue, 22 Nov 2016 10:12:09 GMT

Could you elaborate a bit more on your setup? Are you using the OB Segger programmer on a nRF52 DK? Are you programming a nRF52 DK? If not what are you programming? A custom board? Module?