Stm32 hal 开发
- 作者仓库星标 530
- 作者仓库 embed-ai-tool
STM32 HAL Development
Treat this skill as the working playbook for CubeMX-based STM32 projects.
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 drivers
- references/hal-quick-reference.md for API lookups
- references/troubleshooting-guide.md for failure analysis
- references/usage-examples.md for implementation patterns
- Reuse assets/bsp-template.c and 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
.iocconfiguration.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @LeoKemp223 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Workflow
Read references/core-guidelines.md first. Keep all custom code inside USER CODE regions unless the project has an explicit non-CubeMX extension point. Configure peripherals in CubeMX, regenerate code, then add application or BSP logic.
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.
# 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. 证据边界与执行链路
作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Workflow → Notes
要点 -> 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.
文件/命令 -> 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
内容 SHA-256 -> 9033e8a35636
方法与流程
适用与边界
原文中的明确线索
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