[−][src]Crate drone_nrf_map
Nordic Semi nRFx peripheral mappings for Drone, an Embedded Operating System.
This crate uses CMSIS-SVD files provided by Nordic Semiconductor to automatically generate Drone register and interrupt bindings. However only the corresponding Product Specification is the single source of truth. A difference between this crate bindings and the Product Specification 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
nrf_mcu | Core name | Product specification |
|---|---|---|
nrf52810 | ARM® Cortex®-M4F r0p1 | PS v1.3 |
nrf52811 | ARM® Cortex®-M4F r0p1 | PS v1.0 |
nrf52832 | ARM® Cortex®-M4F r0p1 | PS v1.4 |
nrf52840 | ARM® Cortex®-M4F r0p1 | PS v1.1 |
nrf_mcu config flag should be set at the application level according to
this table.
Documentation
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 Product
Specification 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.
Usage
Place the following to the Cargo.toml:
[dependencies]
drone-nrf-map = { version = "0.11.0", features = [...] }
Modules
| reg | nRF register mappings. |
| thr | nRF interrupt mappings. |
Macros
| nrf_reg_tokens | Defines an index of nrf52 register tokens. |