AnsweredAssumed Answered

PlatformIO stm32cube framework isn't complete

Question asked by Jur Div on May 16, 2018
Latest reply on May 18, 2018 by waclawek.jan

I am using PlatformIO to program the STM32 F7 discovery board. The STM32Cube package is in the PlatformIO's framework registry and HAL&CMSIS drivers are working out of the box without problems.

Since I am not using any RTOS and only trying small examples at the moment, I noticed that the PlatformIO version of stm32cube is not complete. It (for example) doesn't include BSP drivers and it doesn't include STemWin library.
Why is that? At the moment I am using manually downloaded STM32CubeF7 package and including BSP drivers manually and unsucessfully including STemWin library manually as well. It involves a lot of "hacking" around (include paths, compilation options etc.), which doesn't make sense- since the stm32cube (and PIO library manager) was designed to "make developer's life easier"


It's confusing that the PIO version of stm32cube is not the same as the "official" one. If there's some reason I missed in all this? Would it be possible to make BSP and Middlewares (STemWin) "official" libraries, so you could add them via PIO Library Manager?


Also, the official PIO version of the BSP library is compatible only with mbed framework. Why couldn't one use it only with stm32cube framework (HAL)...? I could find and official or complete STemWin library in the PlatformIO library registry.

Thank you for help,