#avr #macros #device

macro avr-device-macros

Attribute macros for re-export in avr-device

4 releases

0.2.3 Oct 19, 2020
0.2.2 Aug 20, 2020
0.2.0 Aug 7, 2020
0.1.0 Jul 26, 2020

#400 in Embedded development

Download history 58/week @ 2020-08-06 41/week @ 2020-08-13 152/week @ 2020-08-20 75/week @ 2020-08-27 62/week @ 2020-09-03 33/week @ 2020-09-10 69/week @ 2020-09-17 41/week @ 2020-09-24 62/week @ 2020-10-01 64/week @ 2020-10-08 76/week @ 2020-10-15 106/week @ 2020-10-22 65/week @ 2020-10-29 59/week @ 2020-11-05 58/week @ 2020-11-12 53/week @ 2020-11-19

256 downloads per month
Used in avr-device


602 lines

avr-device crates.io page docs.rs Build Status

Auto-generated wrappers around registers for AVR microcontrollers.


Add the following to Cargo.toml:

version = "0.1.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
  • atmega8
  • atmega328p
  • atmega32u4
  • atmega64
  • attiny85

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 PyYAML installed:

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

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

If patches need to be applied, create a <chipname>.yaml in patch/. The patching format is compatible to the YAML patching format of stm32, except that you do not need to provide the path to the svd file (_svd: ...) since it is generated in the build process. Additionally, the following patching was added:

            # If a field already contains a write-constraint, you can
            # change it using the _write_constraint modifier.  The
            # following values are allowed:

            # "enum": Only allow enumerated values (<useEnumeratedValues>)
            _write_constraint: "enum"

            # Remove any existing writeConstraint tag
            _write_constraint: "none"

            # Constrain to a range of values (<range>)
            _write_constraint: [min, max]
            # Replaces the enumeratedValues definition for this field.
            # If it does not exist yet, it is created.
                NAME: [VALUE, DESCRIPTION]


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


~21K SLoC