I will open an issue for that, since that should be there.
You could only save it by including it from the previous framework-stm32cube.
Please note that
is technically wrong. framework-stm32cubef4 is the new package that the STM32 platform since version 10 uses. You still have the framework-stm32cube package from the last versions and include files from there in a project that uses the newer platform versions – that’s dangerous. No build_flags should be needed for the BSP anymore though if you have the variant option enabled now.
As a nicer workaroudn you can put the originally missing file in the include/ folder of the project and add -I include to the build flags and remove the reference to the framework-stm32cube folder.
So you would have to add those files yourself if you agree to the license.
Also note that per docs and releases you can choose to use an older platform version for a project, as in platform = email@example.com in the platformio.ini. Then it should work without any major modifications.
added to the .ini file. thanks !
For the newer projects i create, i still get my .json file listing all dependencies from framework-stm32cube and not stm32cubef4, which is present in the packages directory. wonder why that is if the stm32cubef4 was separately added with the update. on changing to stm32cubef4 in the .ini file i get,
Error: This board doesn’t support stm32cubef4 framework!
Nono, framework = stm32cube is correct to select the framework, it’s just that the internal PlatformIO package management has split up the STM32Cube packages into framework-stm32cubef4, framework-stm32cubef3 etc. The old ST-STM32 version had just one framework-stm32cube folder which contained everything.
So if one would just use the newest platform version from a clean installation, framework-stm32cube will not exist when using STM32Cube. Thus it’s needed to copy the missing header file, e.g.