Failed to Connect to Target" Error in SEGGER Embedded Studio with nRF52832 Custom PCB using TC2030 and nRF52-DK

Hello Nordic DevZone community,

I'm currently facing an issue with programming my custom PCB, which houses the nRF52832 chip, using the nRF52-DK and SEGGER Embedded Studio (SES). I've set up the wiring between the nRF52-DK and my custom PCB based on the instructions and diagrams provided in the Nordic Infocenter, specifically from this link: External Programming Support P20.

The interface I'm using for this connection is the TC2030. When I attempt to flash the firmware onto the custom board by pressing 'F5' in SES, I consistently receive the error message: "Failed to connect to target". I've tried this with the custom PCB both powered and unpowered, but the result remains the same.

To provide more clarity:

  • I will attach a detailed diagram of the nRF52832 chip layout on my custom PCB.
  • I will also include a wiring diagram that showcases the connections between the nRF52-DK and the custom PCB.

I've ensured that the wiring matches the provided instructions, but I'm still unable to establish a successful connection. I would greatly appreciate any insights or suggestions on how to resolve this issue and successfully flash the firmware onto my custom PCB.

Thank you in advance for your assistance.

Here is a diagram of the nRF52832:

Parents
  • Thank you for your prompt response and recommendation. I understand the potential benefits of using a dedicated J-Link device for flashing. However, I'm curious as to why the nRF52-DK wouldn't serve the purpose in this case. Is there a specific limitation or compatibility issue with the nRF52-DK that would prevent it from successfully flashing the firmware onto the custom PCB? I was under the impression that the nRF52-DK could be used for such tasks. Any insights or clarifications on this would be greatly appreciated.

Reply
  • Thank you for your prompt response and recommendation. I understand the potential benefits of using a dedicated J-Link device for flashing. However, I'm curious as to why the nRF52-DK wouldn't serve the purpose in this case. Is there a specific limitation or compatibility issue with the nRF52-DK that would prevent it from successfully flashing the firmware onto the custom PCB? I was under the impression that the nRF52-DK could be used for such tasks. Any insights or clarifications on this would be greatly appreciated.

Children
Related