Earlier versions of STM32CubeF2 ? (V1.1.2, 11-December-2015?)I

[Allen Huffman]

Posted on January 12, 2018 at 22:21

Are older versions of 

STM32CubeF2 available? I am trying to find some files that were not included in a project I am working on. From looking at some of the files we do have, I see:

  * @version V1.1.2

  * @date    11-December-2015

Several files I checked match that, so I think I am looking for V1.1.2.

Any pointers where to look? My searches didn't lead me to any answers.

Thanks!

[Bogdan Golab]

Posted on January 12, 2018 at 22:49

Try this trick:

-generate simple project file using CubeMX

-close the CumeMX

-edit the project_name.ioc file, find something like that(this one is for F103): ProjectManager.FirmwarePackage=STM32Cube FW_F1 V1.2.0

-replace the the number with the one you are looking for

-start the CubeMX

-generate code - the CubeMX will complain about lack of the librarry you are using and will download the library

It worked for me for F103

[Bogdan Golab]

Posted on January 12, 2018 at 22:51

[Bogdan Golab]

Posted on January 12, 2018 at 22:53

CubeMX has v1.3.1 of my F1 library so I edited the  ioc file and entered the 1.2.0 to stimulate the CubeMX to use older package and make it download the package:

ProjectManager.CoupleFile=false

ProjectManager.CustomerFirmwarePackage=

ProjectManager.DefaultFWLocation=true

ProjectManager.DeletePrevious=true

ProjectManager.DeviceId=STM32F103C8Tx

ProjectManager.FirmwarePackage=STM32Cube FW_F1 V1.2.0

[Bogdan Golab]

Posted on January 12, 2018 at 22:57

Or another idea  - try to guess a path. In my case the path was as follow

www.st.com/resource/en/firmware2/stm32cube_fw_f1_v120.zip

[Bogdan Golab]

Posted on January 12, 2018 at 23:08

In your case you need to guess the exact F2 lib version because the 1.1.2 seems to not exits

[Bogdan Golab]

Posted on January 12, 2018 at 23:11

I discovered that the pattern for F2 is as follows:

http://www.st.com/resource/en/firmware2/stm32cube_fw_f2_v110.zip

It seems that 1.1.2 does NOT exist

[Tesla DeLorean]

Posted on January 13, 2018 at 01:11

1.1.1 was a delta from 1.1.0 (ie unpacks into the same directory tree adding or overwriting some files)

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

 

[Bogdan Golab]

Posted on January 12, 2018 at 23:13

I hope the ST moderator will not ban me because of this reverse engineering.

[Pavel A.]

Posted on January 12, 2018 at 23:19

Just don't try anything like this with the jive platform anymore

[Bogdan Golab]

Posted on January 12, 2018 at 23:22

Yes, right. I believe that jive is self-destroying beast;) Just because of built-in complexity.

[Allen Huffman]

Posted on January 15, 2018 at 19:49

I had some projects using later versions (from just a few months ago), so I decided to update them while I was at it. It appears the version numbers have been removed from the header comments in the files (@version and @date). For tracking purposes, I'm going to start checking in the Release Notes file(s) so we at least know what version we are using.

Is there a different way to tell versions of the current HAL code?

[Tesla DeLorean]

Posted on January 15, 2018 at 20:32

Usually the code is placed in the repository with a directory name reflecting the primary release. The Z in vX.Y.Z is usually provided as a small differential patch.

CubeMX can download different versions of the code. You should perhaps add your own notes/comments in USER sections of your project code reflecting when it was built and the versions of libraries and tools used. Here we also archive libraries and documentation.

[Allen Huffman]

Posted on January 15, 2018 at 22:12

We are working with legacy repositories and projects, so our ability to change things is limited.

However, as soon as we make a new, clean project, there will be changes. Many changes.

[Allen Huffman]

Posted on February 02, 2018 at 21:51

Looking at a recent package, en.stm32cubef2 (v1.6.0), I see that the HAL inside is labeled as 1.2.1:

  * @file    stm32f2xx_hal.c

  * @author  MCD Application Team

  * @version V1.2.1

  * @date    14-April-2017

How do I find which version of CubeF2 contains HAL 1.1.2?

We are having issues with UART code, as it turns out, and release notes show some changes happened with 1.1.3. We are trying to get an unmodified 1.1.2 to make sure it wasn't some customization we made years ago.

[Allen Huffman]

Posted on March 12, 2018 at 15:39

Beyond installing the Cube software and doing the config hacks, mentioned above, does anyone know how I can get F@ HAL version:

V1.1.3 / 29-June-2016

[Tesla DeLorean]

Posted on March 12, 2018 at 23:40

The minor version seems to have been deprecated, so unless someone posts something they pulled contemporaneously it might be a dead end.

I have a version of CubeMX I upload in July 2016, but don't see any F2 packages on any of the boxes to hand.

DAHMEN.IMEN

‌

st.mcu

‌ is this minor delta available for download anywhere?

Also noticed that new downloads have the date/version removed from the example files. Saw that as I merged code into newer donor projects.

[Tesla DeLorean]

Posted on March 14, 2018 at 13:46

I tried installing an old CubeMX 4.4 version, but it can't connect home, server or settings seem to have been long deprecated.

Not entirely sure the version ♯ in the HAL examples tracks the downloads very well, as you noted earlier.

STM32Cube\Repository\STM32Cube_FW_F2_V1.4.0\Projects\STM322xG_EVAL\Examples\ADC\ADC_DualModeInterleaved\Src\main.c

/**

  ******************************************************************************

  * @file    ADC/ADC_DualModeInterleaved/Src/main.c

  * @author  MCD Application Team

  * @version V1.1.2

  * @date    01-July-2016

  * @brief   This example provides a short description of how to use the ADC

  *          peripheral to convert a regular channel in Dual interleaved mode.

  ******************************************************************************

  * @attention

  *

  * <h2><center>&copy; COPYRIGHT(c) 2016 STMicroelectronics</center></h2>