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

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

Inspectron

image descriptionHi 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

image description

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

image description

image description

image description image description image description

Parents
  • 0

    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.

Reply
  • 0

    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.

Children
No Data
Related

core_v2_widget.Hide()