Bricked ESP32-S3-Wrover? WT32SC01+ Development board #15935
Replies: 3 comments 6 replies
-
Had a look at the schematic and I don't see the usual transistor-pair used to control the boot lines (EN and IO0) for firmware upload. Why do they supply a specific bootloader program? |
Beta Was this translation helpful? Give feedback.
-
If you erase the first few blocks of the vfs filesystem, micropython will rebuild a new littlefs filesystem on the next boot, without erasing the micropython firmware. You should also use the same arguments to erase the flash that you did to flash the original firmware, eg: esptool.py -p /dev/ttyACM0 -b 460800 --chip esp32s3 --flash_mode dio --flash_freq 80m erase_region 0x200000 0x4000 If that succeeds and all goes well, micropython will create the new filesystem on the next boot. (You may also be able to use https://github.com/glenn20/mp-image-tool-esp32 that can help with investigating the partition table and rebuilding filesystems, etc.) That won't explain why the filesystem appears to be corrupted in the first place, but it might help you recover and debug the issue. |
Beta Was this translation helpful? Give feedback.
-
Seems like you got it sorted, but I wanted to add one more suggestion that may be useful in the future. The |
Beta Was this translation helpful? Give feedback.
-
Hello, I've been using micropython on and off as a hobbyist for a few years and have had a great time with it.
However, I recently purchased a WT32SC01+ development board and have now maybe bricked two of them when using micropython.
For both of them, the process went like this:
/home/patrick/.espressif/python_env/idf5.1_py3.8_env/bin/python ../../../esp-idf/components/esptool_py/esptool/esptool.py -p /dev/ttyACM0 -b 460800 --before default_reset --after no_reset --chip esp32s3 write_flash --flash_mode dio --flash_size 8MB --flash_freq 80m 0x0 build-ESP32_GENERIC_S3/bootloader/bootloader.bin 0x8000 build-ESP32_GENERIC_S3/partition_table/partition-table.bin 0x10000 build-ESP32_GENERIC_S3/micropython.bin
If I try to interactively create files using the REPL, I get:
If I try to erase_flash, I get:
If I try to re-flash, I get:
Following the docs, it would seem this development board maybe doesn't have hardware support for firmware reprogramming? But why did it work the first time so easily? Also, it says it can't connect to the serial port, but clearly it can because I can interact with it just fine via picocom and miniterm?
Any ideas on how I can recover these devices?
Beta Was this translation helpful? Give feedback.
All reactions