Rahix

Looks like rustfmt makes files larger. Though if anyone wants to look at the source, a non-formatted file makes it completely impossible while a formatted but large single file (from...

> Another consideration in support of running the generated code through rustfmt are the documentation src links. I think it's more likely users would click through the source links to...

This is an existing project archieving no libc dependence: https://github.com/shepmaster/rust-arduino-blink-led-no-core-with-cargo

No, unfortunately not. To be quite honest, I'm waiting for `nightly` rustc to be fixed for AVR before I intend to spend time on this, because it is getting increasingly...

Yes, `avr-device` is the PAC crate with the raw register definitions. [`avr-hal`](https://github.com/Rahix/avr-hal) builds on top and has safe abstractions over the peripherals. > As it is a MCU of the...

Sounds good, thanks a lot! :)

It looks like this chip does not follow the standard register layout for IO ports. We'll have to fix `atdf2svd` to detect this case and behave differently for it, I...

I see ... So, it's failing in the [`signals_to_port_fields` patch](https://github.com/Rahix/atdf2svd/blob/master/src/atdf/patch.rs#L7-L53) which is applied after parsing the ATDF to create fields for individual pins in the port registers (`PORTn`, `DDRn`, `PINn`)....

Okay, I'd say the best way to deal with this is a whitelist approach. So the patch should only touch registers named - For 'old' scheme (`n` is port letter)...

> For the 'new' scheme: These registers are listened only once in the atdf, but each port has them. So basically it is needed that each port gets a "copy"...