[][src]Crate drone_stm32_map

STM32 peripheral mappings for Drone, an Embedded Operating System.

This crate uses CMSIS-SVD files provided by STMicroelectronics to automatically generate Drone register and interrupt bindings. However only the corresponding Reference Manual is the single source of truth. A difference between this crate bindings and the Reference Manual is considered a bug. Fixing such a bug is not a breaking change.

This crate re-exports the contents of drone_cortex_m::map module and is a drop-in replacement for it.

Supported Devices

Device name / Cargo featureCore nameReference manual
stm32f100ARM® Cortex®-M3 r1p1RM0041
stm32f101ARM® Cortex®-M3 r1p1RM0008
stm32f102ARM® Cortex®-M3 r1p1RM0008
stm32f103ARM® Cortex®-M3 r1p1RM0008
stm32f107ARM® Cortex®-M3 r1p1RM0008
stm32l4x1ARM® Cortex®-M4F r0p1RM0394
stm32l4x2ARM® Cortex®-M4F r0p1RM0394
stm32l4x3ARM® Cortex®-M4F r0p1RM0394
stm32l4x5ARM® Cortex®-M4F r0p1RM0351
stm32l4x6ARM® Cortex®-M4F r0p1RM0351
stm32l4r5ARM® Cortex®-M4F r0p1RM0432
stm32l4s5ARM® Cortex®-M4F r0p1RM0432
stm32l4r7ARM® Cortex®-M4F r0p1RM0432
stm32l4s7ARM® Cortex®-M4F r0p1RM0432
stm32l4r9ARM® Cortex®-M4F r0p1RM0432
stm32l4s9ARM® Cortex®-M4F r0p1RM0432

NOTE Exactly one cargo feature should be selected based on the device model.


The API documentation intentionally skips auto-generated reg and thr bindings. Otherwise it would use several gigabytes of space and would be very slow to render in a browser. One should refer to the Reference Manual instead. And to get an idea of what the API looks like on the Drone side, look at the drone_cortex_m::map module documentation.


Place the following to the Cargo.toml:

drone-stm32-map = { version = "0.10.1", features = [...] }



STM32 peripheral mappings.


STM32 register mappings.


STM32 interrupt mappings.



Defines an index of STM32L4S9 register tokens.