STM32 ST-LINK Utility Programming error

[ame]

Posted on May 17, 2018 at 14:24

Hi everyone,

I have a very strange behavior using the STM32 ST-LINK Utility v4.2.0.0. While flashing a specific HEX file, the error message 'Programming error @ 0x08008C00' is occuring.

When I use the uVision Keil Flash Downloader with the same HEX file, no problem occures.

When I use the STM32CubeProgrammer with the same HEX file, no problem occures.

In the message log of the ST-LINK Utility the following logs are shown:

14:14:09 : STLink USB communication error

14:14:09 : Error occured during program operation!

14:14:10 : Programming error @ 0x08008C00!

So it looks like the STM32 ST-LINK Utility has a problem with this specific HEX file...

The file itself is for a STM32F105R8T6 application:

(From keil compiler) Program Size: Code=51352 RO-data=816 RW-data=924 ZI-data=29404

Has anyone also seen this behavior?

#stm32-f1 #st-link-utility-problem #hex

[Tesla DeLorean]

Posted on May 17, 2018 at 14:33

Stand-alone ST-LINK? Current firmware?

Different cable?

DELL machine? Windows 10?

Problem can be replicated on multiple machines?

[ame]

Posted on May 22, 2018 at 09:16

Hello Clive One,

• The ST-LINK is a buyable ST-Link/v2/ 01-0 STM32 / STM8 stand-alone (not a On-Print version)
• The Firmwares I've tried were V2.J30.S7 and V2.J29.S7
• I've tried with the delivered USB cables and with a higher quality USB cable, also with different download-speeds between 480kHz and 4MHz
• I've tried it on a Lenovo Laptop and a Lenovo Workstation, both with windows 10 and on a DELL workstation with windows 7

When I load a previous HEX file (because the program to download on the chip is a newer firmware and I tried the downloading with the 'older' firmware), all works fine:

• Old HEX File, flashing with ST-LINK Utility, HEX file checksum 0x0053775E, all ok
• New HEX File, flashing with ST-LINK Utility, HEX file checksum 0x0053EADF, failed
• Both the old and new HEX File can be flashed with the STM32CubeProgrammer

I think there is an issue in the ST-LINK utility or something in combination with the HEX file itself... What I've also seen, is that when the chip (STM32F105R8T6) is connected, the ST-LINK Utility shows a flash size of 128KBytes, I thought that this chip has 64KByte?