Hi,
We are using ESP32-WROOM32D module.
1 device out of 100 devices fails to program.
It happens at random location(or address).
I tried both 115200 and 921600, and symptoms are same.
Could it be the module internal SPI Flash failure?
And here is what's happening.
-------------esptool.py v2.6
Serial port /dev/tty.SLAB_USBtoUART
Connecting........____
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, Coding Scheme None
MAC: 24:0a:c4:17:e6:b8
xtal=84100010
xtal=84500010
io-mux= 800
io-mux= b00
Press the button
value= 1
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Compressed 8192 bytes to 31...
Wrote 8192 bytes (31 compressed) at 0x0000d000 in 0.0 seconds (effective 10955.2 kbit/s)...
Hash of data verified.
Compressed 25520 bytes to 14972...
Wrote 25520 bytes (14972 compressed) at 0x00001000 in 0.2 seconds (effective 1011.6 kbit/s)...
Hash of data verified.
Compressed 717888 bytes to 440611...
Writing at 0x0002c000... (29 %)
A fatal error occurred: Timed out waiting for packet header
------------------
Flashing aborted in the midst
Re: Flashing aborted in the midst
Hi Seungwhan,
Is the failing address different each time on the same device?
Usually this kind of failure indicates a problem with power supply, a problem with the serial link, or a problem with the connection between the ESP32 and the flash chip.
Angus
Is the failing address different each time on the same device?
Usually this kind of failure indicates a problem with power supply, a problem with the serial link, or a problem with the connection between the ESP32 and the flash chip.
Angus
Who is online
Users browsing this forum: No registered users and 105 guests