JLink Info: Could not power-up debug power domain.

[Inspectron]

Hi all,

until now, I used nRF51 Chips on my board. I programed them trough the nRF51DK(PCA10028). But now I would like to work with nRF52832 Chip. I have a nRF52DK(PCA10040) and an application which is working fine on the 52DK.The application is based on peripheral examples from SDK 11. SD is not used. But when I try to download the same application on my own board with the nRF52832 Chip, will get this error:

• JLink Info: Found SWD-DP with ID 0x2BA01477
• JLink Info: Could not power-up debug power domain.
• JLink Info: Found SWD-DP with ID 0x2BA01477
• 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.

What means: Could not power-up debug power domain? How can I fix this error?

If I want to program the nRF52832 Chip is it possible to use the Segger from the 51DK, or do I have to use the segger from DK52?

Do I have to use an external crystal for programing the chip? Because I would like to work only with the internal RC oscilator.

Voltbox_Classic 1.0 BRD.pdfVoltbox_Classic 1.0 SCH.pdf

This is what I get when I want hwinfo over jlink commander

[Inspectron]

Dear Kirstin The input for the length of the programming cable was very valid ! I have shortened them. See photo on my post. Now programming works perfect on all boards I have. Next problem is as follows: When I start the board with all voltages connected, it does not execute the code. I think it is a setup issue with the internal clock. We do NOT have a 32MHz crystal on board. I made 1 board with a 32MHz crystal and there I can bring the code up most times. Can you tell us, how we set up the 52 to work fine with the internal clock.

[RK]

Hmm - it was I who first suggested to you the wires were too long, not Kristin, but never mind.

If you're not using the Softdevice or the radio in any way, you don't need a 32MHz crystal, the chip works just fine without it, just uses the internal RC and is perfectly happy. This is how the chip starts up every time from reset, with the internal RC, the HF crystal is only started when it's requested specifically.

So the lack of a 32MHz crystal is not your problem. Unless you have some code which attempts to start the HF clock and then waits for it, in which case that is your problem because it will wait forever, but lacking anything like that, you don't need the crystal, the chip will use the RC and there is absolutely no setup required to get it to do that.

.. and .. now you have a working debugger .. load the code, start it, hit break and find out where you are.

[Inspectron]

Dear RK
Did not get your full name, so pse accept my appologies. ! Your input was the one, bringing us a big step further. I will in this case not mount the 32MHz quartz. We will start to debug tomorrow morning. Many thanks again.

[Inspectron]

Dear RK I have another problem now. I have connected my board with the Eval Board and have powered my board with 3.3V. It programs ok. But I really think, that it programs the 52 chip which is on the eval board: !! How can I be sure, that it programs my 52 chip on my board. Do I have to make a 3.3V cable to attach to Pin 1 on the Debug Out connector, wich is the Ext VTG pin. ??? Many thanks for a fast answer

[Inspectron]

Dear RK Problem solved. Connected VTG pin to 3.3V on my target and now ALL works !