It looks like package "framework-stm32cube/f4" is outdated

today, after generating new code from STMCubeMX with support for timers,
I encountered a strange problem when compiling this new code in PlatformIO:

It looks like files in STM32Cube/f4 package (after using “platformio update” comand) are missing some lines that are present in official STM32Cube GitHub repository (STMicroelectronics/STM32CubeF4, I can’t insert more than 2 links :frowning: ) and that are being used in code generated by STMCubeMX.

Here is code from package that was downloaded by PlatformIO:
And here is code from GitHub repository:

It looks like files from PlatformIO package are outdated, you can even see in Windows Explorer, that their modification date is 26.10.2018.

After replacing problematic files with new ones from GitHub code compiles just fine.
Is there a possibility to update this package?

Thank you in advance for your help.

Haa … interesting … to check the state of the used M4 ST lib is on my agenda in the context of my problem described here: Nucelo-F446RE optimization issue

Anyway +1 for the update!!

The latest version provided by PIO is framework-stm32cube version 181130 aka 30. November 2018.
See Service End for Bintray, JCenter, GoCenter, and ChartCenter | JFrog.

Update-request issues in Issues · platformio/platform-ststm32 · GitHub please so that the developers can see it.

1 Like

I’m confused, I can’t find a git-repository for the framework-stm32cube package…? I wanted to help and submit a PR but don’t know how or where.

Oh, I guess the package is just a condensed and zipped version generated from the official repo of ST:
GitHub - STMicroelectronics/STM32CubeL4: STM32Cube MCU Full Package for the STM32L4 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits)) (and similar)

1 Like

Seems like the bintray packages there are created explicitly without them being in a github, or they’re in a private one. @valeros should now how it works internally.

1 Like

Yes, that is probably the case. I created a repository for it anyway and updated the framework sources.
To use the new versions just add this to platformio.ini:

platform_packages = 
    framework-stm32cube @
1 Like