Skip to main content
Gaston
Associate III
December 30, 2024
Question

cannot communicate STM32CubeProgrammer with STM32G030 ST Embedded bootloader

As described in RM0444

Gaston_0-1735585242552.png

I understand my virgin device (STM32G030C6T6) should to connect via UART using STM32CubeProgrammer but as shown I'm not able to establish the first transaction (byte 0x7F reception and answer)

Gaston_1-1735585427932.png

I've checked my custom board hardware and everything (voltages, consumption, PA14-BOOT0 unconnected, TX/RX pins w/100k-pull-up, etc) seems to be okay.

Any hints?

This topic has been closed for replies.

3 replies

MM..1
Super User
December 30, 2024

Are you sure you connect to 

MM1_0-1735587651220.png

 

Gaston
GastonAuthor
Associate III
January 8, 2025

Yes, these pins are connected and the configuration is okay. It's strange. I've connected the device via ST-LINK successfully and everything seems okay.


Gaston_3-1736326707288.png

 

Gaston_1-1736326457416.pngGaston_2-1736326580551.png

According to the RM if EMPTY-BIT is set Boot is forced to system memory so I expect to answer after a UART 0x7F request.

Gaston_0-1736326288499.png

Tesla DeLorean
Guru
December 31, 2024

So 48-pin device.

Check for other potential pin conflicts via AN2606. Chatter on other interfaces at startup by say a GPS/GNSS device might cause that interface to be identified first

It's not so much expecting to receive the 0x7F pattern as it is trying to time the pattern for auto-bauding. 

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..