stlink VS embassy

I see stlink clones on ebay for $7. The stlink software runs on linux : https://github.com/stlink-org/stlink. Or use pyocd.

This one?

I did do a little bit of digging since this post. I think my distro has this set of tools:https://github.com/stlink-org/stlink

I flashed mine using the flasher included into a Stm32f4 discovery board I had laying around. Used this toolset https://github.com/stlink-org/stlink to flash the firmware. Not sure if you can use UART to flash, if that's so, you might be able to use a raspberry pi or Arduino as an interface which is far way more accessible than the stlink flasher.

Usually the better tools (eg. Segger's J-link, st-link with st-util, OpenOCD) can emulate a GDB-server to which you can connect from a gdb or from the debug session at your IDE.

In order to get into stm32 development I bought a cheap stm32 blue pill clone (STM32F103C8T6) and a ST-LINK v2. I tried to get the info by using the st-info --probe command in the open source version of STlnk tools. I pluged in the stlinkv2 connecting the headers correctly to the dev board and the boot1 and boot0 was in 0 position, no additional connection was given.

Have a look here: https://github.com/stlink-org/stlink/issues/651 Maybe you have the same problem.

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