Espressif is on fire! And the CPU even has SIMD instructions!<p>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.<p>Take a look at <a href="https://kerkour.com/introduction-to-embedded-development-with-rust" rel="nofollow">https://kerkour.com/introduction-to-embedded-development-wit...</a> and <a href="https://kerkour.com/rust-esp32-pentest" rel="nofollow">https://kerkour.com/rust-esp32-pentest</a> to get started with modern (Rust ;) embedded development.
>> And the CPU even has SIMD instructions!<p>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.<p>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 last year I've switched from fixed point to floating point after holding off on that switch for ~15 years.
From the ESP32-S31 datasheet: "Single-precision floating-point unit (FPU) per core"
The datasheet apparently doesn't say, but judging by their other products' listed 12 bit SAR ADC sampling rates (and assuming this one is similar to what appears to be their standard ADC ) the conversion time will be on the order of 10uS.
Also why do you need 1uS for motor control? 1uS is 0.1 degrees of rotation at 16,666 RPM if I did the math right.<p>I don't know much about motor control, is it normal to need that fast of feedback?
>> Also why do you need 1uS for motor control?<p>It's not that important if you use current sensors on the motor phases. But then you're looking at HALL sensors or a shunt with a very high gain amplifier with good common mode rejection - looking for mV signals on top of a +12V or +48V square wave at PWM frequency.<p>By using low-side shunts under each half-bridge you don't need the common mode rejection, but you can only measure phase current while the low side FET for that phase is on. That means limiting the PWM duty cycle to ensure that FET is on long enough to measure current, so we trade available voltage range for sample time.<p>I've also written code to measure all phase voltages with a single low-side current shunt under the whole 3-phase bridge. That requires careful phase shifting of the PWM signals and very fast conversion time, but you don't have to compromise available voltage range 0-100 percent duty cycle is possible.<p>Typically we run the control loop at PWM frequency, but the measurements need to be faster than that.
Field-oriented Control schemes modulate phase currents at high frequency; the feedback loop must be much faster than the motor phases. Until fairly recently, this stuff was the exclusive province of dedicated ICs (Trinamic et al.) and FPGA. Today, FoC can be done in (mostly) software with MCUs.<p>Fast feedback loops are also necessary in SMPS, another area where precision, low latency MCU peripherals and software are actively displacing traditional approaches.
The closed loop experiences a phase margin loss that is exponential with the frequency. At lower frecuencies it is negligible, but if you get close to the frequency of the delay the phase margin reduction becomes dramatic and the control goes from stable to unstable very fast.<p>If the sensor has a limited bandwidth, you add the conversion delay and then the computation delay on top of that you end up with a max workable loop bandwidth in the low tens of kHz and anything higher will have overshoots, oscillations, etc.
You see this in low cost products like MKS SERVO42x, where they're doing FoC with a GD32 MCU. It works; the motor runs cool, smooth and quiet, but the system is limited to 3000 RPM, and struggles with rapid acceleration because the control loop is too slow.
I similarly don't know much about motor control or hardware in general, but would this maybe open up multiplexing options?
People will always find a reason to complain or pretend they are controlling rocket motor servos with their ESP32
[flagged]
where did you find cordic mention?
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.<p>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.
Tbh, we're pretty close to that. This would essentially be the following set of work cells:<p>- PCB etching/engraving<p>- Solder placement<p>- component placement<p>- solder oven<p>This gets you one layer populated PCBs out the other side. Commercial systems like this exist in various forms, and open source projects for all of these also exist. It would be up to you to integrate them together.<p>As it stands, the frontier models are actually pretty ok at firmware dev at a high level. If you need max performance, they won't be any good at all (learning from the dregs of the internet isn't exactly helpful here). You'll also need to bring at least a willingness to learn about what is involved so you can debug the machine's mistakes.
Its good you can do that but the command doesn't exactly roll off the tongue.
Curious: What does the "imac" stand for in the architecture target name ?
IMAC are the RISC-V extensions supported:<p>I = Base integer instruction set, 32-bit<p>M = Standard extension for integer multiplication and division<p>A = Standard extension for atomic instructions<p>C = Standard extension for compressed instructions<p><a href="https://en.wikipedia.org/wiki/RISC-V#ISA_base_and_extensions" rel="nofollow">https://en.wikipedia.org/wiki/RISC-V#ISA_base_and_extensions</a>
There are a few lettered extensions to the base RV32I instruction set. e.g.:<p>* <a href="https://docs.riscv.org/reference/isa/unpriv/m-st-ext.html" rel="nofollow">https://docs.riscv.org/reference/isa/unpriv/m-st-ext.html</a>
where did you find it?
Nice. Been meaning to try rust on these sort of devices but the riscv I saw thus far seemed to be mixed arm and riscv which seemed weird
The sooner ARM and its closed ecosystem dies, the better. The era of shitty half working blobs has gone on for quite long enough.
Almost everything we hate about ARM based systems is the result of <i>everyone</i> in the SoC ecosystem, not just ARM. It's just unfortunate for them from an optics perspective that they've been basically the only CPU core on the block so they get the brunt of the hate.<p>I place far, far more blame on companies like Qualcomm, Broadcom, Imagination Technologies (PowerVR), etc.<p>Go look at any of the non-microcontroller RISC-V based SoCs. It's not any better on any metric. Upstream software support is little to non-existent. Basically every RISC-V board needs a vendor kernel and they all have device tree and u-boot hell.<p>The SoC providers that make powerful chips are in the market of selling more chips - bad external support is a feature for them. Means that when they stop supporting the product you have to come buy a new chip. And if everyone does that, there's no better company to switch to because they all treat you the same.<p>About the only SoC vendor I have any respect for is Texas Instruments because they actually upstream a bunch of their code. Honestly I think this is because most of their parts are aimed industrial products and have support cycles >10 years.<p>I intentionally didn't say Rockchip because while they're in a bunch of hobby boards they don't really help with open source hardware work. They just take the position of "we won't stop you, but we're not going to help you".
very interesting, do you have a pointer with more info on what kind of SIMD support it has?
From the datasheet, I see that there is a Bitscrambler peripheral that seems to be very similar in flexibility to the Raspberry Pi Pico's PIO:<p>> Since bitwise operations can be relatively CPU-intensive and DMA is designed specifically to offload such work from the CPU, ESP32-S31 integrates two dedicated peripherals called BitScramblers. These modules are designed to transform data formats during transfers between memory and peripherals. One BitScrambler handles memory-to-peripheral (or memory-to-memory) transfers, while the other is dedicated to peripheral-to-memory transfers. While BitScramblers can handle the bitwise operations mentioned earlier, they are in fact flexible, programmable state machines capable of performing more advanced transformations as well.<p>Here's hoping that it's as useful as the Pi Pico's PIO
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.<p>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.<p>The ESP32 (Classic, usually WROOM-32E) is still usually what comes to mind when I hear ESP32.
You're fundamentally misunderstanding how MCU families work, I'm afraid.<p>There's <i>not</i> 10+ versions with different features. The word version strongly implies that there's an incremental progression over time, and they keep screwing up by adding and taking away modules. What jerks!<p>What's actually happening is that you have 4-5 different product lines that all share the same SDK, design philosophy, pricing structure, supply chain and support channels. Each one of these dimensions is extremely important to engineering teams designing products around them. It's not about hobbyists who are learning the ropes, although IMO they do a pretty good job of supporting those folks, too.<p>Within those lines (at this point, primarily S, C, H and P) you actually do have versions; for example, ESP32-S2 is no longer recommended for new designs because you should use ESP32-S3.<p>Ultimately, the lens you need to use to understand this stuff is: can I place an ESP32-labeled chip on my PCB and program it using the same SDK?<p>The same is true for the RP2XXX series of MCUs; if someone is confused by the difference between a microcontroller and a SBC then they might just be in the wrong place.<p>Bigger picture, some advice: when confronted by something like this, you will get further faster if you don't lead with the assumption that you have things figured out and everyone else is doing it wrong. Instead, keep an open mind and ask lots of questions. We're living in a golden era of enabling autodidacts but that's only true for folks who go long on humble curiosity.
But it's the same scheme as STM32, EFM32, GD32, …
It signals ESP-IDF compatibility
It's like these for other families too, you've got your STM32, then you can get the sub-models ranging from entry-level STM32C0 to the full Linux chips like the STM32MP2, with lots of options in the middle
<i>I kind of wish these all weren't called ESP32. ESP8266 and ESP8285 -> ESP32 made sense, but now we have 10+ different version</i><p>They've been hanging around with Sony.<p>Apple: AirPods<p>Sony: WMDF559J649Q-1
Showing up in search results, or in this day and age LLM results, is still king. If your famous product is known as the ESP32, it doesn't hurt sales to spin other products off the same line. It might hurt clarity, glance value and many other things, but it will drive people to you.
it's a marketing thing now
And toss away the brand name ?
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.<p>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)<p><<a href="https://kno.wled.ge/" rel="nofollow">https://kno.wled.ge/</a>> - WLED homepage and probably my favorite clever URL of all time.
I do a lot of LED projects too but I just use ws2812s. What do you need the controller for? Large brightness perhaps? Just curious.
There's lots of ways to drive LEDs.<p>WS2812 with any ESP32 board is one way, and that's a perfectly fine way; individual addressable LEDs sure are neat as hell. Amazing stuff can be done with them. And as you already know, a Chinese ESP32 dev kit costing $2 is enough to do ~all the things with this on the controller side. :)<p>But there's other ways, too. At perhaps its simplest: Maybe RGB isn't your bag, and you just want groups (which could be strips or any other shape) of all one color that are smoothly-controllable with WLED.<p>This is electrically simpler: While individual WS2812 pixels each work as a little computer-brain repeater for a serial bus, a group of dumb LEDs can be as simple as just being a group of dumb LEDs. And that's easy; perhaps as easy as one PWM channel.<p>Or maybe it's more complex: Maybe the goal is something like a par can that shines RGBAW all in one direction. Now we need 5 PWM channels.<p>Anyway, the power electronics for doing PWM with dumb LEDs can be built or they can be bought, but they need to exist and to live somewhere.<p>QuinnLED sells devices with power electronics in packages ranging from bare boards, to complete units with metal housings that have power and real ethernet on one side of the box and LED outputs on the other side.<p>Since skillsets and willingness to go full-DIY vary, they present pretty nice range of options.<p>One box I just looked at, the QuinLED An-Penta-Plus: It's a box that has 5 channels of PWM, does up to 10A per channel, or up to 30A combined per box -- at up to 48VDC.<p>That's [up to] 30*48=1440 Watts of LED, which is getting in the realm of the silly. But environment/projects come in all sizes, people do silly things with LEDs sometimes, and that's all perfectly OK. WLED projects don't have to be small. :)
WLED is a system that runs on the ESP32 for some cool capabilities to drive the ws2812s, OP linked above.
cr.yp.to/ is also a pretty cool URL, and has been around for a looong time
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.<p>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:
<a href="https://products.espressif.com/#/product-comparison?names=ESP32-P4NRW16X,ESP32-S31NRV16&type=SoC" rel="nofollow">https://products.espressif.com/#/product-comparison?names=ES...</a><p>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: <a href="https://www.reddit.com/r/WLED/comments/1ry2jd7/wledmmp4_with_native_hdmi_output/" rel="nofollow">https://www.reddit.com/r/WLED/comments/1ry2jd7/wledmmp4_with...</a>
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.
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.
Good to have WiFi and wired ethernet on the same part again.<p>Although we lost the MIPI support that the P4 dual-core RISC-V line has.
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
Previous discussion from two months ago, when this was announced: <a href="https://news.ycombinator.com/item?id=47561678">https://news.ycombinator.com/item?id=47561678</a>
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.<p>Course more PSRAM and hardware encoding would drive up the price...
I'm interested in audio out because I dabble in musical instruments.<p>What's the state of Bluetooth audio out on microcontrollers? Is low latency and high quality output possible?
Is there any reason you want wireless? Bluetooth audio is a disaster, AFAIK. You don't want to use it for music. Just go wired, the ether is too cramped already.
There aren't many choices of cheap hackable A2DP receivers if you were somehow looking for one. Not all headphone chips are programmed to run at slightly under 3.3V on VBAT pins so to protect the supposed battery, with no means to reprogram for lower voltages, officially or not.
There are alternatives, but being able to use an external amplified speaker and also move around easily would be nice. Maybe it's not feasible yet.
Low latency in Bluetooth audio comes down to codecs and the best are proprietary.<p>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).<p>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 chips just aren't quite powerful enough for high-quality music encoding, unfortunately. I'm hoping the S31 might be a bit better fit here (decent CPU boost + better SIMD).<p>Latency is still a bit rough with BT overhead. There might be some new options with LE audio on the S31 but I haven't found a way to get below ~80ms with the existing ESP32-S3 stack.<p>tl;dr, high quality voice is doable today with okay latency, music probably less so, maybe the S31 will be better
I haven't benchmarked Bluetooth on these devices but have you looked at your uncompressed audio rates over WiFi? OP was asking about Bluetooth at high quality and low latency, which I don't think is a possible combo, hence suggesting another ESP32 if wireless is necessary. If it isn't, a wire difficult to beat.<p>ESP-NOW is another option to look at, which of course won't work to transmit to a phone directly but can do a point-to-point or multicast transmission between ESP32 devices. I've used it in some projects but not for audio, I couldn't tell you how much of a buffer would be needed to make that work smoothly.<p>Another option for OP, if the audio is being synthesized then the parameters could be transmitted rather than the audio samples themselves and do synthesizing on the receiving device.
You don't just use four simultaneously connected audio profiles and interleave them?
> I'm interested in audio out because I dabble in musical instruments.<p>Sorry, I don't know. I'm just responding to echo and expand on another reply that Bluetooth for anything related to serious music, from audio playback to MIDI input is a dumpster fire on Windows.<p>Several years ago I tried to set up a high-end Windows laptop for hobby DAW composition on the go. The real-world BT audio latency just from laptop to headphones/earbuds was unworkable and, separately, the input latency from BT midi controllers was unworkable. Stacked together the total lag was laughable.<p>At the time, the issues were widely known and much lamented. Some tech blogs (including one at MSFT) indicated there were issues at every level of the stack (drivers, firmware, silicon) and work was proceeding to address the end to end shit show. The only workable Windows solutions referenced online involved using specific non-Bluetooth wireless devices. Needing to have a dedicated USB dongle hanging off the laptop combined with having a choice of either one specific device or a receiver dongle to support all devices, is less appealing than just having a wire.<p>Since then I've looked again every year or so but have seen no reports yet of meaningful progress and there's even <i>less</i> discussion of work in progress. Very disappointing. And the situation on the BT audio quality side doesn't seem much better. If you don't want degraded audio quality it's either choosing very specific devices which support a proprietary BT codec or switching to non-BT wireless dongle hardware. At least there is talk of improvement on audio quality but no clear indication better baseline <i>minimum</i> audio quality will <i>ever</i> be mandated in the BT audio standard.<p>If anyone has info the baseline latency or quality (input or output) of <i>standard</i> BT devices in Windows configs will improve, I'd be delighted to hear it.
[dead]
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.
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.
I'm excited that this MCU and the P4 has RISC-V CLIC. That puts it <i>at least</i> on par with Cortex NVIC and enables bare metal frameworks like Rust RTIC to work really well.<p>Also 4x MCPWM peripherals; that's a first for any Espressif MCU.<p>The additional GPIOs are very welcome as well. CAN-FD!<p>This device is going to be a big hit for Espressif.
> ESP32-S31 is particularly well suited for edge AI and machine learning workloads, including neural network inference<p>Any way to know what kind of performance one could expect running e.g. a depth anything model on there?
Regarding specifically depth anything: You're not running this on a microcontroller.
In general, CNNs still reign supreme on microcontrollers since you have a way lower peak memory demand which is what usually kills you. Here in this case you have a couple of _kilobytes_ of SRAM, potentially extendable to a couple of megabytes of PSRAM.<p>Even for small CNNs you often need to do some quite complex interleaving of layers (i.e. running parts of layer 1 and layer 2 in parallel interleaved to take advantage of the downsampling of CNNs) to keep performance and memory impact reasonable (see e.g. <a href="https://openreview.net/pdf?id=2O8qbyxH6X" rel="nofollow">https://openreview.net/pdf?id=2O8qbyxH6X</a>).<p>Think more "image classifier" less "run an image to image transformer". For depth anything, a single layer's activation is probably significantly larger than the available SRAM (I think it is (224/16)^2 patches each with activations [48, 96, 192, 384] for depth anything small: You aren't running this.)
A real example <a href="https://github.com/OHF-Voice/micro-wake-word" rel="nofollow">https://github.com/OHF-Voice/micro-wake-word</a>
I was wondering this as well. What exactly makes this a good AI chip vs others.<p>Unless they're not listing a major feature in their spec, a dual core 320Mhz microcontroller is not bad but youre not going to be running any kind of vision model on it, at least very fast.
Memory is the main constraint. You have what, 8mb of psram.<p>Compute wise you can manage. You can do quantisation and run a small 10-15 layer CNN perhaps. Image classification is possible. Keep in mind the channel count and input resolution cannot be high since memory will be a problem. You can maybe do face _detection_, "is my cat on my keyboard" classification as well maybe.<p>Audio, you can do a lot more. Wake word detection happens on _much_ smaller accelerators inside iphones. In this one you can do slightly heavier classifications. Maybe speaker identification "which member of family" or maybe "which dog is barking"
nope. not happening. at most YOLO or mayyybe FastDepth
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?
S has never implied Xtensa, and C doesn't imply RISC-V. That's a widely held misunderstanding. S, C, P, etc. are product categories, not ISAs. S devices are high performance SoCs; large feature set, high frequency, not the lowest power or cost.<p>Just appending 1 to S3 is odd though. This MCU is step change for Espressif. S4 or something would make more sense.
Not saying you're wrong (appreciate the explanation) but S <i>has</i> been Xtensa and C is RISC-V; even if you don't imply, it's how the things have been. And given S2, S3, and C5 are all clocked at 240 MHz, the performance difference is kinda blur.
Espressif is all-in on RISC-V, expanding their portfolio of RISC-V devices where they previously had only XTensa: ESP32-S31 is the first big departure from the coincidental alignment of ISAs within their product structure and definitively ends further debate about what those letter designations mean.<p>BTW, S3 has an RISC-V core in addition to the XTensa cores. That's the part that's running in deep sleep.<p>In practice, most Espressif users barely know or care what ISA is in play: they have ESP-IDF and the Espressif libraries papering over the difference for nearly all purposes.
This is how Jeroen Domburg, Espressif Technical Marketing Manager, addressed this matter in a post on hackaday.io:<p>"We actually never intended the CPU architecture to be part of the name, as for 99.9% of all users, it doesn’t matter: you write your code in C or some other language, and the compiler plasters over any difference in ISA. Available peripherals, supported radio protocols and CPU power and memory are more important."
Any reason why this device wouldn't have Z-Wave? Is the wireless protocol significantly different than Thread and Zigbee?
As I understand it, Z-Wave is substantially more closed/proprietary. Both Thread and Zigbee are protocols that run on top of 802.15.4, which Espressif already has in other products.
I don't know for sure but Bluetooth, WiFi and Zigbee are on the same frequency band. Z-Wave is not.<p>(at least in the US, not sure about other countries)
This device only has a 2.4GHz radio. Z-Wave is sub-1GHz.
Z-Wave works on a different frequency and would separate radio hardware. And then comes the licensing cost.
Z-Wave is completely different from Zigbee. Different frequency bands, modulation, etc.<p>And there are still just two suppliers of Z-Wave radios, as far as I know. I haven't bothered to re-check recently. Up until ~2022 there was just _one_ supplier, you could open any Z-Wave device and find exactly the same chip. Sometimes on a cute little daughter board.
How do I order a few samples, seem like there is a MOQ ?<p>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?<p>What are you using it for ? How do I go from a prototype to mass production via kickstarter?
Typically you look for a development board with the chip embedded on it. The dev board will have a usbc port and multiple pins that can be routed to LEDs, miniscreens, audio devices, etc. To program it you can usually use Lua (a very simple embedded language, almost JS-like) or you can use C/Rust/Zig as well. Arduino IDE works for it, too. You code from desktop and upload ROMs via USBC.<p>You can plug the dev board into sandwich board for easier prototyping. To go to mass production, you'll need to hand off your prototype spec to a custom PCB maker that you can order from, prices vary a lot based on volume and some shops specialize in low volume for early products.<p>Your end product should basically be a circuit board, case, battery, and any external components like LEDs or screens, then you assemble with plugs or wiring/soldering.<p>It is sometimes possible to make a product from the dev boards, especially the small ones, but your product still has to get a custom FCC certification (not a deal breaker, just a hoop to jump through), whether using dev board or custom.
Meanwhile, Texas Instruments[0]...<p>0. <a href="https://news.ycombinator.com/item?id=48378136">https://news.ycombinator.com/item?id=48378136</a>
Love to see more RISC-V in the wild
When can we buy these?
Apparently available on AliExpress as a dev board[0]<p>[0] "ESP32-S31-Korvo-1 Development Board Espressif System AI Intelligent Multimedia Development Board Engineering Sample" for £54.79 from the (allegedly official) Espressif store at <a href="https://www.aliexpress.com/item/1005012333744553.html" rel="nofollow">https://www.aliexpress.com/item/1005012333744553.html</a>
The dev boards are already up for sale. I'm personally looking forward to the modules being stocked on LCSC, no idea when though.
Is anyone else worried that these chips are all made in China?
I am concerned by all chips and software made by giant corporations. None of them are trustable, and any one of them will sell me out for a buck.<p>We must constantly fight to have open source and audited chips and software made in commodity fashion.
You might be interested in the Baochip<p><a href="https://www.crowdsupply.com/baochip/dabao/updates/our-campaign-has-launched" rel="nofollow">https://www.crowdsupply.com/baochip/dabao/updates/our-campai...</a><p>Probably the most open chip on the market, and sits between a pi and a pico
For what its worth, Espressif chips are open source, but yes, I wouldn't run national security or government devices on these.<p>Edit: I take it back on OS comment, they are not OS but some components of the SDK are:<p><a href="https://zeus.ugent.be/blog/23-24/open-source-esp32-wifi-mac/" rel="nofollow">https://zeus.ugent.be/blog/23-24/open-source-esp32-wifi-mac/</a>
This looks like a nucleo144, except its risc-v... but why would I use it over said nucleo144?
Because it's like 5x cheaper and beats it out spec wise in almost every way?
Better connectivity. The Nucleo 144 only has 100mbit ethernet, as far as I can tell, but the new ESP chip has gigabit, along with wireless.
WiFi+BLE?
I'm the maintainer of a standalone printf library, targeting mostly embedded devices and other no-standard-library use cases:<p><a href="https://github.com/eyalroz/printf/" rel="nofollow">https://github.com/eyalroz/printf/</a><p>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.<p>Let's help foster a rich(er) ecosystem of software available on these babies!
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.<p>Their product naming could be better; S3 is going to show S31 in the search results.
The 1GB bandwidth is interesting. It also has Simd instructions too.<p>Could this theoretically be used as a router or wireguard vpn instance?
Theoretically, yeah. Though at 320Mhz, with only 2.4ghz wireless, even with two cores, I doubt it's going to get anywhere near the throughput to fill the gigabit connection.
[dead]