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

Difficulty flashing (or seeing) external board using NRF52-DK

(I've seen several other posts mentioning similar issues, but many of them haven't resolved or found a solution that seems to apply in my case.)

I have a custom board that uses the nRF52832. I'm trying to flash a software image to it, but get errors when using nrfjprog in the terminal, and a reboot of the devboard when I try to select the device in nRF Go Studio (taking me back to the main screen, where I can try to select it under 'NRF52 development boards' again, which inevitably yields the same result).

The terminal output when running nrfjrpog is:

-------------------------------------------------------------------------------- 
nrfjprog --family nRF52 --log --program ./examples/peripheral/blinky/hex/blinky_pca10040_s132.hex 
nrfjprog verion 9.7.2 
-------------------------------------------------------------------------------- 
FUNCTION: open_dll. 
FUNCTION: open_dll. 
FUNCTION: enum_emu_snr. 
FUNCTION: enum_emu_snr. 
FUNCTION: enum_emu_snr. 
FUNCTION: enum_emu_snr. 
FUNCTION: connect_to_emu_with_snr. 
FUNCTION: connect_to_emu_with_snr. 
FUNCTION: connect_to_emu_without_snr. 
FUNCTION: enum_emu_snr. 
Device "NRF52832_XXAA" selected. 
FUNCTION: read_device_version. 
FUNCTION: read_device_version. 
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1. 
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102. 
FUNCTION: close_dll. 
FUNCTION: close_dll.

The external board is separately powered, and wired to the development kit in the way described by this diagram:

I'm attaching the circuit for the custom board as well, in case there's an obvious issue with it that I'm not seeing:

(The INT and AD0s are all from sensors, which are connected via I2C.) 

Parents Reply Children
Related