avr-device
| Crates.io | avr-device |
| lib.rs | avr-device |
| version | 0.6.0 |
| source | src |
| created_at | 2020-07-26 09:19:36.907261 |
| updated_at | 2024-09-20 01:20:20.987823 |
| description | Register access crate for AVR microcontrollers |
| homepage | |
| repository | https://github.com/Rahix/avr-device |
| max_upload_size | |
| id | 269692 |
| size | 31,937,981 |
Rahix (Rahix)
documentation
README
avr-device 
Auto-generated wrappers around registers for AVR microcontrollers.
Usage
Add the following to Cargo.toml:
[dependencies.avr-device]
version = "0.6.0"
features = ["atmega32u4"]
Via the feature you can select which chip you want the register specifications for. The following list is what is currently supported:
| ATmega | ATmega USB | ATmega 0,1 Series | AT90 | ATtiny |
|---|---|---|---|---|
atmega8 |
atmega8u2 |
atmega4808 |
at90usb1286 |
attiny13a |
atmega48p |
atmega32u4 |
atmega4809 |
attiny167 |
|
atmega64 |
avr64du32 |
attiny202 |
||
atmega644 |
avr64du28 |
attiny402 |
||
atmega88p |
attiny404 |
|||
atmega16 |
attiny44a |
|||
atmega168 |
attiny84 |
|||
atmega324pa |
attiny85 |
|||
atmega328p |
attiny88 |
|||
atmega328pb |
attiny816 |
|||
atmega32a |
attiny828 |
|||
atmega1280 |
attiny841 |
|||
atmega1284p |
attiny84a |
|||
atmega128a |
attiny861 |
|||
atmega128rfa1 |
attiny1614 |
|||
atmega2560 |
attiny2313 |
|||
atmega164pa |
attiny2313a |
Build Instructions
The version on crates.io is pre-built. The following is only necessary when trying to build this crate from source.
You need to have atdf2svd (= 0.4.0), svd2rust (= 0.28), form (>= 0.8), rustfmt(for the nightly toolchain) and svdtools (>= 0.1.9) installed:
cargo install atdf2svd --version 0.4.0
cargo install svd2rust --version 0.28.0
cargo install form
rustup component add --toolchain nightly rustfmt
pip3 install --user svdtools
# check svdtools
svd --version
# if a "command not found" error is printed instead of a version,
# either svdtools is installed incorrectly, or its installation path is missing from the PATH variable.
# Temporary solution to PATH variable issue is to manually add the path. Like so:
export PATH=$PATH:~/.local/bin
Next, clone this repo and build the device definitions:
git clone https://github.com/Rahix/avr-device
cd avr-device
make
# You can build for just one specific chip using
# make atmega32u4
# I suggest building documentation as well
cargo +nightly doc --features <chip> --open
Internals
avr-device is generated using atdf2svd and svd2rust. The vendor-provided atdf files can be found in vendor/. The intermediate svd files are patched by svdpatch.py (Adapted from svdpatch.py in stm32-rs) with device-dependent patches in patch/, mainly to improve undescriptive names and missing descriptions.
Adding a new Chip
To add a new chip, download the atdf from http://packs.download.atmel.com/ (or avr-mcu/packs/) and place it in vendor/. Be sure to name it like the Rust module that should be generated. Next, you need to integrate it into the base crate and build system. Follow what was done in commit 290613454fbd ("Add basic support for ATmega64"). Please adhere to the alphabetical sorting that is present so far.
Next, you must create a <chipname>.yaml in patch/ which has at least the following content:
_svd: ../svd/<chipname>.svd
If more patches need to be applied (most likely!), they should be added into this file as well. The patching format is documented in the svdtools README. Ideally, try to reuse the exisiting patches in patch/common/ or patch/timer/.
Finally, try building the crate for your MCU with make <chipname>.
License
avr-device is 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.
The vendored atdf files are licensed under the Apache License, Version 2.0 (LICENSE-VENDOR).