Not across all features, but certainly in specific ones. There are more advanced WiFi 6 chips, more advanced Bluetooth chips and faster MCUs. But they are all separate chips or companion ICs.
I'm puzzled by Espressif's naming here. We had the ESP32-S3, so "S31" sounds like "S3, variant 1," but this part doesn't really look like a simple S3 variant. And then there's an ESP32-E22, but no E21 or even a plain E2 anywhere.
They claim that the chip has an "MMU". But unfortunately this doesn't seem to be a true RISC-V MMU (according to the Sv32 specification) integrated into the CPU core itself, but just a peripheral designed for memory mapped SPI flash and PSRAM. So as far as I understand there is no true process isolation with page faults and dynamic paging.
I guess it hit mass production and then suddenly recalled and is now in sample status again with “X” variant. I designed boards using esp32-p4 and deployed and then suddenly local supply of esp32-p4 went dry. Now waiting for the x variant to go mass production but you can by samples directly from espressif for 3.33$.
I have great news for you: after several years of growing frustration with Espressif's inability to launch this chip properly in NA, I found a company called Wireless Tag that presumably felt the same way and just did it themselves:
I've now used this module in several projects. I love it. And I love (x3) the P4. It is amazingly powerful.
A lot of folks talk about the P4 not having radios as a problem; I personally think that it's an advantage. The assumption that every device is a wifi/BT device is baffling to me.
You'd have a very hard time convincing me to use anything but the WT0132P4-A1 at this point. They are cheaper than ESP32-S3-MINI-1U, too.
Although, I'd like to seem some non-paid blogger head-to-head reviews benchmarking instruction cycle efficiency per power of comparable Arm vs. ESP32 Xtensa LX6* and RISC-V parts.
* Metric crap tons of WROOM parts are still available and ancient ESP8266 probably too.
I don't understand what possesses these folks to continue making 2.4ghz devices. I understand there are use cases for low bandwidth, high range. But surely we've passed the point where that is more desirable to most than lower latency and high throughput, right?
Interesting that they made a new chip with BLE+BR/EDR again. all the chips after the original ESP32 were BLE only.
Hope this chip has good low power options so we can use it in Bluetooth audio workloads.
It would be good if this chip had good idle current comparable to other MCUs. I have used the ESP32S3 and it's idle current with the radio enabled, but not transmitting, is quite terrible.
My application needed both can bus and Bluetooth (though no wifi) so the S3 was one of the only options available. I'm sure the high current draw is because the wifi and ble share the same radio?
Honestly, I have very little interest in this module. I was a frequent S3 user who switched to the P4 last year when I realized that I could buy it in a WROOM-sized package:
The P4 is an amazing part, and the WT0132P4-A1 is cheap, highly available and easy to use. It has so much horsepower, and it's not encumbered by the mandatory wifi/BT stacks. It also has a genuinely superior capacitive touch solution compared to the S3.
For those of you who need radios, the recommended solution is to add a C3 as a coprocessor. I think this makes way more sense than bundling them, because it means you are free to use newer radio chips as they come out; this also makes the P4 somehow cheaper than the S3-MINI modules.
As for the S31, I just hope that they finally fixed the issues with ADC2.
38 comments
[ 2.8 ms ] story [ 56.3 ms ] threadI totally wish that a board would come with PoE…
Because as it is right now, powering a fleet of those with USB power supplies is annoying as fsck…
Edit: found an article explaining some of their naming logic, and said that the SoC naming will get its follow-up article, but sadly it never happened. https://developer.espressif.com/blog/2025/03/espressif-part-...
https://en.wireless-tag.com/product-item-56.html
I've now used this module in several projects. I love it. And I love (x3) the P4. It is amazingly powerful.
A lot of folks talk about the P4 not having radios as a problem; I personally think that it's an advantage. The assumption that every device is a wifi/BT device is baffling to me.
You'd have a very hard time convincing me to use anything but the WT0132P4-A1 at this point. They are cheaper than ESP32-S3-MINI-1U, too.
This is perhaps lost in the noise but IMO a large deal. PSRAM starting to get serious bandwidth.
It shocks me even more that any Western customer would do the same with network-connected Chinese chips. But we do.
The Espressif chips are truly incredible value, but what are we doing here?
Is there any doubt that these don't represent a major attack surface if a conflict were to heat up?
If you had network-connected chips of your own design inside every household of your adversary, what could you do with that?
I wonder if I at some point can create low power devices with EspHome for home assistant. I assume this should use less power than connecting to wifi?
Although, I'd like to seem some non-paid blogger head-to-head reviews benchmarking instruction cycle efficiency per power of comparable Arm vs. ESP32 Xtensa LX6* and RISC-V parts.
* Metric crap tons of WROOM parts are still available and ancient ESP8266 probably too.
I suspect a lot of the things people are using RPi for are better served by things like this (and virtualisation for the heavier end)
My application needed both can bus and Bluetooth (though no wifi) so the S3 was one of the only options available. I'm sure the high current draw is because the wifi and ble share the same radio?
https://en.wireless-tag.com/product-item-56.html
The P4 is an amazing part, and the WT0132P4-A1 is cheap, highly available and easy to use. It has so much horsepower, and it's not encumbered by the mandatory wifi/BT stacks. It also has a genuinely superior capacitive touch solution compared to the S3.
For those of you who need radios, the recommended solution is to add a C3 as a coprocessor. I think this makes way more sense than bundling them, because it means you are free to use newer radio chips as they come out; this also makes the P4 somehow cheaper than the S3-MINI modules.
As for the S31, I just hope that they finally fixed the issues with ADC2.