probe-rs VS embassy

Want debugging capabilities with anything with an am st link/jtag/other compatible probe? https://probe.rs/

/uj The SVG usage looks to be in a visualisation helper. Maybe ought to be a separate module, but I've seen worse.

There is a command to list supported chips for *flashing* in all our CLI tools. Furthermore https://github.com/probe-rs/probe-rs/tree/master/probe-rs/targets contains all targets for which we support *flashing*.

Under the hood, cargo-embed, knurling's probe-run, and Humility are all built atop probe-rs (https://probe.rs/) to provide debugging - I think in this case it's actually a great example of cooperation between projects! Probe-rs has received PRs from both Knurling and Oxide devs; it provides the common interface to use various types of debug hardware and talk to various types of microcontroller cores, essentially replacing OpenOCD.

Ryzen 3700X, 3200Mhz DDR4 tower builds http://probe.rs in 1m47s with fans fully spinning. M1 Pro: zero noise, 1m21s. Ryzen 3950X is on par with the M1 Pro. Actual speed difference will very much depend on your actual workload. Compiling for aarch64 apparently is more efficient than for amd64. Which is why compiling for you locally gives much more speed benefit than some generic benchmarks would indicate :) Also, you cannot forget that I can easily work for 10hrs on my MBP M1 Pro with rust-analyzer and frequent compiles running. You can forget that with any other suggested "on par" notebook. They will drain your battery instantly. Also, with the same thermal mass, other laptop builds will go into throttling much faster, which will lead to slower effective speed. XPS laptops and old macbooks know this issue very well :)

Anyone who fancies doing some coding for fun should have a go at an embedded project using rust's tools. Not just embassy, but the PACs, the HALs, probe-rs (probe-rs is bonkers good), and the community on matrix. My bet is on rust embedded seeing huge growth in the next few years.

probe-rs (embedded debugging toolkit for ARM and RISC-V which is supposed to be used in place of the above if you code with it as it aims to fully replace the GDB portion of the stack for Rust embedded development)

cargo install --git https://github.com/probe-rs/probe-rs probe-rs-debugger

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