Skip to main content
Associate III
September 30, 2026
Question

Download Verification Failed when programming stm32L152

Hardware used:STM32L152 Custom board 

I've been using a STM32U585 Discovery kit for a few days and have succesfully run several programs on it. However today I suddenly got this error in STM32CubeIDE when trying to run a new program:

---------------------------------------------------------------------------------------------------------------

Error: Data mismatch found at address 0x0800899C (byte = 0x31 instead of 0x33)

Error: Download verification failed

---------------------------------------------------------------------------------------------------------------

Trying to upload different programs gave the same result, but with the mismatch at different addresses.

First time the code programmed successfully in the memory. After whenever I tried to program it using stmcube ide or stmcube programmer, it gives the verification failed error in the stmcube programmer and failed to erase memory in stmcube ide. 

I have no option bytes enabled. I can erase the memory using stmcube programmer but stmcube ide gives the error and does not allow to program the mcu. 

Please help me to find the solution of this issue. 

 

 

4 replies

Explorer
October 1, 2026

Same issue in here working with a STM32H757XIH6 based device.

AScha.3
Super User
October 2, 2026

Different cpu, different st-link…. NOT “same” !

so make new thread with your question and give detailed info about your setup.

If you feel a post has answered your question, please click on " Best Answer ".
TDK
October 1, 2026

​@shefu 

I would look to see that power is sufficient, decoupling caps are present. 3.45 V is higher than typical. It’s technically in spec, but why isn’t this lower? Post the schematic if you can.

 

How is it hooked up to the programmer? Long leads may not be reliable. What programmer are you using?

 

​@tisauro Same questions to you, but since you are on a different chip, on a different board, please create a new thread and answer them there.

"If you feel a post has answered your question, please click ""Accept as Solution""."
Explorer
October 2, 2026

Looks like in my case was just a bad connection