Rahix
Sorry for having to ask: With commit b78409b326fcdfb2f26d6a721737c6842615d630, the original issue here should be fixed, right? Or is there anything else remaining?
I guess it is not a problem to upgrade to `^0.7.0`. It will require a breaking version bump of `shared-bus` as well, but I think that's fine. I'm not sure...
> I would say adding this `-c usbtiny` syntax as a small patch is a good solution until a proper refactor can be made for the entire board.rs re-write. I'm...
I see. I'm not a fan of adding such specific options here because supporting them in the long run will be painful... I think what I'd prefer would be adding...
> I also was able to get it working with the toolchain provided by Arduino. Yes, they do ship the support because they need it for the Nano Every. >...
I think with things like #349 hitting, it's time to close this issue.
What LCD are you trying to drive, @victor-wei126? The idea in the embedded Rust community is to have driver crates for each LCD controller and those can be connected to...
(And in line with the original issue topic here, if someone wants to contribute an LCD example, please do!)
@fvilante, you might want to use the API from [`avr-device`](https://github.com/Rahix/avr-device) instead of those raw register accesses.
@DoubleHyphen, the register accesses should really use the `avr-device` API as I wrote in the [comment above](https://github.com/Rahix/avr-hal/issues/265#issuecomment-1245729665). That API prevents such odd mistakes by design.