ESP32 Revision
-
Is there a way to determine the revision of the ESP32 in a WiPy or LoPy? I ask because there are certain issues that are mentioned on the ESP32 forums that reference a particular revision number.
-
@jmarcelino Thanks! Good to know (and that only leaves one--brown-out reset, which isn't all that important).
-
@Eric24
The workarounds listed have been implemented in the ESP-IDF low level RTOS, which MicroPython uses.Where it says "There is no workaround for this issue." well it hasn't :)
-
@Eric24
Turns out that from 3 days ago you don't need to custom flash the chip to get it's revision, just put it programming mode (GND-P2, like when updating the firmware), get the latest esptool from https://github.com/espressif/esptool/releases/tag/v2.0 and run./esptool.py --port YOUR_PORT read_mac
You should get something like this (from my LoPy):
esptool.py v2.0 Connecting........_____ Detecting chip type... ESP32 Chip is ESP32D0WDQ6 (revision 0) Uploading stub... Running stub... Stub running... MAC: 24:0a:c4xxxxxx Hard resetting...
-
PS - Link to ESP32 errata document:
https://espressif.com/sites/default/files/documentation/eco_and_workarounds_for_bugs_in_esp32_en.pdf
-
@jmarcelino OK, that's about what I expected (based on ESP32 silicon release dates). Can I assume that all Rev0 bugs that have firmware-related workarounds have already been included in the latest firmware (for WiPy and LoPy)? Is there a list of silicon bugs that have not been "fixed"?
-
All L01 OEM modules use revision 1 and as far as I know the dev kits for now still use revision 0. Revision 1 is only a few weeks old.
There is a tool to check that through the efuses (by building a custom firmware), look in the esp32.com forums I don't have a link right now.
-
@Eric24
I do not know - but maybe helpfull is that all dev kits are 0 and OEM are 1.
If i'm wrong someone fix me.
