https://devzone.nordicsemi.com/f/nordic-q-a/44544/solved-could-not-power-up-debug-power-domain---what-causes-thisI&#39;ve been using the nRF52840 dongles with a J-Link Plus for over a year now - they generally work great. I am using them without the mbed bootloader, and programming/debugging my code using the bottom 2x5 pads with the appropriate connector to the J-Linken-USTelligent Community 13Fri, 08 Mar 2019 23:00:26 GMThttps://devzone.nordicsemi.com/thread/175153?ContentTypeID=1Fri, 08 Mar 2019 23:00:26 GMT137ad170-7792-4731-bb38-c0d22fbe4515:eb26ebba-ac9c-4564-a016-f3972c37ded1Andrew Kohlsmith<p>Solved.</p> <p>I missed a GPIOTE configuration when porting this to nrf52 and was setting P0.18 low when a timer value was reached. The solution was to take two 470 ohm resistors in parallel between Vtref and RESET# and that gave enough &quot;pull&quot; to allow me to connect to the AP using the J-Link executable and erase the device.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/175128?ContentTypeID=1Fri, 08 Mar 2019 18:03:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2929ba51-320c-4c97-896d-3fce96832a67Andrew Kohlsmith<p>This is an addendum.</p> <p>I have cut SB2 and shorted SB1, which allows me to supply an external 1.8-3.3V on VDD_OUT. I can verify that I do in fact have 3.3V and the J-Link reports that Vtref is 3.3V. However the RESET# line is being pulled low by the nRF52840 rather strongly; even a 470 ohm resistor to 3.3V is only bringing the RESET# line up to 0.9V.</p> <p>I noticed a while ago that P0.18, P0.19, P0.21, P0.23 and P0.25 are all connected together and serve as the RESET# signal; why was the dongle designed this way? I&#39;m not using any of these pins but if one of them inadvertently got set as an output driving low this would certainly explain the problem.</p> <p>If this is the case, how does Nordic suggest correcting the issue?</p><div style="clear:both;"></div>