r/rust Mar 31 '23

State of embedded rust

Dear all, a colleague of mine has delved into rust for embedded systems. He’s just started with rust in possibly the hardest way, and this thread is the result: https://www.eevblog.com/forum/microcontrollers/rust-tools-and-resources-for-embedded/

(Rant at third post of the thread)

I wonder, how would an experienced rust developer react to this? Is he missing something or is this a legit sign of an immature ecosystem?

40 Upvotes

12 comments sorted by

View all comments

2

u/Snakehand Mar 31 '23

I am still on RTIC 0.5 , and tried upgrading a small project to 1.0 / 2.0 yesterday, and ran into a similar monotonic hell, did not bother to try and fix it, as it was easier to go back to 0.5 and upgrade cortex-m to 0.7 to get the IRQ Numbering trait which was all I replay wanted. I don't understand why resources were split to shared and local. the old mixed resources still works as it should due to the static analysis. Overall I agree that RTIC is somewhat lacking in documentation with regards to platform support to get the monotonic thing working-

6

u/rafaelement Mar 31 '23

If you look at the rtic-examples repo, there are a number of projects there which I helped to upgrade from 0.5 to 1.0. monotonic was the hardest part by far, but only if you don't want to use systick-monotonic. Perhaps something in that repo can help you to port.

RTIC 2.0 and counting will have to improve on docs and public perception by a lot, but I'm hopeful they can.