The HAL template still forces a specific Rust compiler version in github.com/Rahix/avr-hal-template/blob/main/rust-toolchain.toml (version nightly-2021-01-07). My understanding is that newer LLVM generates an invalid instruction and there was a lot of back and forth about this in github.com/rust-lang/compiler-builtins/issues/400. My view of this is that AVR works, however as time passes the Rust build starts being older and older and unless the LLVM bug gets fixed, not being able to use (even if just play around) with newer compiler versions is really not ideal. I used arduino in this example because this seems to be a more commonly available hardware, however for newer projects I believe stm32 are generally net better for rust (faster, cheaper, more ram/gpios/functions). Also looking forward to more espressif risc-v as those just work out of the box and I like being able to control my projects over wifi. The only difficulty may be the 3.3 vs 5V (if trying to replicate 5V projects, they may not work out of the box) The great part is that rust_embedded abstracts things enough that knowing/seeing how to make one microcontroller makes it very easy to to do the same thing on another. Switching from AVR to something else should not be too hard.
12:19 this is the opposite of what you explained in the preamble. There you said that turning right is when they are different, and left is when they are same.
Off by one errors it seems :) I would say for this kind of hardware, try it out and adapt things until it looks right. I imagine this is how I got to the mismatch between explanation and actual code. Thanks for noticing! This shows that at least some people are paying close attention to what I am saying ... more pressure on me for any future videos (too late for this one - youtube does not allow you to edit things) :)
I use sublime for other projects and it starts up faster for me. Other than that, I find all of vscode, sublime and atom to be quite usable. I did not see a strong reason to prefer one vs the other so I picked one and stayed with it.
One simple word: AMAZING! You are embedded master! Please continue with rust embedded video, are really enteresting.
Thank you for the encouragement! Will try to keep at it!
I like how you walk the learner through discovering missing dependencies. This is a great learning session.
How is Rust on AVR chips? The last time I looked it was lacking a lot and required a rust fork.
Thanks for the video.
The HAL template still forces a specific Rust compiler version in github.com/Rahix/avr-hal-template/blob/main/rust-toolchain.toml (version nightly-2021-01-07). My understanding is that newer LLVM generates an invalid instruction and there was a lot of back and forth about this in github.com/rust-lang/compiler-builtins/issues/400.
My view of this is that AVR works, however as time passes the Rust build starts being older and older and unless the LLVM bug gets fixed, not being able to use (even if just play around) with newer compiler versions is really not ideal.
I used arduino in this example because this seems to be a more commonly available hardware, however for newer projects I believe stm32 are generally net better for rust (faster, cheaper, more ram/gpios/functions). Also looking forward to more espressif risc-v as those just work out of the box and I like being able to control my projects over wifi. The only difficulty may be the 3.3 vs 5V (if trying to replicate 5V projects, they may not work out of the box)
The great part is that rust_embedded abstracts things enough that knowing/seeing how to make one microcontroller makes it very easy to to do the same thing on another. Switching from AVR to something else should not be too hard.
@@embedded-rust Thanks for the reply! I have some STM32's I should dig them out and get busy.
What is Linux you use?
I use manjaro.org/ currently.
12:19 this is the opposite of what you explained in the preamble. There you said that turning right is when they are different, and left is when they are same.
Off by one errors it seems :)
I would say for this kind of hardware, try it out and adapt things until it looks right. I imagine this is how I got to the mismatch between explanation and actual code.
Thanks for noticing! This shows that at least some people are paying close attention to what I am saying ... more pressure on me for any future videos (too late for this one - youtube does not allow you to edit things) :)
Why don't u use vscode?
I use sublime for other projects and it starts up faster for me.
Other than that, I find all of vscode, sublime and atom to be quite usable. I did not see a strong reason to prefer one vs the other so I picked one and stayed with it.
@@embedded-rust have you try neovide