Felipe Balbi

I decided to make my own keyboard. I've been an urchin for a few years and, before that, a ferris sweep. Now I have a redesign of the urchin on a reversible PCB and 36 keys instead of 34. It will run RMK, at least that's what I'll flash on mine. Once it's tested, I'll make the designs public.

Device-driver release time! Version 2.2.0 introduces the LSP support I've been teasing for a while. This is coupled with a vscode extension. But the LSP should work anywhere you can hook it up to. Lots of internal changes too, probably the biggest MIR change since 1.0.

Please, install and test the latest probe-rs. @dbuga.bsky.social merged all of my proposed fixes/improvements. If you have cortex-m devices, make sure to check that there are no known regressions. I checked with STM32G071RB, MCXA266, MSPM0G3519, and STM32F405.

I've got 2 bugs and 2 enhancements for sequential-storage that require a "disk-breaking" change. So at some point I'll come with a properly breaking release. I don't think I want to maintain two disk formats. So if you have an idea for a (disk) breaking change, please open an issue!

Interested in trying out a Baochip-1x? The 'dabao' evaluation board is now taking pre-orders on Crowd Supply: www.crowdsupply.com/baochip/dabao

I'm torn. I pushed a few PRs to `probe-rs` which improve stability and performance of MCXA targets. There's even a new proposed API for faster image verification which skips a read-back if the HW supports a verification command. The problem: several inconsistencies in vendor documentation :(

Ugh, thanks @diondokter.nl for telling me my handle was invalid. I moved my DNS to desec.io a couple days ago and forgot to port over _atproto TXT record :)

Proof of first low-level driver version :) 2 channels in ext. driven dither mode. Figure shows the signals & trigger. Working with device-driver by @diondokter.nl and Pico de Gallo by @balbi.sh is amazing! Working repo: github.com/trappitsch/l... See example: ll_dither_ext.rs #EmbeddedRust

Must say, seeing folks outside my team at work using pico de gallo is a really nice feeling :-) Cheers @galactic-forensics.space

Hype! blog.rust-lang.org/2026/08/04/e...

Excited to see device-driver moving forward! It’s an amazing crate.

Super glad to see this getting more love. Thanks @jamesmunns.com for all the fish :-)

I’ve been tinkering with Clash and wondered if I could make validating eSPI controller drivers easier. That idea became Tamal. 😊 Clash core + Rust tools! It’s experimental, but should be useful. Why I built it: balbi.sh/posts/tamal-... Code: github.com/felipebalbi/... #haskell #clashlang #fpga

Spent a few weeks bringing up an I3C target driver for NXP MCXA in Rust/embassy. Three gotchas each took a day to diagnose and a line to fix — a 4× slow clock, a FIFO race, and a sneaky Stop that wrecked my framing. Wrote it up to make sure I never fall for these again 👇 balbi.sh/posts/i3c-ta...

I'm biased because I helped write part of it (and @balbi.sh has continued adding even more info!), but I think the `embassy-mcxa`'s DEVGUIDE is probably one of the better references now for "how embassy HALs work and how to write a good one", if that's what you're in to. github.com/embassy-rs/e...

Hi everyone, I wote a few more (personal) ideas on how I'm using Pico de Gallo for crate examples. These are personal opinions, not prescriptive in any way. balbi.sh/posts/exampl...

More metapacs, that's exactly what we need. Hopefully an embassy HAL can be built on top of this work :-) Amazing.

Write embedded drivers without the MCU in your dev loop. Pico de Gallo turns a Pi Pico 2 into a USB-attached I²C/SPI/UART/GPIO/ADC/1-Wire bridge, so your driver is just a cargo run binary talking to real silicon from your laptop. Build one for your chip → balbi.sh/posts/writin...