nrfjprog (9.4.0) --recover fails on custom board

RE: nrfjprog (9.4.0) --recover fails on custom board

butch — Fri, 09 Jun 2017 12:49:34 GMT

So you might try a pullup/down resistor on one of the SW lines (I am fuzzy, you should look at other posts for details. Roughly, there might be noise on those lines.) I have a BMD300 but haven't used it in a while since I found it does not have a 32khz crystal.

RE: nrfjprog (9.4.0) --recover fails on custom board

apuret — Wed, 07 Jun 2017 14:36:48 GMT

@Jørgen, @ butch: see my answers to your questions in the subject.

RE: nrfjprog (9.4.0) --recover fails on custom board

butch — Tue, 06 Jun 2017 10:58:22 GMT

Just ideas... the custom board that doesn't work is the same hw version as the boards that do work? The pullup/down resistor on the SW lines on the custom board? Short wires between DK and target? High resistance/break in the wires? You are not configuring the SW pins for other purposes? You have not recently upgraded your OS/dev system/nfjprog/Jlink installation? Your 3V power supply reads 3V on a voltmeter and is not noisy?

RE: nrfjprog (9.4.0) --recover fails on custom board

apuret — Tue, 06 Jun 2017 10:19:22 GMT

I currently investigate software changes. What I know for sure: the firmware work in my board, I do not change the 'main' part with the sd_app_evt_wait () and I do not add any 'system off'. I don't dare to try this firmware version on too many boards: 3 boards bricked is enough ...

If I was in the case 'the debugger had not enough time to connect', how can I proceed to recover?

Is there any other situations I can check?

RE: nrfjprog (9.4.0) --recover fails on custom board

Jørgen Holmefjord — Tue, 06 Jun 2017 09:26:50 GMT

What exactly did you do when the boards became non-responsive? Make sure you are not putting the device into system off mode very early in your code (before the debugger have gotten time to connect and put the device into debug mode), without configuring a wakeup source.

RE: nrfjprog (9.4.0) --recover fails on custom board

apuret — Tue, 06 Jun 2017 08:18:26 GMT

@butch: to complet my answer, I connect my board like in this post but it is powered with external +3.0V (not from the DK, see update to the question). I have already programed successfully about 30 different boards with this method and I had made 2 years of development the same way.

I am really lost about this sudden problem. I only think of a software problem but who knows... I am open to try everything sensible to solve this problem.

RE: nrfjprog (9.4.0) --recover fails on custom board

butch — Sat, 03 Jun 2017 11:54:03 GMT

AFAIK there is no other reason for the failure than hardware. I think your answer to Jorgen is not complete: maybe you should specify the schematic of your SW connection between the DK and your custom board, and the voltage on your power supply to the custom board. In other words, there are many different ways to do it and lots of posts about it, and just saying "mine is correct" doesn't help us spot a problem.

RE: nrfjprog (9.4.0) --recover fails on custom board

apuret — Fri, 02 Jun 2017 15:09:18 GMT

Reverse way to ask the question: beside hardware problems, what the reasons to brick a nRF52832 (wrong value in wrong/undocumented register, timing, cpu/peripheral work load...)?

RE: nrfjprog (9.4.0) --recover fails on custom board

apuret — Fri, 02 Jun 2017 09:01:38 GMT

The board is correctly powered and the (already programmed) firmware works as expected.
The SWD port of the nRF52832 is connected to the PCA10040 through P20 and an additional GND.
I can program other identical boards with the same HW/SW tools.

With the (two) faulty boards, SWDSelect command dont find the SWD-DP and subsequent commands failed.

Now, when doing some test, I brick another board! I really need a solution to restore them!

RE: nrfjprog (9.4.0) --recover fails on custom board

Jørgen Holmefjord — Fri, 02 Jun 2017 08:35:58 GMT

This error is typically returned when there is connection or power issues to the board. How do you connect the debugger, and how do you power the board?