Hi Munque,
Munque wrote: ↑Wed May 06, 2020 11:22 pm
1 - Is the ESP32v3 the next version following the ESP32S2 or a different version?
This is a good question, can appreciate that the naming is a little bit confusing:
ESP32 V3 is a silicon revision of ESP32. (There have been ESP32 revisions 0, 1 and now 3. Version 2 was never made widely available.)
ESP32-S2 is a new design, not a revision of ESP32.
(The fact one of these has S2 in the name and the other has a V3 is coincidence, the two numbers don't relate to each other.)
Munque wrote: ↑Wed May 06, 2020 11:22 pm
2 - Are either the ESP32v3 or the ESP32s2 available for purchase? Searching those as key words turns up items like a "Nodemcu V3 V2 ESP32" -- kind of ambiguous. Most search results don't indicate anything.
Both chips are available. If you're looking to purchase commercial quantities for a product, then you can
contact sales for a quote.
If you're looking at random listings on retail websites then I'd assume anything that says it's an ESP32 is not revision 3 yet (the V3 V2 thing for NodeMCU probably refers to the board version). But you'd need to ask the seller to be sure.
Munque wrote: ↑Wed May 06, 2020 11:22 pm
3 - If you have existing ESP32s, how do you determine whether you've got a V3, V2 or V1? (e.g. Running
esptool.py reac_mac (or
flash_id, etc) one MCU reveals
Chip is ESP32D0WDQ6 (revision 1) Is that seems like it's neither v2 nor v3 (aka ECO3), but it would seem "revision 1" has nothing to do with that.)
"revision 1" here is silicon V1, aka ECO1.
For ESP32 V3 or ESP32-S2 the markings on the chip itself will be different, and the markings on Espressif-produced modules will also be different. (For third party modules you'll have to ask the manufacturer of the module, but I would expect they'd also change the markings.)
esptool.py will print the revision information when it connects, so running the read_mac or flash_id command is a great idea. Note that you need
esptool v2.8 or newer to detect ESP32 V3, older versions predate V3 and will incorrectly print "revision 1" instead of "revision 3". (esptool.py will also print its version number when it runs.)
Similar to the previous question, generic ESP32 development boards bought on the open market are likely to be "revision 1" at the moment.
Munque wrote: ↑Wed May 06, 2020 11:22 pm
4 -
This comparison sheet shows a few tradeoffs between the ESP32 and the ESP32-S2. (Numerous upsides of the S2, as well as some downsides: smaller SRAM & ROM, no bluetooth, no ethernet (what does ethernet on an ESP32, anyway?), half the number of soft PWMs, no SDMMC, no hall sensor.) Is there a comparison sheet available that includes the V3?
The feature set of ESP32 V3 is almost exactly the same as earlier ESP32 revisions. There is a document "ESP32 ECO V3 User Guide" which lists the differences:
https://www.espressif.com/sites/default ... de__EN.pdf
Note that if you're not using any of the external PSRAM, Flash Encryption or Secure Boot features then in my opinion there is not a compelling reason to hold out for ESP32 V3. (The security bug linked above only relates to physical security which uses these two security features.)
Munque wrote: ↑Wed May 06, 2020 11:22 pm
(what does ethernet on an ESP32, anyway?)
There's an integrated Ethernet MAC controller. You can connect an Ethernet PHY to the chip and bring up an ethernet interface in your app.