Espressif Systems

Yeah, there is a finger with a chip.

Yeah, on my desk right now I've got Espressif, I've got, uh, I've got some Nordic, I've got some Silicon Labs, some TI parts.

You know, basically a lot of the major ones, uh, they all work.

So yeah.

Um, the S31 that's coming out, and that's, like, a new one.

There was a Native Fruit article.

The S31 that's coming out from Espressif is actually gonna run Linux.

They've already just, they've proven that it runs Linux.

One thing that doesn't work is the, uh, host name.

Like under Espressif and other ports, even the Raspberry Pi, uh, Pico W where it has like native Wi-Fi, it will have a host name right here.

It's usually like CPY and then part of a unique thing like some hex digits and stuff.

Um, the Fruit Jam I think doesn't do that.

So it's IP address only right now the way I have it set up.

So 206... 192.168.206 works, but cpy.local does not.

Uh, possible there's an Espressif somewhere on my network, so it might, [laughs] it might hit something else, but the Fruit Jams don't.

Um, all right, we'll pop this one back up.

Thanks to Dan for all of the reviews.

This brings Ethernet support to the ESP, the Espressif port and to the Zephyr port.

So you get web workflow over Ethernet, which is great.

I'm currently doing two things at once.

The chip.

Espressif on one side, Android on the other, and they're not points on a spectrum.

They're two different philosophies of what a computer is.

The ESP32 is a microcontroller.

Onose labs have their own.

Espressif has DSP now.

And yeah, go, go and check the pull request.

Uh, it looked, the proposal for the API looked pretty cool.

Like that, that thing that you have in your car where like on your dashboard when you plug your phone, it starts showing Google Maps and whatnot.

Uh, typically this would be a fancy MPU and big Like Yocto-based distros probably that take a lot of time to build and that br- uh, bring, uh, with them, uh, like lots of dependencies and like effectively a, a large software bill of material and whatnot.

It turns out that if you have a reasonably powerful, uh, MCU, um, just enough RAM, uh, and a display and a USB, because this happens over USB, then you can do, uh, Android Auto head unit on Zephyr, and I have it running on SD boards, Renaissance board, Espressif boards, Native SIM.

Um, so again, this one is also, I'm in the process of polishing it up.

Um, in that vein, uh, Zephyr real t- real-time clock support is merged in, is very basic, um, but it added a native sim test, which was great.

Um, I have, uh, Ethernet support for Zephyr and Espressif.

Uh, it's almost out of PR.

I did a local review pass, but I have to look at the feedback, uh, back from the LLM about it.

I, I really like that this is, uh, sleep stream.

This is from Silvio from, uh, Espressif, though, so all, this is obviously it- the ESP stuff, right, the stuff that they do really well.

And, uh, so, uh, when I, when I did the traffic light CI demo last year, one of the thing that I wanted to do with that demo was to have the firmware build in GitHub pushing the firmware image with GitHub Pages, and then w- I wanted to have the device, uh, retrieving the image and flashing it automatically from GitHub, so a sort of, um, uh, over-the-air update without infrastructure using only GitHub Pages.

This was back when I thought that GitHub Pages was a reliable thing.

Like, if your, if your application is really big, uh, then you won't be able to-

Yeah.

Uh, so E- Espressif, uh, platform have external flash, so you're-

Yes

It really is.

So we have a stack of official Espressif programming guides on the table alongside a highly critical security advisory, specifically AR2026-006.

Right.

And the mission for this deep dive is clear.

We are on a mission today to really unpack a very specific, highly critical vulnerability.

For those of you managing hardware fleets or building IoT devices, or if you're just deeply invested in hardware security, you need to understand the exact technical mechanism here.

We're going to map out the causal chain and the broken trust boundaries behind the Espressif AR2026-006 security advisory.

And this affects a whole lineup of chips.