Closed roblatour closed 1 year ago
Hi, you have to put board on boot mode. Hold boot and then ress reset or unlug and plug cable again. This should work
I agree, that should work - and I did try holding the boot button down and then the 'En' button but it didn't work. Also tried unplugging it and plugging it in; still didn't work.
Here is what the screen looks like under chrome: https://ibb.co/sRMcygb
Notice the progress bars are blank, when I flashed my T-Display S3 these turn a solid blue/purple, but with the esp32-WROOM they don't.
I can however flash the board with a simple hello world sketch from the Arduino IDE without any issues.
I had the same Issue on Windows. After installing this Driver https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers an additional serial Interface was installed (Com7 in my Case) and using this new Interface i could flash the Firmware. Without the Driver the ESP was recognized on Com5 by Windows. Please see Screenshot.
@BuckligerBaron Thank you - installing the driver resolved the issue for me.
Esp32I can't upload either.
The flash tool at https://bitmaker-hub.github.io/diyflasher/ is not working for the esp32 wroom-32 devkit 1.
I tried both Chrome and Brave.
I pressed and held the boot button, pressed the EN button, and released the boot button (to put the device in upload mode).
With Chrome you can select the board and the port, but then in about 2 seconds the webpage says the firmware was flashed but it appears it was not as the Nerdminer Accesss Point doesn't appear in the list of wifi networks I can connect too.
Also, the percent completion bars remain unchanged (all white).
With Brave you can select the board but not the port. After selecting the board and clicking flash nothing happens.
I also tried to flash the board using the esspressif flash tool with the binaries on github - but that didn't work either.
When I turn on a com port monitor, I get the following:
19:10:20.033 -> 19:10:20.033 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 19:10:20.080 -> invalid header: 0xffffffff 19:10:20.112 -> invalid header: 0xffffffff 19:10:20.158 -> invalid header: 0xffffffff 19:10:20.205 -> invalid header: 0xffffffff 19:10:20.252 -> invalid header: 0xffffffff 19:10:20.283 -> invalid header: 0xffffffff 19:10:20.315 -> invalid header: 0xffffffff 19:10:20.393 -> invalid header: 0xfffffff�ets Jul 29 2019 12:21:46 19:10:20.393 -> 19:10:20.393 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 19:10:20.439 -> invalid header: 0xffffffff 19:10:20.471 -> invalid header: 0xffffffff 19:10:20.517 -> invalid header: 0xffffffff 19:10:20.563 -> invalid header: 0xffffffff 19:10:20.609 -> invalid header: 0xffffffff 19:10:20.641 -> invalid header: 0xffffffff 19:10:20.674 -> invalid header: 0xffffffff 19:10:20.752 -> invalid header: 0xfffffff�ets Jul 29 2019 12:21:46 19:10:20.752 -> 19:10:20.752 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 19:10:20.800 -> invalid header: 0xffffffff 19:10:20.845 -> invalid header: 0xffffffff 19:10:20.893 -> invalid header: 0xffffffff 19:10:20.940 -> invalid header: 0xffffffff 19:10:20.985 -> invalid header: 0xffffffff 19:10:21.018 -> invalid header: 0xffffffff 19:10:21.064 -> invalid header: 0xffffffff 19:10:21.111 -> invalid header: 0xffffffffets Jul 29 2019 12:21:46 ...
The tool has worked fine for my T-Display S3 boards, its just not working for my esp32 wroom-32 devkit 1 board.