Regarding the Rust programming language and moreover its ecosystem and the overall maturity there is this trend of "measuring" the latter with series of question in the vein of: Are-we-Something-Yet? A few key examples would be: Are we (I)DE yet? - the classic (and probably the first one that started it all) one. Are we Web yet? Are we Game yet? Are we Embedded, yet? And so on, and so forth ... There is even a subReddit (along with the GitHub page it represents) that obviously aims to gather them all in one place as a curated list of links. The Official State The last one in the list above is not linked anywhere. There might not be a dedicated " yet " page for it but what actually exists might be even better. On one hand there is this dedicated domain which serves as the front of the actual people at Rust who work on the parts of the language that should provide the means for embedded programming. On the other hand there is the respective Embedded Book a
For some time I'm following the Circuit Dojo channel . I'm sure the guy (Jared Wolff) knows what he's talking about since he has a web store with embedded electronics products of his own making (including a tiny nRF9160 based circuit board). In recent times he seemingly specialized the channel to represent the theme of the Zephyr RTOS by organizing live streams under the umbrella ZEPHYR: 101 . These might be very helpful for those new to Zephyr as whole because he provides essential (sometimes basic, sometimes more advanced) information on a specific subject. For instance, the latest video is dedicated to the particular way one can configure their Zephyr based application to work with their custom tinkered board. In the general case a vanilla Zephyr should work but as a specific example it is said that the nRF916x type of boards would require the nRF Connect SDK . With that example he says that any of the dependencies of the custom board must be satisfied prior to wor