STM32 on Zephyr, What You Need to Know
summary
Concrete answers about device setup and current limits: how to express device tree clock bindings and domain clocks (including USB/peripheral clocks and persistent clocks in stop mode), which DTS properties and pinctrl settings actually generate working register values, the state of power management levels and runtime/stop support and what fails today, how Trusted Firmware‑M flash partition mapping must match Zephyr partitions, how Cube packaging and GitHub patches are used and what actually builds and runs versus what remains partial.
AI-written summary · about
chapters (13)
- 0:00STM32 on Zephyr intro
- 2:07Porting peripherals and docs
- 8:15Driver abstraction and complexity
- 12:58Memory and flash size
- 16:38System clock config
- 23:05Pin control and properties
- 27:09Advanced properties and build
- 30:11Clock domains and specifics
- 34:50Gestion de l'alimentation et niveaux de puissance
- 36:08Secure firmware partitions
- 37:24Partition mapping example
- 38:18Community support and contrib
- 41:43Conclusion et questions
related talks
27mZephyr and Trusted Execution Environments
46mDevice Tree in Zephyr Project
41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con- 41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
43mBeyond Static Devicetrees: Implementing Runtime Hardware Dynamism in Ze...
33mZephyr Support for Heterogeneous SoCs
42mEnabling Zephyr on Your Hardware Platform
42mEnabling Zephyr on Your Hardware Platform