I'm trying to get v4.04 beta onto a new esp32-cam board ( https://www.amazon.co.uk/gp/product/B08YR7S2LP/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 ), I've got it all connected up, and pretty sure it's in the correct mode to upload, e.g.
13:49:13.867 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
13:49:13.867 -> flash read err, 1000
13:49:13.867 -> ets_main.c 371
13:49:14.200 -> ets Jun 8 2016 00:22:57
No gpio 0->gnd
13:49:14.200 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
13:49:14.200 -> waiting for download
With gpio->gnd - so pretty sure in a good state. I then start the Espixelstick flash tool, select Cam32, and serial port 3 (only one available), and get
-= Building Filesystem Image =-
bin/win32/mklittlefs -c fs/ -p 256 -b 4096 -s 0x30000 firmware/filesystem.bin
/config.json
/UpdRecipe.json
/www/alexa.html.gz
/www/apa102.html.gz
/www/artnet.html.gz
/www/ddp.html.gz
/www/dmx.html.gz
/www/e1_31.html.gz
/www/effects.html.gz
/www/esps.css.gz
/www/esps.js.gz
/www/favicon.ico
/www/fpp_remote.html.gz
/www/gece.html.gz
/www/index.html.gz
/www/mqtt.html.gz
/www/relay.html.gz
/www/renard.html.gz
/www/serial.html.gz
/www/servo_pca9685.html.gz
/www/tls3001.html.gz
/www/tm1814.html.gz
/www/ws2801.html.gz
/www/ws2811.html.gz
Done
-= Programming ESP =-
bin/win32/python3/python bin/upload.py --chip esp32 --baud 460800 --port COM3 erase_flash
esptool.py v2.8
Serial port COM3
Connecting.....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 9c:9c:1f:e9:03:6c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Erasing flash (this may take a while)...
Chip erase completed successfully in 11.5s
Hard resetting via RTS pin...
Done
bin/win32/python3/python bin/upload.py --chip esp32 --baud 460800 --port COM3 --before default_reset --after hard_reset write_flash -z 0x1000 firmware/esp32/esp32_cam-bootloader.bin 0x8000 firmware/esp32/esp32_cam-partitions.bin 0xe000 firmware/esp32/boot_app0.bin 0x10000 firmware/esp32/esp32_cam-app.bin 0x3D0000 firmware/filesystem.bin
esptool.py v2.8
Serial port COM3
Connecting........_____....._____....._____....._____....._____....._____....._____
Traceback (most recent call last):
File "C:\Temp\EspixelStick 4\bin\upload.py", line 19, in <module>
esptool.main(sys.argv)
File "C:/Temp/EspixelStick 4/bin/esptool\esptool.py", line 2890, in main
esp.connect(args.before)
File "C:/Temp/EspixelStick 4/bin/esptool\esptool.py", line 483, in connect
raise FatalError('Failed to connect to %s: %s' % (self.CHIP_NAME, last_error))
esptool.FatalError: Failed to connect to ESP32: Timed out waiting for packet header
Done
PROGRAMMING FAILED
Any ideas?
It looks like the upload tool does not support that model of the CPU.
This program "bin/win32/python3/python bin/upload.py" may need to be updated. You can try to upload a different version on your own.
For many of the ESP32-CAM boards, the issue is manipulation of the RTS and DTR lines which PlatformIO overrides for the ESP32-CAM environment. ESPSFlashTool doesn't manually force them so you may have to grab PlatoformIO and build / flash them manaully if you're having issues flashing the binaries.
I have the same ESP32 cam as shown in the OP's Link .
It flashes without issue in Win 10 using the java tool.
