48 comments

[ 5.6 ms ] story [ 55.9 ms ] thread
Love to see more RISC-V in the wild
Why? Because company you buy stuff from didnt have to pay license? I always imagine people saying this havent seen riscv assembler code.
Espressif is on fire! And the CPU even has SIMD instructions!

RISC-V cores is a big deal for embedded systems because now compiling for SoCs is only a matter of `rustup target add riscv32imac-unknown-none-elf` instead of downloading half-broken proprietary toolchains and SDKs.

Take a look at https://kerkour.com/introduction-to-embedded-development-wit... and https://kerkour.com/rust-esp32-pentest to get started with modern (Rust ;) embedded development.

Yeah but the moment you need IP blocks like for wifi or ethernet or usb, it's back to square one.
I need the equivalent of Claude Code, but for hardware projects, so I can actually do all the projects I envision with the EPS32s.

Something that combines: 3d printing; auto procurement of parts; custom software writing; maybe a robot arms or something, all in a nice box on my desk that I feed parts into like a mail slot. PROFIT.

Its good you can do that but the command doesn't exactly roll off the tongue.
The 1GB bandwidth is interesting. It also has Simd instructions too.

Could this theoretically be used as a router or wireguard vpn instance?

Good to have WiFi and wired ethernet on the same part again.

Although we lost the MIPI support that the P4 dual-core RISC-V line has.

I'm interested in audio out because I dabble in musical instruments.

What's the state of Bluetooth audio out on microcontrollers? Is low latency and high quality output possible?

Espressif products are not ideal for Bluetooth audio since support for classic Bluetooth (which is what is still mostly used for Bluetooth audio) is hit or miss , and on newer models often entirely missing.
I've been building hobby LED art projects with WLED (exclusively built on the ESP32 platform). It's been a blast. These little boards are so powerful and the open source community continues to amaze me.

My preferred controller platform is of the QuinLED line - comes with power distribution, voltage regulators, fat copper lines, configurable data-line resistors, and smart auxiliary hardware support all for an affordable $30-$50 per controller. (quinled.info)

<https://kno.wled.ge/> - WLED homepage and probably my favorite clever URL of all time.

What kinds of hardware are you using? I'm curious what LEDS/matrices you're buying? And also which controller from QuinLED you have? I've recently been having a lot of fun with some HUB75 displays and am interested in exploring other options and projects.
The specs look great, will see how long it takes to get these as WROOM modules or on little dev boards; my two form factors of choice for Espressif devices. I'm also curious about the pricing, so far they've impressed me with how much more you get in successive generations at a similar price.

If you're excited about the (relatively) speedy RISC-V cores and SIMD, look at the P4 which is available now. It has a slightly faster clock but no wireless: https://products.espressif.com/#/product-comparison?names=ES...

There's some cool work out there using the dsp functionality and built in image handling to crunch a lot of pixel data, which should work similarly on the S31: https://www.reddit.com/r/WLED/comments/1ry2jd7/wledmmp4_with...

If the prices remain relatively similar this is going to be incredible value! I might have to procrastinate on my current side projects to go back to another side project I'm procrastinating on because of optimization issues on an older ESP32.
They've already released the ESP32-S31-WROOM-3 and two development boards based on it: the ESP32-S31-Function-CoreBoard-1 and ESP32-S31-Korvo-1. All are available on Espressif's official Aliexpress store.
This looks like a nucleo144, except its risc-v... but why would I use it over said nucleo144?
Any reason why this device wouldn't have Z-Wave? Is the wireless protocol significantly different than Thread and Zigbee?
It being RISC-V is awesome, but how does it make sense that it's S series when S series have been Xtensa cores? Why is it not C series?
This looks like the long-awaited replacement for the original ESP32. The S and C series have been relatively low performance (the S better than the C but stuck on the outgoing Xtensa architecture), the P4 is powerful but lacks wireless. This is a relatively high performance, dual core MCU with wireless; a nice default option for low volume designs where being able to copy a previous implementation is more important than saving a few cents. Just like the ESP32. Nice.
How do I order a few samples, seem like there is a MOQ ?

Also I want to dive into hardware stuff but I'm always clueless as to what I do afterwards when this would arrive? Are you using a generic board or are you ordering and designing PCBs to hook this up to?

What are you using it for ? How do I go from a prototype to mass production via kickstarter?

Previous discussion from two months ago, when this was announced: https://news.ycombinator.com/item?id=47561678
Damn, I’ve only checked the last month for duplicates.
Oh, I wouldn't worry about posting a dupe. Announcement vs release is different enough, and people are clearly interested in it. I didn't link it as any sort of admonition; there was just some good discussion there.
I'm excited that this MCU and the P4 has RISC-V CLIC. That puts it at least on par with Cortex NVIC and enables bare metal frameworks like Rust RTIC to work really well.

Also 4x MCPWM peripherals; that's a first for any Espressif MCU.

The additional GPIOs are very welcome as well. CAN-FD!

This device is going to be a big hit for Espressif.

(comment deleted)
Is anyone else worried that these chips are all made in China?
I kind of wish these all weren't called ESP32. ESP8266 and ESP8285 -> ESP32 made sense, but now we have 10+ different versions with different features and different architectures.

Kind of like how in every thread involving a Raspberry Pi Pico (RP2030/RP2350), there's always someone confusing it with the single board computer version.

The ESP32 (Classic, usually WROOM-32E) is still usually what comes to mind when I hear ESP32.

Amusingly you just conflated the pico (a dev board) with its chip (rp2040)
> ESP32-S31 is particularly well suited for edge AI and machine learning workloads, including neural network inference

Any way to know what kind of performance one could expect running e.g. a depth anything model on there?

I wish Espressif was an American company and publicly traded. I'd invest heavily. I have nothing but good things to say about their products.

Their product naming could be better; S3 is going to show S31 in the search results.

Great to hear the adoption of RISC-V across the ESP32 line. The old Xtensa-based parts were fine, but RISC-V should make tooling, compiler support, and long-term ecosystem work cleaner
I'm the maintainer of a standalone printf library, targeting mostly embedded devices and other no-standard-library use cases:

https://github.com/eyalroz/printf/

I would like to make sure the library can be used on this SoC, and other RISC-V systems; which it probably can, but if there are any issues cross-compiling for it, or using the toolchain Espressif provides, please consider filing a bug report on GitHub at the link above. Same of course goes for any FOSS librar/tool that you're trying out.

Let's help foster a rich(er) ecosystem of software available on these babies!

This is so sick except it only has 2 pulse counters instead of the 4 on the S3 which means I can't use it as a drop in replacement on my current project. Not really complaining, I cut my teeth as an embedded dev on the ESP8266 and for years now all of my personal projects (and a fair few professional ones) have been based on the ESP32 line of chips. They're all pretty incredible for the cost, absolutely my favorite embedded target.
I personally am itching for more hardware H.264 or even H.265. There's the ESP32-P4 but it requires a second ESP32 to handle the WiFi. I got it working, but it feels like a hack, and the BOM cost is more than 2x a single chip.

Course more PSRAM and hardware encoding would drive up the price...