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

nrfgo studio doesn't see my custom board

Hello all,

I am trying to program my custom board using the debug out from the nrf51-DK. I connect all the needed pins and on the nrfgo select the Segger but when I do this my nrf51-DK resets and it doesn't show me nothing.

I already reinstalled the nrfgo studio 1.21.2, also the JLink controlers. I am using a windows 10 64 bit, and already tried to check the registry which I saw in this thread and the path is correct.

Also tried to use the software for the command window the nrfjprog and it says that he cannot detect the board.

Also tried to power on the DK on bootloader mode and flash the JLink to it, but it also didn't help.

If I disconnect my custom board I can detect the nrf51422 inside.

Do I need to connect more than the VTG, SWDIO, SWDCLK and GNDs?

EDIT: I have tested using the P19 and P20 for the debug out and had the same results.

I think my problem is the same as found on this question.

  • I would start with making nrfjprog able to recognize and flash the board. Have you tried "nrfjprog --recover --family NRF51"? (That clears all flash and unlocks the lock on the flash.) Also, have you tried powering your board separately? (That is what I do with the NRF52DK.) There are many more posts in the forum about the proper way to connect and power your custom board. You say "GNDs" plural : I recall a post saying that only GND_DETECT is needed (but it has worked for me with GND and GND_DETECT together.)

  • Yes, all the commands using the nrfjprog say "not able to detect the board". I know that he is going to the correct nrf but it resets my nrf-DK, using the nrfgo or the nrfjprog tool. It is the same result on both. I am powering my board separately, I just connect the VTG to detect the VBAT from my custom board.

  • Under the <Jlink-v6.xx> selection from the Start menu (or whatever the Windows 10 equivalent is) there should be an option to run SEGGER's J-Link Commander. Once the Commander connects to the J-Link pod you should be able to get some more diagnostic info from the Commander about what it is seeing on the pod. One possibility is that it has defaulted to using a JTAG connection instead of SWD.

    Which J-Link pod do you have? The J-Link lite only works at 3.3V - we got burned with that one on a low Voltage custom board.

  • For the nRF5x-DK to program the target board the target board must have a voltage of 3.0 to 3.3 volts. The VTG reference line from the target aboard to the programmer tells the nRF5x-DK that it has a external board connected to it and to ignore the on board nRF5x device and it also determines wither or not it is between 3.0vdc and 3.3vdc.

    Side Note: If you have a device plugged into P20 and then another put into P19, P19 takes precedence.

Related