[avr] create initial example #3696
Conversation
tones111
force-pushed
the
avr_example
branch
2 times, most recently
from
d8ab606 to
4f4fb7e
Compare
tones111
force-pushed
the
avr_example
branch
from
4f4fb7e to
0578870
Compare
| @@ -0,0 +1,8 @@ | |||
| [build] | |||
| target = "avr-unknown-gnu-atmega328" | |||
There was a problem hiding this comment.
Should the example directory name more closely match the rustc target (avr -> atmega328)?
Currently nightly only supports this target, but avr-hal maintains some additional spec files. I'm unsure if these will all end up being their own rustc platforms, if they can drop the gnu dependency, or if they can be consolidated under a more generic name.
I'm assuming any AVR support here would only use rustc supported targets, otherwise this repo would likely need to duplicate the spec files.
There was a problem hiding this comment.
I've learned of some progress regarding rustc avr target support.
rust-lang/rust#131651
The proposal consolidates the avr processors into one avr-unknown-unknown or avr-unknown-none target.
There was a problem hiding this comment.
i put "avr-unknown-gnu-atmega328" just because it was there, i think most of the times, you'll be using target jsons from avr-hal
| #[embassy_executor::main] | ||
| async fn main(_spawner: Spawner) { | ||
| loop { | ||
| // TODO |
There was a problem hiding this comment.
Toggling a pin using avr-device is easy enough, but the big hang up here is lack of an AVR time driver.
Is there interest in implementing/supporting an embassy-specific AVR hal, or should the examples make use of avr-hal? Does embassy attempt to have a consistent feel across its HALs?
One challenge is that none of the AVR HAL crates have been published, so git dependencies are needed. I'm also unsure how well it's design aligns with the HALs here.
|
i wrote time driver https://github.com/djdisodo/avr_embassy_time/tree/master it works well enough that i could drive stepper motors with it but there's also lot of features with questionable benefits for example wake scheduled in goofy linked list to keep it sorted but since i later found that embassy never drops a timer, if you have a code that may cancel timer, the queue will be always full and it has to check all the timers when inserting new (also it uses a bit more ram) (i think embassy should allow the driver to drop timer that has been dropped by user) (also MARGIN_TICKS is random number that i found it working) |
This commit adds a minimal example demonstrating how to create an embassy executor. This gets the infrastructure in place for future work to add missing pieces like a timer driver.