Nucleo-64 ST-LINK Fails with External PCB (But Works with ST-LINK V2)

[Manowi25]

Hello,

I previously used ST-LINK V2, which worked fine, but due to its lack of a Virtual COM Port (VCP), I recently purchased a NUCLEO-64 (STM32F030R8 EVAL BRD) to program my own PCB using its ST-LINK.

The Nucleo board itself works fine, but when I try to use its ST-LINK to program my own PCB (using STM32G030F6P6TR), I encounter issues despite following the manual:

What I Have Done:

• Removed CN2 jumpers to enable external debugging.
• Wired ST-LINK (CN4) to my PCB:
  • VDD_TARGET → My PCB’s 3.3V
  • GND → Shared with Nucleo
  • SWCLK → My PCB's SWCLK
  • SWDIO → My PCB's SWDIO
• Powered my PCB with an external 3.3V source.

What Happens:

• Without external power: STM32CubeProgrammer does not connect.
• With external power: CubeProgrammer connects but disconnects after ~10 seconds, then crashes.

I have been troubleshooting this for days but found very few resources on using a Nucleo board's ST-LINK for external programming.

As mentioned, the Nucleo board itself works fine, and my PCB works with ST-LINK V2, but not with this Nucleo ST-LINK.

Do you have any insights on why this might be happening?

[TDK]

> Without external power: STM32CubeProgrammer does not connect.

This is expected as CN4 does not provide power.

> With external power: CubeProgrammer connects but disconnects after ~10 seconds, then crashes.

Any error messages? Does lowering the speed help? Updated ST-Link firmware?

Ground loops could always cause an issue. Can you power it from the nucleo board and see if that changes things?