Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ESP32-S31

espressif.com

Post reply on HN
Print view View original

161–170 of 207 posts

Re: ESP32-S31

#161

Post by kelnos »

9rx wrote: post #90
JCTheDenthog wrote: post #74

Earlier quoted context omitted.

They can signal that with numbers other than 32, the "ESP" part is what matters.

ESP-IDF is only compatible with the ESP32 range of devices, not all ESP-prefixed devices, so "ESP" alone is not sufficient information to satisfy the earlier comment.

Sure, but there's nothing in the name "ESP-IDF" that inherently means it can only support ESP32 devices. It could also support a new theoretical ESP33 device.

(I don't have an issue with Espressif's ESP32-* naming scheme, but I don't think the ESP-IDF angle is a good argument for not changing it.)

Re: ESP32-S31

#162

Post by v1ne »

It's sad to see Xtensa go. Their architecture was a clean design, a treat to read the assembly code. I get it, RISC-V comes without licensing costs, but that's one of the few positive things about it. For a fresh start, it is just already in this "we pile stuff on stuff on stuff" state that you expect of an architecture after 10-20 years of productive use.

Re: ESP32-S31

#163

Post by dsign »

I very much respect Espressif products, specially because how good their documentation is. I wish though somebody would package an ESP board with 256 Mb of RAM or more... From what I've seen, that amount of RAM seems to be exclusive Linux SBC territory, but Linux doesn't make sense for a lot of projects.

Re: ESP32-S31

#164

Post by andynerd »

throwaway81523 wrote: post #81
tosh wrote: post #9

Earlier quoted context omitted.

very interesting, do you have a pointer with more info on what kind of SIMD support it has?

Why on earth SIMD instead of the risc-v vector extensions that are supposed to be better?

For compatibility and simplicity. Most SIMD instructions in P4 and S31 (compatible with P4 rev 3.x) are an direct evolution from S3. Espressif just doesn't want to rewrite their optimized assembly libraries.

Re: ESP32-S31

#165

Post by andynerd »

dsign wrote: post #163

I very much respect Espressif products, specially because how good their documentation is. I wish though somebody would package an ESP board with 256 Mb of RAM or more... From what I've seen, that amount of RAM seems to be exclusive Linux SBC territory, but Linux doesn't make sense for a lot of projects.

Sadly this S31 can address up to 64 MiB of PSRAM at most. And only 32 MiB SKU has been released.

Re: ESP32-S31

#166

Post by andynerd »

phkahler wrote: post #13
randomint64 wrote: post #3

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…

>> And the CPU even has SIMD instructions! Yes, but it looks like there is no hardware floating point. The description of the CORDIC module indicates fixed-point calculations, which is consistent with the lack of any reference to floating point. I am happy the have CAN-FD and Motor PWM module, but nowhere did I see conversion times listed for the ADC. For motor control I demand 1uS conversion time or less, and in the…

Both HP cores have single-precision FPU. But only HP core 1 has SIMD, unlike S3 and P4.

Re: ESP32-S31

#167

Post by AshamedCaptain »

timothyb89 wrote: post #71
oritron wrote: post #24

Earlier quoted context omitted.

Low latency in Bluetooth audio comes down to codecs and the best are proprietary. If you want to really cut down latency and need wireless with hardware like this, you could use a second ESP32 and send your own bitstream between them.

I've been experimenting with more-or-less this on the existing ESP32-S3 (well, to a smartphone/PC rather than a 2nd ESP32). Practical bandwidth limits are in the ~72kb/s range with Bluetooth and a custom wire protocol, and Opus voice-mode encoding can't run in realtime beyond complexity 3; music encoding can't run at all. Maybe there's a more compute-friendly audio codec I'm not aware of, but as far as I know these c…

I was not aware that _any_ Espressif hardware even supported classic bluetooth other than the very first ESP32 (which I am not sure if they're even available). And I was getting around 50ms latency back then (with the original ESP32 and SBC!)

What exactly did you try?

Re: ESP32-S31

#168

Post by AshamedCaptain »

skybrian wrote: post #10

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.

Re: ESP32-S31

#169

Post by MrBuddyCasino »

v1ne wrote: post #162

It's sad to see Xtensa go. Their architecture was a clean design, a treat to read the assembly code. I get it, RISC-V comes without licensing costs, but that's one of the few positive things about it. For a fresh start, it is just already in this "we pile stuff on stuff on stuff" state that you expect of an architecture after 10-20 years of productive use.

The inevitable result of Risc-v trying to be everything to everyone, so everything is half-baked.
Post reply on HN