Skip to main content
Visitor
August 3, 2026
Question

Uploading the Program on STM32G0B1KEU6 using STLINKV2.

  • August 3, 2026
  • 1 reply
  • 11 views

Hi everyone,

I'm currently bringing up a custom board based on the STM32G0B1KEU6 (UFQFPN32) and I'm stuck at the very first step. I can't get the MCU to respond over SWD.

I'm using STM32CubeIDE with an ST-LINK/V2, and every attempt to connect gives me:

Target no device found

Error in initializing ST-LINK device.
Reason: No device found on target.

The relevant part of the GDB server log is:

STMicroelectronics ST-LINK GDB server. Version 7.12.0

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 3333
SWD Debug : Enabled

Target no device found

Error in initializing ST-LINK device.
Reason: No device found on target.

The MCU is powered from 1.8 V. Since I thought the supply voltage might be the issue, I also powered it from 3.3 V, but the result was exactly the same.

I've already checked the following:

- SWDIO is connected to PA13.
- SWCLK is connected to PA14.
- NRST is connected with a 10 kΩ pull-up and 100 nF capacitor.
- VDD is present at the MCU.
- The PCB footprint and pin numbering have been verified against the STM32G0B1KEU6 datasheet.

One thing I'm unsure about is the BOOT0 configuration.

On this device, BOOT0 is multiplexed with PA14 (SWCLK). Unlike some other STM32 families where BOOT0 is often pulled low externally with a 10 kΩ resistor, I haven't added an external pull-down because the datasheet mentions an internal pull-down on the BOOT0 pin.

Could this prevent SWD from working, or should the debugger still be able to detect the MCU regardless of the boot mode?

Has anyone seen this behaviour on the STM32G0B1 series before? Is there anything specific to this family that I should check?

Any suggestions would be greatly appreciated. Thanks!

 

1 reply

Andrew Neil
Super User
August 3, 2026

Welcome to the forum

Please see How to write your question to maximize your chances to find a solution for best results.

In particular, as it’s a custom board, you need to post your schematic.

 

I'm using STM32CubeIDE with an ST-LINK/V2

What version of CubeIDE ?

Have you tried CubeProgrammer ?

 

Is it a genuine ST-Link ?

 

bringing up a custom board

Have you done basic checks - chip orientations, supply voltages, solder joints, etc ?

Is it a brand new design?

Do you have other examples of the board?

 

If it’s a new design, have you checked it against Application Note AN5096, Getting started with STM32G0 MCUs hardware development ?

 

See also:

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.