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