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

Programming External nRF52 via nRF52-DK Board RELIABLY

We are programming our nRF52 based boards through USB via the P20 connector on a Nordic nRF52-DK board. However when there is a problem with our board, e.g. if it did not power up, then the DK doesn't see it and assumes the FW loading is meant for itself. Since the DK serves no function in this setup other than as a pass through FW programming device our Contract Manufacturer can't tell the difference and believes the FW load succeeded.

On my engineering bench I'm using a JLink direct to our product so I can load and run our program and check the log to see that the proper FW was installed and that the board is working. However on Manufacturing's DK based system all I know is that the FW loaded... but not which board (DK vs ours) saved the image.

Is there a way to force the FW load to go out through P20 and indicate a failure if nothing is there?

If not, is there a way to detect before loading FW which board is connected to the debug chip or (less ideal) detect which board got the image update... ours or the DK?

At one point I saw a "Device...selected" message that said 'NRF52" in one case and "NRF52832-XXAA" in another case, but was not able to convince myself that this was a reliable way to determine which board the DK Debug chip thought it was connected to.

Thanks, Jeff

Parents Reply Children
No Data
Related