stm32 hal development
- Repo stars 530
- Author repo embed-ai-tool
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @LeoKemp223 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# STM32 HAL Development
Treat this skill as the working playbook for CubeMX-based STM32 projects.
## Workflow
1. Read [references/core-guidelines.md](references/core-guidelines.md) first.
2. Keep all custom code inside `USER CODE` regions unless the project has an explicit non-CubeMX extension point.
3. Configure peripherals in CubeMX, regenerate code, then add application or BSP logic.
4. Read additional references only as needed:
- [references/peripheral-driver-guide.md](references/peripheral-driver-guide.md) for sensor and bus drivers
- [references/hal-quick-reference.md](references/hal-quick-reference.md) for API lookups
- [references/troubleshooting-guide.md](references/troubleshooting-guide.md) for failure analysis
- [references/usage-examples.md](references/usage-examples.md) for implementation patterns
5. Reuse [assets/bsp-template.c](assets/bsp-template.c) and [assets/bsp-template.h](assets/bsp-template.h) when starting a new BSP module.
## Notes
- Prioritize hardware constraints, interrupt safety, and regeneration safety over local code convenience.
- Do not modify CubeMX-generated initialization files directly when the same change belongs in the `.ioc` configuration.
Sections and files
Listed in source order.
sections -> Workflow → Notes
terms -> Treat this skill as the working playbook for CubeMX-based STM32 projects. · 1. Read [references/core-guidelines.md](references/core-guidelines.md) first. · - Prioritize hardware constraints, interrupt safety, and regeneration safety over local code convenience.
files/cmd -> USER CODE · .ioc · references/core-guidelines.md · references/peripheral-driver-guide.md · references/hal-quick-reference.md · references/troubleshooting-guide.md · references/usage-examples.md · assets/bsp-template.c
body sha256 -> 9033e8a35636
Workflow
Read references/core-guidelines.md first. Keep all custom code inside
USER CODEregions unless the project has an explicit non-CubeMX extension point. Configure peripherals in CubeMX, regenerate code, then add application or BSP logic. Read additional references only as needed: references/peripheral-driver-guide.md for sensor and bus driversNotes
Prioritize hardware constraints, interrupt safety, and regeneration safety over local code convenience. Do not modify CubeMX-generated initialization files directly when the same change belongs in the
.iocconfiguration.