Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

nRF52-DK "Failed to connect to target" and "Access protection is enabled, can't read device version"

Hello Nordic developers,

Last week, I got a new nRF52-DK development board from Mouser Electronics UK. I could use this board for a while with SEGGER Embedded Studio for ARM 5.68 and nRF5_SDK_17.1.0_ddde560. I could run "blinky" and other examples from the SDK successfully. Also a program I wrote was successfully programmed in the chip. A day later, I could not program the chip anymore. SEGGER showed the following screen:

After a click "Yes" I got the same screen again:

Then SEGGER showed the following screen:

I read in this forum that this is related to some new "Access Protection" feature and that to disable I should recover the board using nrfjprog. This is what I did as you can see in the following commands:

As a result, it looks like I cannot recover the chip because Access protection is enabled. The logs generated by nrfjprog are the following:

Also I tried to "Erase" the chip using nrfConnect's Programmer as you can see in the following screenshots with no success.

After clicking "Erase All"  I get the following log:

I know that the nrf52832 chip is working correctly because it is currently executing the last program I flashed. This program sends data via the UART port and I can read it correctly from my computer. The issue is that I cannot program the board again due to the Access Protection issue.

This is the image of the board:

Do you have an idea how I can "resurrect" this board so I program software again?

Parents
  • Were you able to resolve this?  I am having the same problem.

  • Did you try running the following?

    Are you in the same environment as this post? (nRF5 SDK)?

    Have you tried opening RTT viewer or connecting to debugger? This usually prompts a flash erase and clears the protection.

    If on NCS, there can be a few other procedures to clear this protection.

Reply
  • Did you try running the following?

    Are you in the same environment as this post? (nRF5 SDK)?

    Have you tried opening RTT viewer or connecting to debugger? This usually prompts a flash erase and clears the protection.

    If on NCS, there can be a few other procedures to clear this protection.

Children