wokwi-features VS embassy

No, no - I have a half a dozen RPi's of varying revisions. Since they run Linux and the SDcards are less than robust, anytime you accidentially trip the power (which to me happens several times during hardware debugging sessions) you risk scrambling the rootfs and thus need to reflash a new SDcard. Some SDcards get damaged.

I recommend using Arduino and/or Wokwi (https://wokwi.com/) to get started.

More Wokwi Integration: Wokwi is an amazing embedded simulator and is great for getting started quickly. For a learner, there's no need for toolchain setup or even the purchase of hardware. There are many features as well that make it quite a flexible tool supporting a lot of features right from the browser. Users can also vote for more features. Still maybe at some point, one might want to tinker with physical hardware. However, at that point, they would have gained some confidence first. Currently, only ESP boards are supported with Rust on Wokwi. I hope for the variety to expand soon.

In addition to the other great suggestions here I wanted to point out that you can practice and learn a lot for free using an online simulator such as wokwi.com and tinkercad.com (among others)! And you don't have to buy an Arduino or any parts to get started!

And you can prototype all of this first to get it working for free using an online simulator at sites like wokwi.com or tinkercad.com!

If you don't have the budget for real hardware consider the simulator at https://wokwi.com/ It works with Rust (at least for ESP32, haven't tried other architectures). Bonus: you can't blow up the electronics by a wiring mistake.

I spent a bit of time today with a few FastLED programs and uploaded them to wokwi.com on a simulated Arduino Nano and a WS2812 strip of 64 LED's (not in a 2D matrix). The chatgpt requests I made were:

https://tinyurl.com/yr34sym6

https://wokwi.com/ is great for simple, digital only stuff.

https://fritzing.org/ will kind of lay out the PCB for you, but it's kind of a pain in the ass.

Wokwi and Fritzing are more "Breadboard Simulators" than real circuit simulators, but they do have their place.

Another cool thing you may want to try is making a simulator https://wokwi.com/

thanks. looked that up. for the curious: https://embassy.dev/

Running the Embassy RP2040 USB CDC ACM serial example takes about 5 seconds on a Pico.

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

Async solves different problems, you can, for instance, have just a single-threaded CPU and still have a nice API if you have async-await. It might not be so cool at a higher level as Go's approach of channels and threads, but it's cool in embedded, read this:

https://github.com/embassy-rs/embassy?tab=readme-ov-file#rus...

"Rust's async/await allows for unprecedently easy and efficient multitasking in embedded systems. Tasks get transformed at compile time into state machines that get run cooperatively. It requires no dynamic memory allocation, and runs on a single stack, so no per-task stack size tuning is required. It obsoletes the need for a traditional RTOS with kernel context switching, and is faster and smaller than one!"

I'm just toying with Raspberry Pi Pico and it's pretty nice.

Go and Rust have different use cases, the async-await is nice at a low level.

I have not yet dipped by toes in the Rust waters, but reading about the embassy project is actually what piqued my curiosity about using C++ coroutines in embedded. Are you familiar with the project or have you found it lacking?

I think I get the basics (shoutout to the Rust Embedded Working Group!), and I've started looking for the stack I'd be using. I think Embassy is really amazing, as well as the work of the ESP team -- hats off.

> }

And this is how to do it using embassy, which is an async framework for embedded in rust:

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

> not good for embedded

embassy begs to differ

https://embassy.dev/

async/await is really just a syntax for building state machines in a way that resembles regular code. It's compiled down to the same code that you would write by hand anyway (early on it had some bloat in state size but I think it's all fixed now).

And embedded has a lot of state machines!

You can run multiple executors at different interrupt priority levels (with multiple tasks per executor), which allows tasks on the higher priority executor to interrupt other tasks. Here's an example https://github.com/embassy-rs/embassy/blob/main/examples/nrf...