Rahix

@flyingyizi, thanks for providing the code snippets. Just FYI, instead of the raw `cli` and `sei` instructions, you should probably use the [`avr_device::interrupt::free`](https://docs.rs/avr-device/0.4.0/avr_device/interrupt/fn.free.html) helper. It makes sure interrupts are only...

PR #1901 was only for register reports so it makes sense the balance report is still broken. I.e. this issue is separate from what I was working on. But if...

[`opt-depth_flat.test`](https://github.com/ledger/ledger/blob/master/test/baseline/opt-depth_flat.test) seems to test exactly the weird behavior described here. I can't find history why it was added? But the consensus here is that it should be changed (and thus...

Just FYI: I had a stab at fixing this but it wasn't as easy as I had hoped - the problem is that sometimes new accounts (at the cut-off depth)...

@uberblah, I think your problem relates more to #4717.

ACK, we've already identified at least one spec violation (https://github.com/Rahix/atdf2svd/issues/25). Just as a bit of background: With https://github.com/Rahix/avr-device the intent was obviously just to get the Rust generation working so...

Hi, I'll close this PR for now, but if you feel that this is something we should talk about again, let me know.

I'll close this PR for now, I think it makes more sense to take a fresh look at it once support in avr-hal is implemented.

Some good news: https://github.com/avrdudes/avr-libc/issues/890 was fixed upstream. Once the fix trickles down into distro packages, we can maybe move forward on the Nano Every support.

@hiszd, not really. `IoPin` moves the pin to change its state more permanently while the methods in this PR only change the pin state for the duration of a closure.