rust-esp32-std-demo VS embassy

This is my link: https://github.com/ivmarkov/rust-esp32-std-demo

A complete STD demo on ESP32C3

I'm trying lots of Rust demos (including rust-esp32-std-demo, esp32-spooky-maze-game) for ESP32 on my M5GO kit with ili9342c controller and all of them struggle to give fullscreen (320x240) frame-rate > 5.

I used this demo as a guide, it uses esp-idf for rust, and allows you to use std

rust-esp32-std-demo works quite well with WiFi, HTTPS and MQTTS. The only thing I could not make work (but I did not put much effort into it) was using async primitives. That part seems to be experimental, indeed.

FWIW I've very recently gotten https://github.com/ivmarkov/rust-esp32-std-demo (which is a pretty comprehensive demo) running on a TinyPICO (w/ESP32) and am looking forward to building out my own projects next.

I'm using this template project to get started with the esp32, though I've started fresh in a new main function. Every time I build the project -even if I only add a blank line to main - it seems to re-compile bindgen and embuild, and regenerate the bindings for a variety of packages that have C components. I haven't made any changes to these though and the process takes a full 90 seconds. In addition nothing in the bindings that are getting generated shows up in intellisense in vscode. Any help appreciated.

This worked fairly well for me. I assume that's where the book takes you, bit I've missed if you said if you're trying to use std or no_std. https://github.com/ivmarkov/rust-esp32-std-demo

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...