Problem flashing brand-new ESP32-CAM. #15693
-
|
It is a bit OT (as this is not strictly Tasmota problem):
` rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2)) If then try to upload firmware, I get success: `[laurent@laptop4 esptool]$ ./esptool.py --chip esp32 --before default_reset --after hard_reset --port /dev/ttyUSB5 --baud 921600 write_flash -z --flash_mode dout 0x0 /opt/esp-open-sdk.old/esptool/tasmota32-webcam.factory.bin -fm dout Leaving... But returning to Minicom - still nothing. So doughterboard seems to work. But something does not. Any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 10 replies
-
|
For ESP32, you should use current esptool.py, v2.3.1 is ancient, but may have worked. However it saying After flashing, you should disconnect gpio0 from ground, and power cycle the device to get out of flashing mode. If everything is ok, then it should boot normally, and broadcast a Wifi AP to connect to, and of course also have a serial console available. Note that many computer USB sockets may be too low in power for ESP32 to operate reliably, especially with camera. Better to use a stronger power supply, at least 1A of 5V. BTW: My experience with those cheap ESP32-CAM modules is that quality may be "varying", to put it nicely. |
Beta Was this translation helpful? Give feedback.
-
|
What I meant by "dropping" was not related to ESP-IDF, but about getting a current esptool.py where version 4.0.1 was released a short time ago. The Jason2866 fork of ESP-IDF is not so much meant to be used outside of Tasmota, more to have a stable and tested version "confirmed" to work well with Tasmota. AFAIK the main difference is selection of which patches to avoid, and which to integrate "ahead of time". But to be clear, I was in no way making a suggestion of even considering picking a different ESP-IDF. Since you asked about ESP-IDF, I answered, without any assumptions about why you suddenly asked about something unrelated. |
Beta Was this translation helpful? Give feedback.
-
|
esptool.py is a part of ESP-IDF? Isn't it? BTW, I really appreciate Your work with Tasmota. This leaves me free (no need to deevelop own firmmware) to work :) |
Beta Was this translation helpful? Give feedback.
-
|
No, esptool.py is a narrow tool specifically for flashing (I provided a link), while ESP-IDF is a much broader development framework, basically for producing the firmware to be flashed. From the docs for ESP-IDF:
Hence esptool.py is not part of ESP-IDF, but expected to be used by the developer after the build finished. I'd not be surprised if both tools are often installed at the same time, without the user doing a separate install of esptool.py, but that's just my speculation. For context: ESP-IDF is for ESP32 chips, while RTOS SDK is their framework for ESP8266. And |
Beta Was this translation helpful? Give feedback.
-
|
Ok: 2 next tests:
Same result. Except ESP chip identified. Ask on Espressif forum? Maybe there is someone knowing essptool.py internals? |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried the official Tasmota's web-installer for ESP32CAM that is at https://tasmota.github.io/docs/Getting-Started/ ? If I were you, I will start there since the web-installer takes care of all files and flashing process. And if that works, then you can move to esptool.py, if you really want to use it. The ESP32CAM is a very cheap hardware with poor design but it works fine. I use several of those and the unique problem I had was when the power supply broke down after 2 years of installed and burnt the cam's chip due to overvoltage. The ESP32CAM gets hot very fast, but with proper ventilation it has no problems. For latest ones I flashed last month, I used the web-installer and it worked just fine. No need to worry about the files nor the esptool.py. |
Beta Was this translation helpful? Give feedback.
-
|
Finally GOT IT:
Question [OT] - why firmware allways tries to init camera? Even if board type is set to ESP32-DevKitC? Should I reflash to "regular" Tasmota32 (if no plans to use camera on one of modules, but want I2C, ADS1115 and INA226 - for the last one I think I'll have to compile my own like for ESP8266?) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, if you do not want to use the camera, better upgrade to regular tasmota32.bin which includes a lot of sensor support already. If the camera is not connected, I'd expect no restrictions on what pins you can use, unless you intend to use the SD card, of course. The onboard LED is connected to gpio 4. |
Beta Was this translation helpful? Give feedback.
-
|
Default built-in template should be: |
Beta Was this translation helpful? Give feedback.
-
|
Found this in Google while trying to resolve the same issue, so describe my solution if anyone else need a help. Well, I spent a lot of time to flash my ESP32-CAM, and finnaly I found the only working solution. The main idea: are you sure your board is in bootload state? :-) That is not enough to ground GPIO0 and power up the board. You need to press the small hardware button Reset on the board's chip side after power up! I just connect +5V, RX, TX and GND to my USB dongle, connect GPIO0 to GND, plug into USB port and press Reset button. Now it runs the bootloader and ready to be flasshed even through browser! |
Beta Was this translation helpful? Give feedback.
Finally GOT IT:
Anyway have 2 modules with Tasmota32-webcam.factory.bin flashed. On one module it seems camera went dead, but this is not a problem.
Question [OT] - why firmware allways tries to init camera? Even if board type is set to ESP32-DevKitC? Should I reflash to "regular" Tasmota32 (if no plans to use camera on one of modules, but want I2C, ADS1115 and INA226 - for the last one I think I'll have to compile my own like for ESP8266?)
Where to find which pins I have free to use on WebCAM module (camera removed)?