We tackled the challenge of writing an over-the-air firmware update mechanism for the lossy LoRaWAN network. In this blog, David explains how we reconstructed the lost data using parity blocks: https://tweedegolf.nl/en/blog/158/reconstructing-lost-data-from-parity-blocks

This work was performed in close collaboration with Philip Markgraf for Kelvin.

@tamme is speaking about the Rust Embedded Ecosystem at the online Rust on Embedded - Elektor Academy Pro Conference on 16 July 2025!

Early-bird tickets here: https://elektor.scoocs.co/public/event/rust-on-embedded (until 18 June)

Curious about Rust on Embedded? Sign up for "Rust on Embedded", the upcoming online Elektor Academy Pro Conference on July 16th. Juraj Michálek from #Espressif will showcase #Slint, #BevyEngine and more running on Rust with no_std.

https://www.youtube.com/watch?v=N_PrevR02kU

https://www.elektormagazine.com/news/rust-on-embedded-conference

Lol, why adding rust vec! in completely logical part of program separated from ADC readout is causing malfunction 0 ADC readout lmao

@diondokter's RustWeek talk 'Codegen your problems away - device-driver toolkit' was recorded and uploaded to YouTube. Watch it now: https://www.youtube.com/watch?v=xt1vcL5rF1c

@rustnl
#rustlang #embeddedrust #rustweek

I wrote some ST7789 screen driver Rust code which just takes bytes from memory and flushes them into the screen. It seems to work but somehow the screen turns completely white less than one second after the memory write operation. This used to work fine, so I was wondering if maybe some other driver was interfering with the SPI, but nope, I disabled everything else and it still does that. I wrote a small test program which uses a different library to speak to the ST, and it works just fine. I am probably doing something wrong somewhere, BUT THEN WHY WAS IT WORKING OK BEFORE? I suspect some weird timing issues. Or maybe my driver code is being optimized by the compiler somehow, and things are not being done in the correct order?

I will probably plug in a logic analyzer tomorrow, but if anyone has any tips on how to debug it...

has anyone coaxed the #rp2350 into using PSRAM with embassy-rs? I couldn't find an obvious example in my searches this morning. I did find some arduino startup code that I can probably translate and adapt, but if someone has already done the heavy lifting, that would save me some effort! #rust #embeddedrust #rustembedded #pico2

Omar Hiari is now presenting "The five pillars of Embedded Rust" at Rust In Paris.

Oo, remember last week when I said I didn’t think I had a project I’d like to use to learn #rust?

I may have one - #EmbeddedRust on an #Arduino

Hm. I think I have the various bits around…

https://blog.logrocket.com/complete-guide-running-rust-arduino/

From: @rmartinnielsen
https://mastodon.social/@rmartinnielsen/113970296851975261

Watch: @tamme presents 'Chips don't bite!' at RustLab 2024, giving 'a fearless introduction to µController programming for Rustaceans'!

https://www.youtube.com/watch?v=vtIovLsacj8

I'm struggling with some Rust confusion ... specifically, esp-hal::dma. How does one idiomatically allocate a DmaTxBuff in PSRAM? ... At this point, the compiler is happy, but the ESP32s3 just seems to hang.... All I want is some 800x480 display. Am I being greedy?

#rust
#EmbeddedRust
#ESP32

@tamme presented 'Chips don't bite!' at RustLab 2024, giving 'a fearless introduction to µController programming for Rustaceans'!

Things were learned, enthusiasm shared, and pictures were taken!

Thanks to @rustlab for the photos.

@tamme is at RustLab 2024 in Florence, and will present "Chips don't bite! A fearless introduction to µController programming for Rustaceans" this Sunday!

https://rustlab.it/talks/chips-don-t-bite-a-fearless-introduction-to-ucontroller-programming-for-rusteacea

#RustLab2024 #RustLab #rust #rustlang #embeddedrust #rustprogramming

@rustlab

Anyone looking for an #embedded engineer? Full time remote strongly preferred. #getFediHired

I am experienced with #EmbeddedC and, to a lesser degree, #EmbeddedRust and #EmbeddedJava. I even wrote JNI bindings for Java in Rust to call into Tock:OS. I have some recent experience with a very large C++ code base, but I wouldn't call myself an expert with it. I also have experience building test automation frameworks written in #Python and #Rust.

Oh, sorry for the edit spam. But I almost forgot to mention that I have extensive experience with the #RISCV architecture and instruction set.

Writing some Rust on a pico with embassy and thus async/await really does feel like a superpower...

Akira Moroo will now present "Firmware in Rust: More Than Just 'Rewrite It In Rust'"

FML the #SSD1306 crate is not ready for async and the #oledasync does only support 1309.

Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.

I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.