Update tool ST-LINK gives old firmware?

[Willunen]

Posted on January 11, 2017 at 09:44

Hi, newby here. I recently bought two discovery boards from Conrad.nl.

One with a STM32F100RTB and the other with a STM8S003K3T.

Now I wanted to upgrade the firmware of the integrated ST-LINK modules on the Discovery boards. According to the documentation :

On ST-LINK/V2-1 boards, upgrade firmware to the version V2J28M

On ST-LINK/V2 boards, upgrade firmware to the version V2J28S7.

On ST-LINK boards, upgrade firmware to the version V1J13S4.

But in my case the STM32 board is updated to firmware V1.JS0

And worse, the STM8 board to firmware V1.J0.S4

This version seems to be too old for the ST-LINK Utility.

What am I doing wrong?

Regards,

Wilko Lunenburg

Note: this post was migrated and contained many threaded conversations, some content may be missing.

[Khouloud GARSI]

Posted on January 11, 2017 at 12:47

Hi

Lunenburg.Wilko

,

What is the version of the firmware upgrade application you are using?

Please make sure to use the last one available on ST website:

https://my.st.com/content/my_st_com/en/products/embedded-software/development-tool-software/stsw-linklicense%3d1484131860html

.

If you were not using the last version, please remake the upgrade procedure and tell me to which version your firmware is upgraded?

Khouloud.

[Willunen]

Posted on January 11, 2017 at 13:39

Hello Khouloud,

Yes, I did use the lastest version of the firmware upgrade application. To be absolutely sure, I downloaded the application again via your link. But the results are the same.

Regards,

Wilko

[Khouloud GARSI]

Posted on January 12, 2017 at 14:52

Hi Wilko,

Refereing to the technical note

http://www.st.com/content/ccc/resource/technical/document/technical_note/group0/30/c8/1d/0f/15/62/46/ef/DM00290229/files/DM00290229.pdf/jcr:content/translations/en.DM00290229.pdf

section3:

• V : major version ID. (1 for ST-LINK)
• J: version for STM32 debug interface (JTAG and SWD protocols). 

       In your case J=13 (this is the most recent version for the STM32 debug interface.)

• S: version for STM8 debug interface (SWIM protocol). In you case, S=0 -> This means that the STM8 debug interface is not supported by your board.

-> The upgrade was done conveniently: you have got the last version of 

STM32 debug interface but the STM8 debug interface is not supported.

Khouloud.

[Khouloud GARSI]

Posted on January 12, 2017 at 16:29

Hi Avatar,

I interpret you post that he probably needs to download a separate update for his STM8 board, and the 'SWIM' debug interface.

In the previous post, I was talking about the STM32VLDiscovery (

STM32F100RB MCU) and not the STM8 board.

Khouloud.

[AvaTar]

Posted on January 12, 2017 at 15:49

That might explain the result, but seems not very helpful for the O.P., though.

I interpret you post that he probably needs to download a separate update for his STM8 board, and the 'SWIM' debug interface.

BTW, I would scrap the ST_LINK V1 altogether, it is a complete failure. I rather use newer, external ST-Link V2 board to debug my old VL-Discoveries ...

[AvaTar]

Posted on January 12, 2017 at 16:32

The OP mentioned a STM8S003K3T in his first post. I suppose that one has a SWIM interface, and need a different firmware.

[Khouloud GARSI]

Posted on January 12, 2017 at 17:58

Hi,

The OP mentioned a STM8S003K3T in his first post.

And worse, the STM8 board to firmware

V1.J0.S4

For the STM8 board, t

he STLink firmware is also upgraded correctly:

• V : major version ID. (1 for ST-LINK)
• J=0 ( because

  STM32 debug interface is not supported on the board)

• S: version for STM8 debug interface (SWIM protocol). Here S=4 -> which

   is the most recent version for the STM8 debug interface.

Khouloud.

[Tesla DeLorean]

Posted on January 12, 2017 at 17:17

This is an older version of just the update, you might be able to stage the older unit through this and update to most current from there.

https://drive.google.com/open?id=0B7OY5pub_GfIR2taa1YzWEJtTmM

 

[Tesla DeLorean]

Posted on January 12, 2017 at 17:22

As I recall the updaters contain multiple images, I've attached a link to my mirror of one of the older ones, but have a collection.

Would agree that the V1 is rather sad, and might not be supported by newer drivers/dlls moving forward, I remember having to fight one of my systems back in the day to get things working, but that's been a couple of years ago.