Custom board (nRF52) external programming Using nRF52-DK

[Tajpeer]

Hello All,

I am trying to Program our custom board which has nRF52 controller using nRF52- development kit (https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52840-DK).

Followed the steps as explained in below discussion,

https://devzone.nordicsemi.com/f/nordic-q-a/14058/external-programming-using-nrf52-dk?ReplySortBy=CreatedDate&ReplySortOrder=Ascending

But couldn't program the custom board with the above connection from nRF52-DK as it's making connection with on-board controller only.

And also explored from the the nRF52-DK user guide that, to use nRF52-DK as debugger to programm external controller we need to make SW6 to nRF only mode as explained in Operating modes section.

But with the nRF only mode change able to disconnect on board MCU but nRF-DK is not finding the external MCU conencted via the custom board.

Can someone helps here with the detailed steps or procedure to make us understand "How to use nRF52-DK as debugger only to program external MCU?".

Thanks a lot in advance.

[Henry_Chou]

Why don't you use the segger Jlink tools? If you want to use the DK as jlink.. I think you have to cut off the original SW circuit or there are some jump setting to cut off.

[Tajpeer]

We are able to program the custom board using JLink debugger.

But we want to make us of the nRF52-DK so that we can utilize the development board also for programming and debugging purposes.

We are also suspecting there should be some jumper settings or switch setting which needed to make nRF52-DK as debugger. Please share if any information.

[Amanda Hsieh]

Hi Tajpeer, 

Please see the DK user guide/Debug output. You also need to provide power 3.3v to the custom board. 

Notice that we are entering the Christmas and New Year holidays and will have reduced staff, please expect delayed responses until after January 4th. Sorry for the inconvenience.

-Amanda H. 

[Tajpeer]

We are following the steps mentioned in Debug Output section.

But observation is,

1. If the VTG is not shorted to VDD then, the code is flashed on the on board MCU on the nRF52 development kit.

2. If the VTG is shorted to VDD then, we are getting "no idcode detected" error code when we tried to connect the debugger to custom board in segger embedded studio.

We assume the above error (as mentioned in 2) is because of the debugger is not able to find the custom MCU to program. In other words, custom board is not powered properly right?

[Amanda Hsieh]

Yes, Should make sure that VTG+GND is connected on the DK.

-Amanda H.