• State Not Answered
  • Locked Locked
  • Replies 18 replies
  • Subscribers 72 subscribers
  • Views 11038 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 113070
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

JLink not recognized after setting --rbp ALL

VarunR

I'm using the nRF52 Dev board and set the --rbp ALL option while using nrfjprog. It worked fine, and I am able to do OTA updates as I was testing the bootloader example. But the jlink is no longer recognized. I cannot undo the readback protection as I can no longer recognize the jlink on the board. I get the following error in keil: ***JLink Error: Communication timed out: Requested 20 bytes, received 0 bytes ! Could not transfer JTAG data. DAP error while reading DP-Ctrl-Stat register. Error: Flash Download failed - Target DLL has been cancelled

And I can't use any of the methods given here to disable the RBP: devzone.nordicsemi.com/.../

Has anyone seen this problem before? Any help would be appreciated, thanks!

  • 0

    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

  • 0

    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.

  • 0

    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...

  • 0

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

    1. 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.
    2. 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

Related
Terms of service