Could not verify ST device on STM32F407VGT6

untitled__666 · ‎2025-07-23

I have already updated my CubeIDE to the latest version 1.19.0 available on the official website. After writing the code with it, I attempted to download it to my F407VGT6 via STLink, but the download has never been successful. It always prompts "Could not verify ST device!" When I replaced one board with another, I was able to successfully download. The only difference between the two boards is that the silk-screening of the two VGT6s is slightly different. One has a small circle with "e3" inside and can be downloaded, while the one that cannot be downloaded has "e4" in the circle. I wonder if CubeIDE has not yet adapted to this chip. Has anyone encountered the same situation? I hope to get your solution!

Karl Yamashita · ‎2025-07-23

Your title suggests that STM32CubeIDE can't be downloaded from ST's site. Maybe change the title to "Could not verify ST device on STM32F407BGT6"

Are you using a development board or a custom board?

I was told that if a devices starts to smoke, put the smoke back in. I guess I never got all the smoke because the device never worked afterwards.
Don't worry, I won't byte.
TimerCallback tutorial! | UART and DMA Idle with multiple UART instances tutorial!

If you find my solution useful, please click the Accept as Solution so others see the solution.

AScha.3 · ‎2025-07-23

Try connect with CubeProgrammer, to both, and show, what its telling (chip ID etc.).

If you feel a post has answered your question, please click "Accept as Solution".

untitled__666 · ‎2025-07-23

Thank you. I have already modified the title. Yes, I'm using a custom board.

untitled__666 · ‎2025-07-23

OK, I have uploaded the screenshot of the fault code.

Andrew Neil · ‎2025-07-23

@untitled__666 wrote:
Yes, I'm using a custom board.

Then you need to give details of that board - we can't see it from here!

Please see: How to write your question to maximize your chances to find a solution.

Is it, perhaps, a so-called "Black Pill"?

If so, it might have a fake STM32...

Also, what ST-Link are you using?

How to recognize a genuine ST-LINK/V2 versus a cloned one.

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.

untitled__666 · ‎2025-07-23

But actually, I don't think it's the problem of the board or the ST-LINK, because I have used the same ST-LINK and board for testing before. The only difference lies in the chip. When there is an "e3" silk-screen on the chip, it can be programmed; however, "e4" cannot.

untitled__666 · ‎2025-07-23

The same board, the same ST-Link programmer, but some chips just can't be programmed. Are the chips fake?!

TDK · ‎2025-07-23

Based on the screenshots, seems like the programmer is to blame, probably a fake. Show a picture of your programmer.

If you feel a post has answered your question, please click "Accept as Solution".

Karl Yamashita · ‎2025-07-23

That soldering looks pretty bad. Doesn't look like it was soldered flowed. I would double check to be sure there are no shorts.

I was told that if a devices starts to smoke, put the smoke back in. I guess I never got all the smoke because the device never worked afterwards.
Don't worry, I won't byte.
TimerCallback tutorial! | UART and DMA Idle with multiple UART instances tutorial!

If you find my solution useful, please click the Accept as Solution so others see the solution.