Skip to main content
Associate II
February 28, 2026
Solved

Unable to flash or debug using stlink-v3minie

  • February 28, 2026
  • 4 replies
  • 212 views

Hello!

I just bought the stlink-v3minie for myself but I am unable to flash my board using it. 

I can program my board with a borrowed stlink-v3pwr but not with the minie.

I have upgraded the firmware on it and it still doesnt work. It fails with this output:

ST-LINK SN : 003300313235510537333439
ST-LINK FW : V3J17M10
Board : STLINK-V3MINIE
Voltage : 3.28V
SWD freq : 8000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x451
Revision ID : Rev Z
Device name : STM32F76x/STM32F77x
Flash size : 2 MBytes
Device type : MCU
Device CPU : Cortex-M7
BL Version : 0x93

Opening and parsing file: ST-LINK_GDB_server_a28496.srec


Memory Programming ...
 File : ST-LINK_GDB_server_a28496.srec
 Size : 668.68 KB 
 Address : 0x08000000 



Erasing memory corresponding to sector 0:
Erasing internal memory sectors [0 6]
Error: failed to erase memory


Error: failed to erase memory
Encountered Error when opening C:\ST\STM32CubeIDE_1.18.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.100.202412061334\tools\bin\STM32_Programmer_CLI.exe
Error in STM32CubeProgrammer
Shutting down...
Exit.

 

Does anyone have any ideas on how to fix it or what I am doing wrong. 

Thanks in advance!

Best answer by Mrquokka

Ok turns out after updating all software it works now. My bad:grinning_face_with_sweat:

4 replies

AScha.3
Super User
February 28, 2026

Hi,

try connect with CubeProgrammer , set: hot plug, soft. reset ; 

connect ...?

- check: write protection : not set (on all sectors)

- do a full chip erase

- try: flash your prog

"If you feel a post has answered your question, please click ""Accept as Solution""."
MrquokkaAuthor
Associate II
March 1, 2026

Hi!

Thanks for the response!

I can connect via CubeProgrammer. I can also see that Write protection is not enabled on any sector. I did an erase but I am still unable to flash with the stlink-v3minie. If I use the stlink-v3pwr I can flash the chip.

 

Any other advice i greatly appreciated!

 

AScha.3
Super User
March 1, 2026

(This cannot be...!)

So how the target gets power ?  stlink-v3pwr ? and using miniE ?

+

Connect with CubeProgrammer, try to read and write some data from/to flash in the HEX view / edit window.

set: hot plug, soft. reset ;  try same.

Is connection to target stable if just let it be connected 10 mins or so ?

"If you feel a post has answered your question, please click ""Accept as Solution""."
MrquokkaAuthor
Associate II
March 1, 2026

The power is from a buck converter on my board which gets its power from a usb cable. The power is stable. I can repeatably progam my board using the stlink-v3pwr through the STDC14 cable. but when i swap it to the stlink-v3minie then it fails. I even tried different cables. 

To prove that its not power related, I now connected 3.3V directly from a lab psu.

Now when trying to make a screenshot showing that i can indeed edit memory with the minie I discovered that it sometimes works and sometimes doesnt. 

Could it be that I got a faulty stlink? (I doubt that)

Thanks for the response. 

AScha.3
Super User
March 1, 2026

I use a V3mods here and some V2-"sticks" , at work most time a miniE ; all working fine.

Why i asked about supply and connections:   i found the V3 much more sensitive to spikes or stray in, even the ground connection is critical, than old V2 versions. (Or i just got a super "sensible" device here.)

Problems then : debug not working, or only some seconds, etc.

I had the supply for target plugged to mains at wall and PC is on another - didnt work in useful way.

But when cables close together and target gets power from same power strip as PC - working fine.

So your >that it sometimes works and sometimes doesnt. < could come from ground/stray in.

Play a little with connections, where its plugged in , etc.

"If you feel a post has answered your question, please click ""Accept as Solution""."
MrquokkaAuthorBest answer
Associate II
March 1, 2026

Ok turns out after updating all software it works now. My bad:grinning_face_with_sweat: