Hi!

Has anyone experiences with using RTIC as executor in combination with a bunch of embassy crates?

I have a stm32wb55 and I want to use the [embassy-stm32](https://crates.io/crates/embassy-stm32) as HAL, because the support for the WB55 seems to be the best. Also I want to use the WPAN functionality and embassy-net for my modem.
As I understand, this should work because the HAL offers interoperability with any executor. Embassy also does not support low-power for stm32wb55 so far. At least as far as I understand.

I really like the explicitness of the RTIC `idle` task. So using the idle task seems to be an easy way to enter a power saving mode. Also, the compile time guarantees for deadlock free scheduling seem almost too good to be true.
So using RTIC with the “batteries” of Embassy seems like a viable approach?

To clarify, I am willing to contribute, and I am not expecting that everything is just there. But at the moment, I am stilll a newby in the great new rust embedded world and would appreciate some pointers/hints.
I have the opportunity to pitch rust for embedded in my company and really want this to work out, because IMO this is the future and way better than our current C/FreeRTOS custom setup. Current saving is crucial for this.

Looking and [awesome-embedded-rust](https://github.com/rust-embedded/awesome-embedded-rust) I found [booster](https://github.com/quartiq/booster) which used smoltcp, so embassy-net should also work.
Do you now of other advanced firmware projects that use RTIC ideally in combination with embassy which I could look at?

Thanks :-)