STM32CubeF7
STM32CubeL4
STM32CubeF7 | STM32CubeL4 | |
---|---|---|
1 | 6 | |
315 | 249 | |
2.2% | 3.2% | |
6.7 | 6.1 | |
about 1 month ago | 22 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
STM32CubeF7
-
New to STM32 and STM32CubeIDE
It also doesn't seem to be included in their STM32Cube package either: https://github.com/STMicroelectronics/STM32CubeF7/tree/master/Projects
STM32CubeL4
-
How to enable the ART Accelerator on STM32?
The bare minimum would be to include stm32l4xx_hal_flash.h and do:
-
The Rust conundrum
or UB, or platform defined, or some weird rule for (partial) retocompatibilty with C, or bad concurrency.. even the official STM hal still have issue with misuse of volatile and atomic that could potentially cause issue (https://github.com/STMicroelectronics/STM32CubeL4/issues/30). Simply sometimes C++ does not have way to fully express a safe API, so it became pretty much impossible to make a safe wrapping
-
to HAL or not to HAL - THE definitive answer
St HAL had and still have huge issues, there is no repo for the code, so you need to download the zip, and for a long time there was not even a issue tracker, I had many time issues and found out someone on the forum reporting the problem. Now at least we have issue tracker, but that made mode clear there are some interesting decision, like missing volatile and no plan to fix it: https://github.com/STMicroelectronics/STM32CubeL4/issues/30 https://github.com/STMicroelectronics/STM32CubeF4/issues/10
-
Love and hate of ST HAL / pointer to volatile correctness
Now my tricky question about volatile pointers is here https://github.com/STMicroelectronics/STM32CubeL4/issues/30
-
STM32L4R5 || read/erase/write internal Flash
This variable I got from an example: https://github.com/STMicroelectronics/STM32CubeL4/tree/master/Projects/NUCLEO-L4R5ZI/Examples/FLASH/FLASH_FastProgram
What are some alternatives?
STM32CubeF3 - STM32Cube MCU Full Package for the STM32F3 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))
STM32CubeF0 - STM32Cube MCU Full Package for the STM32F0 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))
STM32CubeH7 - STM32Cube MCU Full Package for the STM32H7 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))
STM32CubeF4 - STM32Cube MCU Full Package for the STM32F4 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))
STM32CubeL1 - Full Firmware Package for the STM32L1 series: HAL+LL drivers, CMSIS, BSP, MW, plus a set of Projects (examples and demos) running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits).
STM32F7xx-template - Template application for developing ChibiOS applications for cortex-F7 devices in vscode.
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families