Jake Goulding

> all PORT/DDR registers are zeroed. And that's true on soft restarts too?

That specific code does nothing, it’s just examples of how you would get a `u8` value corresponding to a specific pin in a specific register. In context: https://github.com/shepmaster/rust-arduino-blink-led-no-core-with-cargo/blob/b2d612142b8112a4c70f97b4f74f62be3b9a28c3/src/main.rs#L46-L49 https://github.com/shepmaster/rust-arduino-blink-led-no-core-with-cargo/blob/b2d612142b8112a4c70f97b4f74f62be3b9a28c3/src/main.rs#L475-L481

> we require users to write their own interrupt vector table (IVT) in assembly I don't think this is strictly true if you are linking with the avr-gcc runtime glue....

A related aspect that we will need to deal with is model-specific aspects. For example, this linker script bakes in the amount of memory available. It also has a fixed...

> store the interrupt flag in the status register One thing that I think would be very interesting to explore would be to see if we could track the state...

> Do you have any nice idea on how to have different boards in the same code base? Yeah, that's a big question for this library! My *hope* was that...

Yeah that should definitely be an unsafe trait. Maybe also sealed as no one should be able to implement it out of the library.

> wouldn't it make sense to try to align this to the route @japaric is taking with embedded-hal etc, or is his arm efforts just too far away? Thinking otherwise...

Thanks. Would you mind running the script for the atmega328p as well? That way I can compare it to the checked-in version. Any idea about 16-bit register pairs or aliases?...

@dylanmckay any idea if [avrd](https://github.com/avr-rust/avrd) can be of use here? Specifically, I don't see any of the bits available there.