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!

[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?

[AScha.3]

using CubeProgrammer, then connect:

[untitled__666]

Is that so?

This is the information of the chip that cannot be burned.

[AScha.3]

So you get connected to the chip:

It's basically working ok,

And is F4xx type, good, so far.

Now try to flash a bin or hex file to the CPU.

If not possible, try doing mass erase, full chip erase , then try flashing.

If not possible, 

check the option bytes, but be careful, not to activate rdp Levels, this would brick the chip. Just set all memory to not write protected. Then flash your program.

[untitled__666]

I tried to program the chip using Keil and it worked successfully. Then I tried to re-burn the program using the CubeIDE again, but it still failed. The program code is the same.

[Andrew Neil]

As @TDK  (and I) suggested earlier, this smells like a fake ST-Link and/or fake STM32.

You still haven't said what ST-Link you are using.