drone-tisl-map
| Crates.io | drone-tisl-map |
| lib.rs | drone-tisl-map |
| version | 0.13.0 |
| created_at | 2020-05-04 19:08:27.603643+00 |
| updated_at | 2020-12-05 16:25:25.524528+00 |
| description | Texas Instruments SimpleLink™ peripheral mappings for Drone, an Embedded Operating System. |
| homepage | https://www.drone-os.com/ |
| repository | https://github.com/drone-os/drone-tisl-map |
| max_upload_size | |
| id | 237510 |
| size | 29,142 |
Valentine Valyaeff (valff)
documentation
README
drone-tisl-map
Texas Instruments SimpleLink™ peripheral mappings for Drone, an Embedded Operating System.
This crate uses CMSIS-SVD files based on TI CCS target db 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_cortexm::map] module and is a
drop-in replacement for it.
Supported Devices
tisl_mcu |
Core name | Product specification | Available features |
|---|---|---|---|
cc2538 |
ARM® Cortex®-M3 r2p0 | SWRU319C | gpio ioc sysctrl tim uart |
tisl_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_cortexm::map] module documentation.
Usage
Add the crate to your Cargo.toml dependencies:
[dependencies]
drone-tisl-map = { version = "0.13.0", features = [...] }
Add or extend std feature as follows:
[features]
std = ["drone-tisl-map/std"]
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.