cyt2b9
| Crates.io | cyt2b9 |
| lib.rs | cyt2b9 |
| version | 0.0.1 |
| source | src |
| created_at | 2023-03-20 23:27:46.095024 |
| updated_at | 2023-03-20 23:27:46.095024 |
| description | Peripheral access crate for cyt2b9 T2G family |
| homepage | |
| repository | https://github.com/Infineon/traveo-t2g-pal/tree/develop/pal_crates/cyt2b9 |
| max_upload_size | |
| id | 815696 |
| size | 4,674 |
(AthiraRamakrishna)
documentation
https://docs.rs/cyt2b9
README
Supported Device Family
cyt2b9
Supported Crates
| crate | svd version |
|---|---|
| cyt2b9_c | 1.0.0 |
Using device meta-package crate in your project
In your own project's Cargo.toml:
[dependencies.cyt2b9]
version = "0.0.1"
features = ["<one of the supported revisions>", "rt", "critical-section"]
The rt feature is optional.
See svd2rust for details.
The critical-section feature is optional.
See critical-section for details.
Usage of device meta-package in your code:
use cyt2b9 as pac;
let mut peripherals = pac::Peripherals::take().unwrap();
By default cyt2b9 refers to the latest revision of the supported crates, if your project requires a specific revision, you can pass it as a feature in your project's cargo.toml file. This way of using meta package you dont have to change your project code each time you change the revision.