Could not power-up debug power domain.

RE: Could not power-up debug power domain.

janwillemp — Fri, 17 Nov 2017 08:57:57 GMT

Strangely enough it came back to life a few days ago, but yesterday, after having to take it for a bumpy bike ride, it died on me again, so it looks like a bad connection somewhere. I guess I'll have to buy a new one.

RE: Could not power-up debug power domain.

MartinBL — Wed, 20 Sep 2017 10:32:10 GMT

The most accessible point to measure Vdd_nRF is probably on Pin1 on P22 (the current measurement header).
If you have a second debugger you could try to hook it up to the 'Debug In' header (P18) on the DK and try to program the nRF52.

BTW: You can find layout and hw files that you can use to look for test points etc. here.

RE: Could not power-up debug power domain.

janwillemp — Wed, 20 Sep 2017 07:38:40 GMT

thanks. The 8.6Vpp I wrote earlier likely was a measurement error. I set the whole thing up again using an external board and now have 4Vpp AC which converts to about 2.9Vpp DC (1.1V rectifier drop).

Is there another (preferably physical) way I can test whether or not the nRF52 on the DK is broken? And where can I verify the 2.8V, is there a test point somewhere?

RE: Could not power-up debug power domain.

MartinBL — Tue, 19 Sep 2017 09:15:29 GMT

If your ADC input stays below VDD+0.3V your input voltage shouldn't be a problem. Note that the nRF5s on the DK kits often run at ~2.8V due to some protection diodes on the kit.

I see there are a few similar reports on this forum , but they all seem to discuss external devices.