connection issues with my new ST-Link v3 MINIE

[mstreicher]

Hi,

I am designing a custom PCB with an STM32H723. To programm it, i bought a brandnew ST-Link v3 MINIE. CubeIDE reads the serial number of the V3 but can not connect to the target.
- Target is supplied with VCC.
- From the Board-to-Board-Connector after a lengthy search i connected TMS to SWDIO, TDI to SWO. RESET, CLK, GND and VCC where obvious.
- BOOT0 i connected to GND.
- Config as follows:

starting debuging i get this return:

[EDIT: solved sidequest] Searching for solutions i found the programm ST-Link Utility and wanted to start by updating the firmware but the V3 gives me a communication error.

When i klick ok, sometimes a version is read and the "Yes" button for upgrade is enabled. But when i klick it i get another error:

I tried a different V3MINIE even a new USB-cable for this.
[EDIT: Solution for the sidequest] Use the upgrade only software named ST-LinkUpgrade.exe : https://www.st.com/en/development-tools/stsw-link007.html

My question: what am i missing?

[TDK]

Use STM32CubeProgrammer. ST-Link Utility has been deprecated for many years now.

How is your board powered? The programmer does not provide power. Ensure the voltage in STM32CubeProgrammer is reflected correctly after you hit connect.

 

[mstreicher]

Thanks for the Tip.
After I used the right File to install CubeProgrammer *facepalm* it gave me a valid Voltage and Firmware Version: 

but the log tells me, i should use Debug Authentication

after a little search i found this Command Line:

Is there annything else i can do?
I am starting to think the MCUs of all my three prototypes could be fried.

[mstreicher]

I took one MCU off the PCB, cleaned everything and soldered it back in place. CubeProgrammer actually connected and could read!

Then i tried debug mode in the IDE. It workt at first and then lost connection before it was ready for the play button. (unfortunatly lost te log of this part) I tried to reconnect in CubeIDE or CubeProgrammer with no success.

I am absolutely riddeled! Is there any false setting which could cause this kind of error?

[TDK]

Sounds like you may have some workmanship or design issues on the board. If you include the schematic, I'll take a look. A large high-res in focus picture of the board may help as well.

[Christian N]

This post has been escalated to the ST Online Support Team for additional assistance. We'll contact you directly.

Regards,
Christian