avrd
avrd copied to clipboard
avr-rust
AVR device definitions
It seems that documentation failed to build for 0.3.0: https://docs.rs/crate/avrd/0.3.0 If you look at the build log, there's a panic with message "Read-only filesystem". I think it's `docs.rs` problem. But...
The check for the target arch in the build script doesn't work. https://github.com/avr-rust/avrd/blob/6072399dfe037d2807abb4058d4da6f045cc3f6c/build.rs#L13 Checking the environment variable `CARGO_CFG_TARGET_ARCH` would probably be the correct way (like `avr_mcu::is_compiling_for_avr()`). I would have submitted...
I imagine that there are AVR devices which have IO ports where only half of the bits are actually connected to pins. We might want to look into something like...
At the moment, all registers have their associated bitfields in the crate docs. We should insert a link so it is clickable and takes the user to the bitfield constant.
It may make sense for us to convert the build script into a normal script and committing all generated cores to VCS. This makes it quicker, and also means that...
Compilation time is quite long because we generate modules for each and every mcu, even ones for the automotive-specific microcontrollers. Look into disabling them by default, so that you must...
It looks like the pack files are detailed enough that they specify which bits are used for all `instance`s of `name="PORT"` modules. See the ATXMEGA64a4, which only uses half of...
This repository knows about every single AVR device in existence (assuming that Atmel provides pack files for all chips). Because of this, we can use it to generate target specification...
As far as I can tell, these represent enums The enums in this file seem to correspond to `value-group`s in pack files https://www.mikrocontroller.net/attachment/332082/iotn3217.h