wg

To specifically answer your question, here: * <http://www.areweembeddedyet.com/> It currently redirects to: * <https://rust-embedded.org> Which doesn't really contain anything other than a link to <https://github.com/rust-embedded>. (via <https://github.com/rust-embedded/wg/issues/15>)

TIL MSRV minimum supported rust version https://github.com/rust-embedded/wg/blob/master/ops/msrv.md

32 bit microcontrollers are well-supported, and often cheaper, more power efficient and with more features than old 8-bit uCs. https://github.com/rust-embedded/wg

> I was getting quite worried that Mozilla would go to Discord, like Rust and other projects have done. Just so you know, the Rust Embedded guys went with Matrix back in June and several people do use the IRC bridge. https://github.com/rust-embedded/wg/issues/357

If there's anyone from the embedded community who's taking a stab at fixing rust for that use case, it's James. He's one of the three members of the Rust Embedded Working Group (https://github.com/rust-embedded/wg).

Not OP, but further info can be found in the GitHub repo of the build tool: https://github.com/rust-embedded/cross https://github.com/rust-embedded/wg#the-tools-team

No mention of RISC-V support? It sounds like RV64GC finally landed (Hurra and thanks!): "riscv64imac-unknown-none-elf and riscv64gc-unknown-none-elf targets are now on stable rustc 1.34.0 :slightly_smiling_face: https://github.com/rust-lang/rust/blob/master/RELEASES.md#ve... https://github.com/rust-embedded/wg/issues/218#issuecomment-... EDIT: Mea culpa, I somehow missed that it _is_ in the release notes, but still, it's worth pointing out. I hope it'll find its way into Fedora/RISC-V.

There are lots of issues with using Rust for embedded development, most of them long standing, which are often felt to be neglected, and some suspicion that progress is slow because it is not the highest priority for decision-making people. https://github.com/rust-embedded/wg/issues/64 details some of these technical issues. Personally issues with Cargo are the most pressing, and math/compiler_builtins is very annoying.

I don't think so, but so far the only other such websites I've seen are http://www.arewewebyet.org/ and https://areweasyncyet.rs/ . Though looks like there used to be a areweembeddedyet.org[1], but now https://docs.rust-embedded.org/ seems to be the main jumping off point for rust embedded. [1]: https://github.com/rust-embedded/wg/issues/15

Hey, I saw that links to the Embedded Working Group[0], TockOS[1], and others have been posted already, and those are great places to start! My company, Ferrous Systems[2], is also focused on embedded systems development in Rust, and we are already helping companies both with embedded linux and bare-metal/RTOS projects in Rust. We're also running a conference in Berlin on April 26th-29th called OxidizeConf[3] if you are interested in learning more about what is already going on in the Embedded Rust world :) [0]: https://github.com/rust-embedded/wg [1]: https://www.tockos.org/ [2]: https://ferrous-systems.com [3]: https://oxidizeconf.com

Thank you for sharing, subscribed. As I read through the Rust Embedded Work Group manifesto, it is comforting to see the level of organizational skills, planning and vision of the team involved. Bravo. https://github.com/rust-embedded/wg

Hey! Feel free to check out what we have going on at https://github.com/rust-embedded/wg, and our docs with getting started guides at https://docs.rust-embedded.org!

Hey, Author of the first link above. The Teensy3 crate was some of my first embedded work, I was working with SimonSapin (author of the 4th link) at RustFest to get something working. That library wraps some of the Teensyduino code using bindgen, which gives you the ability to write application code using Rust. Overall, the Teensy 3.1/3.2 family wasn't great for developing Rust, as they don't have debugger (SWD, similar to JTAG) lines available, meaning you have to use the serial bootloader, and rely on a serial port for all debugging. I believe the newer version of the board expose SWD lines now, so it's not a problem. Let me know if you have any questions :) Definitely check out the embedded WG[1], and the new Rust homepage[2] [1]: https://github.com/rust-embedded/wg [2]: http://beta.rust-lang.org/what/embedded

For anyone that might be interested, there were some efforts some time back to get Rust running on the Teensy[1][2][3][4], and although there have been no recent updates, the code is available to use and should still be relevant although there have been changes[5][6][7] in the meantime. [1]: https://github.com/jamesmunns/teensy3-rs [2]: https://branan.github.io/teensy/ [3]: https://disconnected.systems/blog/bare-metal-rust-on-the-tee... [4]: https://github.com/SimonSapin/teensy-clock [5]: https://rust-embedded.github.io/book/ [6]: https://josh.robsonchase.com/embedded-bootstrapping/ [7]: https://github.com/rust-embedded/wg/issues/40

Hey, member of the embedded wg here. Originally, our first push was to get Cortex M bare metal microcontrollers as a "Tier 1" stable target for the 2018 edition of Rust. Over the last couple months, we've been expanding, and have subteams for a bunch of different topics, including chip support, drivers, documentation, tooling, etc. We're mostly focused on helping other people who are getting started with embedded rust, as well as give feedback to the compiler teams, etc. It would be interesting to hear more about your porting attempt, we also have a blog - https://rust-embedded.github.io/blog/ - if you'd like to share it as a blog post. As Steve mentioned, https://github.com/rust-embedded/wg is our main coordination repo, and has links to most of the stuff we're actively working on.