RTIC is really simple and doesn't use it's own HALs. Also it's macro system makes it hard to modularize your code since all tasks need to be in one module. I've played around with it a bit and it seems like it could be great in the future, but currently not really.
Embassy has it's own HALs which makes it better at async and has also nicer ergonomic IMO
> Embassy has it's own HALs which makes it better at async and has also nicer ergonomic IMO
Worth noting, you don't HAVE to use the embassy HALs with the embassy executor. However, AFAIK, the only mainstream non-embassy HALs that supports async is the ESP32 HALs.
There's no technical lock in, it's just that everyone I've seen implementing async support (outside ESP32) tends to do it within the Embassy project today. That may change over time.
liamkinne|1 year ago
I’m using RTIC for the firmware on my STM32H7 based product (https://umi.engineering) and it has been a joy.
jamesmunns|1 year ago
Worth noting, you don't HAVE to use the embassy HALs with the embassy executor. However, AFAIK, the only mainstream non-embassy HALs that supports async is the ESP32 HALs.
There's no technical lock in, it's just that everyone I've seen implementing async support (outside ESP32) tends to do it within the Embassy project today. That may change over time.
Katzenmann|1 year ago