cyt3bb
| Crates.io | cyt3bb |
| lib.rs | cyt3bb |
| version | 0.0.1 |
| created_at | 2023-10-25 23:03:08.100624+00 |
| updated_at | 2023-10-25 23:03:08.100624+00 |
| description | Peripheral access crate for cyt3bb T2G family |
| homepage | |
| repository | https://github.com/Infineon/traveo-t2g-pal/tree/develop/pal_crates/cyt3bb |
| max_upload_size | |
| id | 1013737 |
| size | 5,043 |
(AthiraRamakrishna)
documentation
https://docs.rs/cyt3bb
README
Supported Device Family
cyt3bb
Supported Crates
| crate | svd version |
|---|---|
| cyt3bb_a | 1.0.0 |
| cyt3bb_b | 1.0.0 |
Using device meta-package crate in your project
In your own project's Cargo.toml:
[dependencies.cyt3bb]
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 cyt3bb as pac;
let mut peripherals = pac::Peripherals::take().unwrap();
By default cyt3bb 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.