-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STM HAL drivers are out of date #439
Comments
I am running into the same problem with a Nucleo STM32H743 board. Current stable framework version in CubeMX is 1.8.0 from May 29, 2020. In platformio, newest update is 1.3.0 from July 4, 2018. So more than 2 years and 5 releases old. Right now, a bare minimum project for the Nucleo board generated in CubeMX will not compile due to unimplemented functions and undeclared constants. Some error messages from the failed compilation:
....et cetera. Seems it's high time, the libraries get updated. At |
If anyone in platformio dev team would publish the package on Github it would be awesome. The stm32cube fw is released on Git and making it a submodule of the fw package solve it ig? Or some small changes can be done on the build script..... |
I made some rough changes that might solve the problem, not sure I correctly implemented them since I didn't read main.py... |
Yeah these versions are ancient. I'll just cut it short and generate a new package version of |
I've created a script which can automatically download the latest versions of STM32Cube packages for every available series (including G0, G4, L5, MP1 and WB which PIO's package doesn't have) and create a I'm currently testing the created packet. Compilation of the current STM32Cube-HAL-Blink example goes through for all boards plus a custom STM32H750VB board of mine.
The FW works for my board. Whether they work in all other cases is another question. I'll test as much as possible. |
Is there anything else we can do to help them update this? Maybe we should create a separate issue for the G0, G4, L5, MP1 and WB? |
Hey! Any updates on this? |
I wasn't really able to find time to do extensive testing of my framework package, so I'm appreciating support and testing from others regarding all the example projects here and more STM32CubeMX generated projects with like an RTOS etc. Also hoping for integration by @valeros :) |
Resolved in ec29fab. Sorry for such a late update. |
@valeros Thanks! |
Since it's in the dev branch you should be able to use it in a PlatformIO project just by replacing the
|
Is there any plan to solve/update this? The platformio STM32G0 drivers are almost 4 years old and missing some key bug fixes. |
I found framework-stm32cube\f4\Drivers\STM32F4xx_HAL_Driver haven't get updated for a year. This leads to some incompatability with code generated by STM32CubeMx using the newest framework from https://github.com/STMicroelectronics/STM32CubeF4. For example, htim2.Init.AutoReloadPreload is not defined in the old framework package and had to comment out manually.
I tried to manually include the newest driver but it wasn't working.
Here are the edits I made to my ini file:
They didn't work and I believe it was firmware package related because I got the following error (I only copied a section of it):
Is there any way to partially replace
FRAMEWORK_DIR
in the python scriptstm32cube.py
or update the framework package?The text was updated successfully, but these errors were encountered: