• State Verified Answer
  • Replies 7 replies
  • Subscribers 62 subscribers
  • Views 11080 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 113830
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

`Could not power-up debug power domain.` with nrfjproj on nRF52

Gordon

Hi,

I'm trying to use the nRF52832DK to flash a Rigado BMD-300 module (nRF52) - I've connected SWDIO, SWCLK, GND and voltage sense to P20.

It seems that because the protection bit comes set, you have to use --recover, and I did that but I get the following:

./nrfjprog --recover
Recovering device. This operation might take 30s.
ERROR: Cannot connect to any nRF device. Please make sure a device is
ERROR: connected to the debugger and supplied.

When enabling logging, it shows:

--------------------------------------------------------------------------------
./nrfjprog --recover --log
nrfjprog verion 8.4.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF51822_XXAA" selected.
FUNCTION: recover.
FUNCTION: recover.
Found SWD-DP with ID 0x2BA01477
Could not power-up debug power domain.
Communication timed out: Requested 20 bytes, received 0 bytes !
Could not read hardware status!
FUNCTION: close_dll.
FUNCTION: close_dll.

It's done something, because the Rigado bootloader no longer shows in BLE, but it seems to have basically bricked the module now. I can't write any new firmware to it (either via nrfjprog or mass storage) - whatever I do I get the same Could not power-up debug power domain. message.

I've tried powering from a battery and the devkit's own power supply. Neither seems to make any difference.

Any ideas what could be wrong? This is causing serious problems - I've got prototypes here waiting to be programmed.

  • 0

    Thanks for your help with this - I'm still hitting the same problems I'm afraid. I'm not entirely sure but I may not have ever got it going - it's possible that I just ended up programming the on-board NRF52 by mistake! Running connect in JLinkExe gives Found SWD-DP with ID 0x2BA01477 but then Could not power-up debug power domain.. I soldered up a whole new board, and the first nrfjproj --family NRF52 --recover definitely worked, but after that I'm getting no response. If you could have a go with a BMD-300 and see if you have any luck, it'd be hugely appreciated.

  • 0

    Ok, this is resolved now. RST had got connected to some unpowered hardware that was pulling it low. RigDFU (flashed initially) ignored RST (I think it's a bit that is set somewhere) and worked fine, but when doing --recoverthat got changed, RST was used, and the whole module became totally unresponsive until I cut the offending trace.

Related