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