JLink not recognized after setting --rbp ALL

RE: JLink not recognized after setting --rbp ALL

abe — Fri, 12 Aug 2016 20:11:14 GMT

Dear all, I have same issue with my NRF52 Dk board. I'm not able to debug, and i have no way to connect it. I used jFlash and NRFTOOL v9.0.0, but board will disconnect. When I try to connect the board, the green led near usb connector (debug led I think...) will ligths off and after few seconds ligths on. Jflash and NRFTOOLS answer "could not connect the target" Kind regards, Abele

RE: JLink not recognized after setting --rbp ALL

endnode — Tue, 26 Jul 2016 13:47:03 GMT

Well then you hopefully get some attention of Nordic's support at your question. In my case submitting it through "My Page" support zone on main Nordic web site helped, if you can share the source code and you can develop reliable procedure how to reproduce then even better. Upgrading to NRFTOOLS v9.0.0 worked for all our locked boards and we don't have any problem since then (some of our engineers reported on older versions of the toolchain that board which was unrecoverable for some time started "magically" work after they kept it unpowered over night or longer, but there were no exact evidence that this shows some real issue so we never investigated these strange occasions).

Cheers Jan

RE: JLink not recognized after setting --rbp ALL

mikoff — Tue, 26 Jul 2016 13:32:09 GMT

endnode, thank you for you reply. I um unable to debug the target (but I see that it operates normally through the uart output). Also I am unable to connect under reset. The other boards with exact same configuration debugs normally. Therefore the symptoms looks very similar to me.

RE: JLink not recognized after setting --rbp ALL

endnode — Tue, 26 Jul 2016 13:14:30 GMT

No, I'm afraid this is different. Reasons:

Issue tracked in this question was strictly linked to read-back protected code (RBPALL flag in UICR). You mention that you care able to debug your firmware which is impossible to do when you have RBPALL enabled.
Issue mentioned in this question was resolved by NRFTOOLS v9.0.0. You seems to be using the latest version so it's probably different problem.

Have you tried to connect under reset (SEGGER can do it I believe)? Change the way you power it? Cheers

RE: JLink not recognized after setting --rbp ALL

mikoff — Tue, 26 Jul 2016 13:07:40 GMT

endnode, it seems that we have the same problem: devzone.nordicsemi.com/.../

RE: JLink not recognized after setting --rbp ALL

endnode — Tue, 19 Apr 2016 14:32:36 GMT

Yes, that's our solution as well. There is a risk that once we need to lock nRF52 in the production there will be no way for rework (in case that programming goes wrong or that we need to redo some large badge because of FW bugs), At least no way to do it over JTAG/SWD...

RE: JLink not recognized after setting --rbp ALL

VarunR — Tue, 19 Apr 2016 14:26:50 GMT

Hi Jan, thanks for the info! I was worried that this might be an isolated case. I will make sure not to set --RBP in more chips until this gets resolved.

RE: JLink not recognized after setting --rbp ALL

endnode — Tue, 19 Apr 2016 14:24:01 GMT

Hi Bjørn and Varun, don't want to interfere but we have seen the same issue with our nRF52 DK boards, case created on the official support portal, boards sent to Norway, issue acknowledged (meaning Nordic could see that boards cannot be recovered by any of their tools) and we are still waiting for resolution (my actual fear is that there is HW bug in SWD or other module on nRF52 REV1 which can cause unrecoverable chips under certain conditions caused by FW...) So I'd be careful to call this rare or unusual (we can even reproduce it, unfortunately only with certain FW binaries which we cannot really share). Cheers Jan

RE: JLink not recognized after setting --rbp ALL

VarunR — Tue, 19 Apr 2016 14:16:21 GMT

Yes, that is the question I had linked to in the main description, the J-link never connects so I can't write to the device access port or the registers. I get an error as follows: (this is with device set as NRF52832_XXAA, using the SWD and speed as 12000)

`Found SWD-DP with ID 0x2BA01477 Found SWD-DP with ID 0x2BA01477

****** Error: Communication timed out: Requested 20 bytes, received 0 bytes ! Could not transfer JTAG data. DAP error while reading DP-Ctrl-Stat register.` This is irrespective of what speed I try with (1000, 4000 or 12000). Could you please try reproducing the issue?

RE: JLink not recognized after setting --rbp ALL

bjorn-spockeli — Tue, 19 Apr 2016 07:37:00 GMT

This is very odd. Have you also tried the method described in this answer, using J-Link?

RE: JLink not recognized after setting --rbp ALL

VarunR — Thu, 14 Apr 2016 13:46:11 GMT

Yes it does show up on the virtual Windows machine. I can see it appear and disappear in the Device Manager and as a JLINK drive when I plug it in and out.

RE: JLink not recognized after setting --rbp ALL

bjorn-spockeli — Thu, 14 Apr 2016 12:54:23 GMT

Could it be that the DK is connected to the host machine( i.e. Mac ) and not the virtual Windows machine? Does your DK still show up as a JLINK drive on the virtual machine?

RE: JLink not recognized after setting --rbp ALL

VarunR — Wed, 13 Apr 2016 14:03:08 GMT

I tried it with two versions: (nrfjprog version: 8.2.0 JLinkARM.dll version: 5.10t) and ( nrfjprog version: 7.6.0 JLinkARM.dll version: 5.10t)

RE: JLink not recognized after setting --rbp ALL

bjorn-spockeli — Wed, 13 Apr 2016 09:05:30 GMT

Which version of nrfjprog are you using?

RE: JLink not recognized after setting --rbp ALL

VarunR — Tue, 12 Apr 2016 13:25:26 GMT

No, I got this error: Device "NRF52832_XXAA" selected.

Found SWD-DP with ID 0x2BA01477

****** Error: Communication timed out: Requested 20 bytes, received 0 bytes ! Could not read hardware status! Can not connect to target.

RE: JLink not recognized after setting --rbp ALL

bjorn-spockeli — Tue, 12 Apr 2016 11:47:34 GMT

Were you able to connect with J-Link commander after rebooting?

RE: JLink not recognized after setting --rbp ALL

VarunR — Mon, 11 Apr 2016 15:59:03 GMT

Turns out I had to do a full reboot. I was running Windows 10 on Parallels on a Macbook, and prior to this I had just tried rebooting the Windows. I did a clean reboot after updating my OSX. Although now I am not able to run nrfjprog -f NRF52 --recover successfully. It says it should take 30s but it never completes. I'll try method 3 in the above link and see if that works. I had tried with the JLink commander before I did the reboot, and even that couldn't connect to it.

RE: JLink not recognized after setting --rbp ALL

bjorn-spockeli — Mon, 11 Apr 2016 11:26:36 GMT

Are you seeing the same behavior when using J-Link Commander?