#avr #arduino

nightly no-std avr-device

Register access crate for AVR microcontrollers

7 releases

0.3.0 Feb 7, 2021
0.2.3 Oct 19, 2020
0.2.2 Aug 20, 2020
0.1.1 Jul 31, 2020

#442 in Embedded development

Download history 170/week @ 2021-02-23 278/week @ 2021-03-02 204/week @ 2021-03-09 235/week @ 2021-03-16 117/week @ 2021-03-23 89/week @ 2021-03-30 222/week @ 2021-04-06 164/week @ 2021-04-13 313/week @ 2021-04-20 248/week @ 2021-04-27 85/week @ 2021-05-04 92/week @ 2021-05-11 96/week @ 2021-05-18 90/week @ 2021-05-25 108/week @ 2021-06-01 118/week @ 2021-06-08

785 downloads per month


462K SLoC

avr-device crates.io page docs.rs Continuous Integration

Auto-generated wrappers around registers for AVR microcontrollers.


Add the following to Cargo.toml:

version = "0.3.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:

  • atmega1280
  • atmega168
  • atmega2560
  • atmega8
  • atmega328p
  • atmega32u4
  • atmega4809
  • atmega48p
  • atmega64
  • atmega644
  • attiny84
  • attiny841
  • attiny85
  • attiny861
  • attiny88

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, svd2rust, form, rustfmt(for the nightly toolchain) and svdtools (>= 0.1.9) installed:

cargo install atdf2svd
cargo install svd2rust
cargo install form
rustup component add --toolchain nightly rustfmt
pip3 install --user svdtools

Next, clone this repo and build the device definitions:

git clone https://github.com/Rahix/avr-device
cd avr-device
# You can build for just one specific chip using
# make atmega32u4
# I suggest building documentation as well
cargo +nightly doc --features <chip> --open


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>.


avr-device is licensed under either of

at your option.

The vendored atdf files are licensed under the Apache License, Version 2.0 (LICENSE-VENDOR).