How janieblas/stm32f446e_whitout_stm32cubeide works
Main components
• Hardware & Development Environment: Include the STM32F446RE board; note that developers use WSL/Ubuntu running VS Code and the ARM Toolchain (e.g., ARM GCC).
• Boot & Startup: The startup code and linker scripts (across multiple experiments, e.g., in “e001_bare_metal”, “e002_add_cmsis”, etc.).
• Software Framework Layers:
– Low-level Hardware Abstraction: CMSIS components (found in directories named “CMSIS” across several experiments).
– HAL Drivers Layer: Provided for advanced peripheral initialization (as in “e006_hal_driver” and “e007_add_timebase_tim”).
– Application Code: The “main.c” files that implement the core application logic for each example.
• Debug/Utilities: Dedicated examples, such as the “e003_debugger” project, that integrate debugging configurations (like VS Code launch configurations).
Establish relationships and interactions
• That the HAL or CMSIS layers are “stacked”: the startup initializes the microcontroller and then hands off execution to main, which calls into the CMSIS routines and HAL driver functions to interface with hardware.
Architectural patterns and design principles
• Layered Abstraction: Clearly outline that hardware registers or the microcontroller’s low-level settings are abstracted by CMSIS and HAL libraries. This separation simplifies the development and testing processes.
• Build Abstraction: Note how using both Makefiles and CMake scripts provides alternative paths for building the firmware. Represent these in a “Build Tools” section.
• Reusability: Since many projects share common code (for example, the same CMSIS headers and startup routines), you might indicate a shared “Library” or “Driver” block that is re-used across examples.
Relevant technologies and frameworks
• ARM Toolchain (arm-none-eabi) – as the compiler and linker.
• CMSIS Core and Device Libraries.
• STM32F4 HAL drivers.
• Build tools: Make and CMake.
• Development environment: WSL (running Ubuntu) + VSCode.
• Hardware: STM32F446RE board.
• Clear labels for each component (e.g., “Development Environment”, “Startup Code”, “CMSIS Core”, “HAL Drivers”, “Application”, “Build System”).
– From development environment → build system.
– From build system → various layers (startup, CMSIS, HAL, application).
– Finally from compiled firmware → STM32F446RE board.
Happy diagramming!