STM32Cube L4 firmware v1.8.1 patch issue

[Innomatic]

Posted on July 24, 2017 at 05:43

STM32CubeMX v4.22 fails to merge L4 v1.8.1 patch with existing L4 v1.8.0 source tree. Instead it creates two distinctive trees, one for v1.8.0 and one for v1.8.1 when they are installed one after another, i.e. when you install v1.8.1 patch on top of existing v1.8.0 tree. Solution is to delete existing v1.8.0 repository entirely and install v1.8.1 from the scratch. I don't know it applies to other patches.

[Khouloud GARSI]

Posted on July 27, 2017 at 12:58

Hi

Lee.Sungjune

‌,

Thanks a lot for your feedback.

The issue is internally forwarded to our CubeMX team.

Khouloud.

[jeffl.kelley9]

Posted on August 29, 2017 at 20:16

Not interested in 'Patch' -- If version 1.8.1 exists, where do I download it from?

[Tesla DeLorean]

Posted on August 29, 2017 at 20:39

I had CubeMX download them and merged the trees from the .ZIPs in the repository, want me to mirror that?

I've argued multiple times that ST should provide a means to directly download these, or provide a torrent. This would increase the chance people could successfully download the files, and reduce the loading on the servers from recurrent and failing downloads of >600MB files.

[jeffl.kelley9]

Posted on August 30, 2017 at 17:09

I'm good now, I just hand-merged the patch by assuming any files in it took precedence.

[Tesla DeLorean]

Posted on August 30, 2017 at 17:17

Yes, I just had WinRAR unpack and replace in the same STM32Cube_FW_L4_V1.8.0 directory both files describe.

[Khouloud GARSI]

Posted on August 31, 2017 at 14:18

Hi

Kelley.Jeff

‌,

There is no STM32CubeL4 V1.8.1.

You have to download

http://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-embedded-software/stm32cubel4.html

and then apply

http://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-embedded-software/patch-cubefw-l4.html

. Sorry for any inconvenience this may have caused.

Khouloud.

[waclawek.jan]

Posted on August 31, 2017 at 14:26

Okay, and how is the patch applied? I could not find any document describing this procedure.

It's obviously not the standard

https://en.wikipedia.org/wiki/Patch_(Unix)

as produced by standard

https://en.wikipedia.org/wiki/Diff_utility

(which is a pity).

JW

[After Forever]

Posted on August 31, 2017 at 14:31

The standard UNIX patch format wouldn't work for binary files (like PDFs). In this case the 'patching' is just a matter of extracting the archive over the existing files of the previous version with rewriting the old files.

[waclawek.jan]

Posted on August 31, 2017 at 14:49

Jive Tihs wrote:

The standard UNIX patch format wouldn't work for binary files (like PDFs). In this case the 'patching' is just a matter of extracting the archive over the existing files of the previous version with rewriting the old files.

This is exactly why Cube sources ought to be distributed in a way traditionally used for sources. Removing binaries from the zips would slim them down significantly to sane size, while retaining all relevant functionality, except perhaps the closed-source parts, which could be quite easily distributed separately.

In this case the 'patching' is just a matter of extracting the archive over the existing files of the previous version with rewriting the old files.

Thanks, but I'd like to hear official position of ST on this one.

JW