Not able to flash ISC-nRF52810-A using nrf52 DK (nrf52832)

[Sujiv0]

I bought both nrf52 DK with nrf52832 and ISC-nRF52810-A module. I use Visual Studio Code with nrf SDK + toolchain.
Hardware connection from ISC-nRF52810-A to nrf52 DK is as follows, (based on nrf52 DK User Guide 4.8.2)

• P20-1 VDD_nRF to NC
• P20-2 VDD to ISC-nRF52810-A VDD
• P20-3 VTG to P1-VDD
• P20-4 SWDIO to ISC-nRF52810-A SWDIO
• P20-5 SWCLK to ISC-nRF52810-A SWCLK
• P20-6 SWO to NC
• P20-7 RESET to ISC-nRF52810-A RESET
• P20-8 to P1-GND
• P1-GND to ISC-nRF52810-A GND

But whenever I flash the application, nrf52832 in the DK is getting flashed, even though the connected device in the GUI shows nrf52810.

Sample application: Peripheral LBS

Advance thanks for any help.

Sujiv0

[Einar Thorsrud]

Hi,

If the onboard device is programmet, there is a problem with the connection to the external board. The connections should be as shown in Programming an external  board. I wonder if you have connected the SWD0_SELECT to ground? If not, the onboard debugger will debug/program the onboard nRF.

PS: The target board in you screen shows what you build for, but does not tell you anything about which device is being debugged.

[Sujiv0]

Hi Einar Thorsrud , I'm using SWD1 port via P20 of nrf52 DK. SWD1_SELECT (VTG) Pin-3 is connected to VDD as per the Programming a board with custom connections.

Connected device shows as follows,

But when I flash the application, it shows 

But nothing gets flashed to nrf52810 module.

[Turbo J]

How do you know? I am asking because even blinky sample won't run properly when the LF clock is messed up (like no crystal connected).

Did you try reading the flash with nrfjprog or nrfutil?

[Sujiv0]

I'm checking whether any Bluetooth is shown in my android phone.

This (indiesemic.com/.../683ee380f6137a265ce71620) the module I'm using. 

As of now, I installed only the nrf extension and SDK for Visual Studio Code.

Please enlighten me about nrfjprog or nrfutil

NB: I'm a newbie in the NRF world.

[Turbo J]

Fist steps: Get Segger RTT working on the DK with a sample (like blinky). Then learn what the "Debug" button does.

THEN you can try running stuff on an external board. With Segger RTT and a debugger you can see at least somewhat where problems occur.

[Sujiv0]

Let me try the debugging options.