Skip to main content
Associate III
July 12, 2024
Solved

Issues in flashing new G473CB microcontroller - no STM32 Target found

Hi !

I got some samples of G473CBTx from ST through one of the official distributor, which were populated on prototype boards. I am trying to flash them, but unfortunately stumbled upon the "no STM32 Target found" error. I tried the following.

 

1. Use a different ST-Link programmer / Nucleo board from F3/G0 family

2. Double check the pinout with CubeMX file (I use CubeMX to generate the initial pinout assignment for ease of layout designing).

3. Check the voltage levels across the µC pins (VDD, VSS, SWDIO and SWCLK).

4. Use the NRST functionality along with ST-Link along with SWDIO and SWCLK.

5. Update the ST-Link driver of the Nucleo board / ST-Link programmer.

6. Try the new ST-Link software (STSW-LINK009)

 

My attempts are unsuccessful until now. It must be noted that the G431CBTx were already populated on similar prototype boards and are working properly as expected. I tried to flash the G431 with the same setup and could flash it successfully. But not with the G473x.

It will be great to have some suggestions on what I might be doing different. Thanks in advance!

 

 

Update -> issue was with capacitance on the lines.

This topic has been closed for replies.
mechatronBest answer
Associate III
November 20, 2024

The issue was with the capacitance on the lines. Once it was reduced, programming frequency could be increased in MHz range.

3 replies

mechatronAuthor
Associate III
July 12, 2024

Update - by lowering the Frequency from 4 MHz to 125 kHz (and lower), I could program the µc. Any idea why this could happen, despite the connection being < 30cm in length (works like a charm with F3x and G43x family).

mechatronAuthorBest answer
Associate III
November 20, 2024

The issue was with the capacitance on the lines. Once it was reduced, programming frequency could be increased in MHz range.

mechatronAuthor
Associate III
July 31, 2024

Hi !

 

Any helpful comments/suggestions?? The issue still exists.