How to download firmware nrf52832 to the other nrf52832?

[ENENER]

Hi.

I am going to make my own PCB with nrf52832.

Before making it, I have to check debugging through P20 in nrf52832 DK.

I have two nrf52832 DKs with SDK17.0.0.

I will call first nrf52832  No1, and the other No2 for understanding.

So, I connected No1's GND, SWDCLK, SWDIO and VDD to No2's same part.(I connected No1's P20 to No2's P20)

Also, I connect USB to No1. And, I connected external VDD to No2.

Then, I run nRF Connect's Programmer to download firmware to NO2.

But, there are only No1. I want to check No2.

How to I download firmware to No2 through No1?

I attached picture for your understanding.

Thanks

[Jørgen Holmefjord]

Hi,

In order for the debugger on DK No1 to detect that an external board is connected, you need to connect VDD from the external board to VTG pin. If the debug chip detects voltage on this pin, the external board will be programmed, else the on-board nRF52 chip on DK No1 will be programmed.

If DK No2 is powered externally, there is no need to connect VDD_NRF together.

When programming from the nRF Connect application (or nrfjprog), you will only see the debugger on DK No1, it is not possible to select from the application which nRF52 chip should be programmed, this is decided solely from the state of the VTG pin.

Best regards,
Jørgen

[Jørgen Holmefjord]

What exactly do you mean by "But, the nRF Connect still only see No1"? As I mention, nRF Connect will only show the COM port and serial number of the Interface MCU/J-Link debugger chip. You select the serial number of DK No1 in nRF Connect and it will program No1 or No2 based on if VTG is connected to VDD of the external board or not. Have you tested this? Are you not able to program the external board?

As a test, you can flash a blinky application to the No1 DK, then perform an erase operation from nRF Connect programmer after connecting VTG. If DK No1 still blinks, the programmer have programmed No2.

[Jørgen Holmefjord]

Try connecting GND from one board to GND on the other instead of connecting the "GND Detect" pins together. These pins are connected to the interface MCU only, so there may be different ground levels on the boards.

[ENENER]

I tried the way that you told me.

But there is still error message. "Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)" 

[Jørgen Holmefjord]

I still think there is some issue with how board No2 is powered. Can you post an image showing how everything is connected, and how the board is powered? (Not a schematic, and actual image of your physical setup and connections)

[ENENER]

Here!

[ENENER]

hI Jorgen

Could you tell me more advise?

[Jørgen Holmefjord]

Sorry for the slow response. I tested the same connections, and I am also not able to program the external board. Getting the same error.

Programming through the 10 pin debug out/debug in connectors (P18/P19) work fine though. I see that P20 and P19 connectors have different inputs to the on-board debugger chip. It is possible that P20 can only be used for Debug output, and not input. The P18 connector is connected directly to the SWD lines of the nRF52832, without going through the J-Link debugger. 

If you create your own  custom board, you will not face this issue, as you will not have the on-board debug chip and the SWD pins will go directly to the nRF52832 chip. If you want to test with the DK, you need to get a "breakout cable" for use with P18 connector.