This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Segger Debug Out on DK can't see my target

I just got a new target board back from fab/assembly and I'm trying to use the debug out connector on the PCA10028 to program the new target.

My target is the NRF51822-CFAC-R

I've wired J19 on the DK as follows:

Pin 1 - tied to the same 3V supply that powers the DK and my target
Pin 2 - SWDIO (pin H2) on my target
Pin 3 - GND on my target
Pin 4 - SWDCLK (pin C8) on my target

In nRFgo Studio, I'm able to see the Segger on the DK but the Segger is not able to see my target device. Is there any additional setup I need to do on the DK in order to download to my device?

Parents
  • Where does it say that it needs 3.3V? In the nRF51 DK user guide pp. 20 it says that "The voltage supported by external debugging/programmins is 3.0V". There is actually nothing on the nRF51 DK that runs on 3.3V (by default anyway). The USB power gets regulated down to 3.3V, but the current is running through a reverse voltage protection diode with a ~0.3V voltage drop so the actual VIO (supplying the Segger chip) and VDD_nRF are usually at ~3.0V or even lower.

    So I suspect the problem lies elsewhere. It should be plug and play. Do you have other debuggers to test if the problem is with your custom board or your nRF51 DK? Are you able to program other boards/kits with your nRF51 DK? Do you know for sure that your custom board is working? No shorts? All traces are connected? Do you mind posting your layout?

Reply
  • Where does it say that it needs 3.3V? In the nRF51 DK user guide pp. 20 it says that "The voltage supported by external debugging/programmins is 3.0V". There is actually nothing on the nRF51 DK that runs on 3.3V (by default anyway). The USB power gets regulated down to 3.3V, but the current is running through a reverse voltage protection diode with a ~0.3V voltage drop so the actual VIO (supplying the Segger chip) and VDD_nRF are usually at ~3.0V or even lower.

    So I suspect the problem lies elsewhere. It should be plug and play. Do you have other debuggers to test if the problem is with your custom board or your nRF51 DK? Are you able to program other boards/kits with your nRF51 DK? Do you know for sure that your custom board is working? No shorts? All traces are connected? Do you mind posting your layout?

Children
No Data
Related