cancel
Showing results for 
Search instead for 
Did you mean: 

connection issues with my new ST-Link v3 MINIE

mstreicher
Associate II

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:

mstreicher_1-1755678605652.png

starting debuging i get this return:

mstreicher_2-1755678672792.png

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

mstreicher_0-1755678308025.png

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:

mstreicher_3-1755679569141.png

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?

5 REPLIES 5
TDK
Super User

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.

TDK_0-1755693571211.png

 

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

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

mstreicher_0-1755762304389.png

but the log tells me, i should use Debug Authentication

mstreicher_1-1755762416252.png

after a little search i found this Command Line:

mstreicher_2-1755763525445.png

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

mstreicher
Associate II

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

funzt endlich.PNG

mstreicher_0-1755778319823.png
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
Super User

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.

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

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

Regards,
Christian