STM32CubeF4
STM32CubeL4
STM32CubeF4 | STM32CubeL4 | |
---|---|---|
10 | 6 | |
799 | 248 | |
3.3% | 2.8% | |
6.5 | 6.2 | |
21 days ago | 11 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.
STM32CubeF4
-
ARM vector table & address space question
2b. I think the more interesting thing for you to look at is the linker script (example). This tells the linker where to put sections (data, bss, rodata, etc). Here you can see where exactly the isr_vector goes and the section it comes from
-
Would Vale count as a low-level language?
Most chip vendors offer a "HAL" or hardware abstraction layer, which is basically a set of functions and defines that does all of this low level stuff. Here's an example of one for STM32F4 chips. The CMSIS folder contains code that is common to most ARM Cortex-M devices, and the STM32F4xx_HAL_Driver folder contains the actual HAL. And here's an example of a startup script and a linker script.
-
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
-
cubeide
Download the firmware package for your series. Here is the F4 series. Look under the "projects" folder.
-
How do I "replicate" an IDE like the Keil uVision or the TI CCS using Visual Studio Code?
Lastly, and I think these were the hardest things to find when I was transitioning away from Keil, is all of the vendor-specific and compiler-specific “glue” like startup files and linker scripts. For example, STM32F4 startup, system config, and linker scripts can be found here for various MCUs
-
Help with company culture towards compiler warnings
There's an open issue if you're interested in tracking progress on it.
-
Love and hate of ST HAL / pointer to volatile correctness
This 1.5Y old ticket proves the point https://github.com/STMicroelectronics/STM32CubeF4/issues/10 (do not hesitate to upvote this one as everybody agrees it needs to be modified).
-
What is the pre-installed program that comes with my STM32F429 Discovery board?
I think this would be the preinstalled program: https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Projects/STM32F429I-Discovery/Demonstrations/TouchGFX
-
Why is it so difficult to develop USB using HAL libraries
That's where I would begin for building new projects for interfaces and peripherals I don't already know well. However when you are just starting out with something, it can be even easier to modify a working example. Here's a source for official ST USB examples on STM32F4 MCUs: https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Projects/STM32446E_EVAL/Applications/USB_Device
-
What is a good comment header template where to put author, title of the source and date?
Clone STMCube repo https://github.com/STMicroelectronics/STM32CubeF4
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))
STM32CubeF7 - STM32Cube MCU Full Package for the STM32F7 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))
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
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))
gdb-dashboard - Modular visual interface for GDB in Python
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).
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families