Could not verify ST device on STM32F407VGT6

[untitled__666]

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]

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?

 

[untitled__666]

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

[Andrew Neil]

---

@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.

[AScha.3]

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

[untitled__666]

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

[untitled__666]

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

[AScha.3]

Maybe...or defective...or write protected (I had this once - no joke ! New chips from mouser - protected !)

So show, pic, not error message - this is useless,  CubeProgrammer, to both, and show, what its telling (chip ID etc.).

so:

 

[untitled__666]

Where can I find this information in the picture?

[TDK]

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