Tracking Issue: Call for blog posts, EoY 2023 about wg HOT 12 OPEN

Thanks, @jamesmunns for the great idea. We'd like to share a blogpost here https://www.systemscape.de/en/blog/2023/wrap-up/ about the great experience we've had so far and a big "thank you" to some of the most helpful folks in the community. At Systemscape we're very convinced of a bright future for embedded rust and are confident that we're doing the right thing, starting our life after university in this field.

from wg.

Not a blog post per se, but it still covers some of the aspects in "The Good", in particular useful crates of the ecosystem: https://google.github.io/wasefire/acknowledgments.html

from wg.

Great idea @jamesmunns. Here's my two-cent:
https://apollolabsblog.hashnode.dev/embedded-rust-education-2023-reflections-2024-visions

from wg.

I would be very interested in a talk about the current state of cross-compiling and flashing of various hardware. I'm used to both: the raspberry pi method of putting binaries on an SD card and the AVR method of FTDI uploading with a standalone tool (avrdude). It would be magnificent if we could unify this workflow if it hasn't already been.

from wg.

I wish I had something to contribute but I'm in a bit of a slump still.

Right now my hardware Rust project is hung up on three things:

1. cargo flash
2. My learning async
3. A little bit of time and money to wire everything up nicely

Not very helpful I know, but it's what I've got.

from wg.

Great idea @jamesmunns. Here's my two-cent: https://apollolabsblog.hashnode.dev/embedded-rust-education-2023-reflections-2024-visions

Dude, you're awesome - your blog posts have been incredibly helpful in inducting me into a side of rust I believe I never would've been able to enter otherwise.
I seriously wish documentation wasn't as scarce as it is - I'm used to the rust where I can easily determine what functions do but now like 40% of the time, functions/structs simply don't have a description

from wg.

Great idea @jamesmunns. Here's my two-cent: https://apollolabsblog.hashnode.dev/embedded-rust-education-2023-reflections-2024-visions

Dude, you're awesome - your blog posts have been incredibly helpful in inducting me into a side of rust I believe I never would've been able to enter otherwise. I seriously wish documentation wasn't as scarce as it is - I'm used to the rust where I can easily determine what functions do but now like 40% of the time, functions/structs simply don't have a description

Thank you for your kind words! I'm thrilled to hear that my blog posts have been helpful in your journey into embedded Rust. It's always a pleasure to share knowledge and make the learning process more accessible. If there's anything specific you'd like to see covered in future posts or if you have any questions, feel free to let me know. Maybe I can cover it in a future post. Happy coding!

from wg.

Hello, I could give this a try.
I just finished my first blog post here: test-driven-embedded-rust-development
Let me know if I could improve on it.

from wg.

Also should grab the embassy release notes: https://embassy.dev/blog/embassy-hals-released/

from wg.

Also should grab the e-hal 1.0 release notes: https://blog.rust-embedded.org/embedded-hal-v1/

from wg.

I just posted this getting started guide https://desilva.io/posts/debugging-arm-cortex-m-with-jlink-mini-and-arduino-portenta-h7-giga-r1-wifi-board

from wg.

At work we wrote about:

• Rust on ThreadX
• Rust on SPARC
• Using mem::take to reduce heap allocations in rustls

from wg.