Problems programming an ESP32-S3 chip.
Posted: Thu Dec 19, 2024 8:56 pm
Hi,
When I try to program an ESP32-S3 that is in a custom design I made, consisting of 2 ESP32-S3s together, the device manager detects the COM port where the ESP is connected. However, when I go to upload the program using Arduino IDE, a message appears indicating that the port does not exist.
Trying to solve the problem, I saw that the probe I use, ESP-PROG, has the RX LED blinking constantly. When I observed the TX signal from the ESP32, I got the following signal
Then I opened a port using Hercules and managed to connect, and I could see that the ESP32 sends many reboot messages for no apparent reason.
Then I measured the voltage on IO0 of the ESP32 and it had a value of approximately 4V. Additionally, I saw the CHIP_PU signal and it was permanently at 3.2V, which is correct and should not cause a reboot
What could be happening? I have attached some PCB design photos of the small module. Additionally, the two ESP32-S3s are covered by a single protective shield
The strangest thing about all this is that I had previously uploaded blank programs to that ESP32 without any problems.
When I try to program an ESP32-S3 that is in a custom design I made, consisting of 2 ESP32-S3s together, the device manager detects the COM port where the ESP is connected. However, when I go to upload the program using Arduino IDE, a message appears indicating that the port does not exist.
Trying to solve the problem, I saw that the probe I use, ESP-PROG, has the RX LED blinking constantly. When I observed the TX signal from the ESP32, I got the following signal
Then I opened a port using Hercules and managed to connect, and I could see that the ESP32 sends many reboot messages for no apparent reason.
Then I measured the voltage on IO0 of the ESP32 and it had a value of approximately 4V. Additionally, I saw the CHIP_PU signal and it was permanently at 3.2V, which is correct and should not cause a reboot
What could be happening? I have attached some PCB design photos of the small module. Additionally, the two ESP32-S3s are covered by a single protective shield
The strangest thing about all this is that I had previously uploaded blank programs to that ESP32 without any problems.