For investigating Random memory corruption faults on ESP32-WROVER rev.1 and rev.2 when running in dual-core mode, we wanted to know about the chip revision of the ESP32 embedded into the FiPy device on our workbench.
When running on the Pycom expansion board, you will have to put the PIC on the expansion board into firmware update mode using Pycom’s pypic.py before being able to use the vanilla esptool to interact with the ESP32.
pypic.py is available from pycom-micropython-sigfox/pypic.py at Dev · pycom/pycom-micropython-sigfox · GitHub.
See how that goes.
Enter programming mode
export MCU_PORT=/dev/cu.usbmodemPy001711 # libero
python tools/pypic.py --port $MCU_PORT --enter
Inquire chip id
esptool.py --port $MCU_PORT --after no_reset chip_id
esptool.py v2.8
Serial port /dev/cu.usbmodemPy001711
Connecting.....
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 80:7d:3a:c2:de:44
Uploading stub...
Running stub...
Stub running...
Warning: ESP32 has no Chip ID. Reading MAC instead.
MAC: 80:7d:3a:c2:de:44
Staying in bootloader.
Inquire flash id
$ esptool.py --port $MCU_PORT --after no_reset flash_id
esptool.py v2.8
Serial port /dev/cu.usbmodemPy001711
Connecting....
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 80:7d:3a:c2:de:44
Uploading stub...
Running stub...
Stub running...
Manufacturer: c8
Device: 6017
Detected flash size: 8MB
Staying in bootloader.
Leave programming mode
python tools/pypic.py --port $MCU_PORT --exit