Hello everyone, I have a strange error that I can’t get any further with.
For context:
I am using an esp-wroom32-ue on a custom board, with the espressif platform 6.12.0 and arduinoespressif @3.20017
I don’t have a boot button, so the ESP is brought into boot mode via DTR, which has been working for 2 years without any problems.
Now I have bought a brand new computer, when I want to install the new firmware on the ESP from this PC I get this error:
A fatal error occurred: Failed to connect to ESP32: Wrong boot mode detected (0x13)! The chip needs to be in download mode.
If I open the same software version on my old PC and upload it, it works without any problems.
However, if I only start the serial monitor on the new PC, I get the logs of the ESP without any problems, only the upload does not work.
I have reinstalled Platformio, installed the appropriate FTDI driver, made updates and tried every USB port.
Also I am using the same programmer on both devices.
Do new mainboards (Asus TUF B650E) possibly no longer supply enough power for the programmer, so that it cannot bring the ESP into boot mode?
Does anyone have any ideas what else could be the problem?
Many thanks
Daniel
Some boards need an external capacitor between EN and GND to fix some issues - See [SOLVED] Failed to connect to ESP32: Timed out waiting for packet header | Random Nerd Tutorials
I also have a board like this that works perfectly on my PC without a capacitor, but does not work on my notebook without a capacitor. So it may also be due to the combination of board and computer.
I have this capacitor inserted on my pcb, its 1nF and not 10uF, maybe its a capacity problem, but for now I dont have the possibility to change them out
Do you think using a powered USB-hub could solve the problem?
I don’t know. But it would be worth a try (if you have such a hub available).
OK, so I’ve now got the USB power hub, but it still doesn’t work.
Does anyone have any ideas what the problem could be?
I’m using these package versions
- framework-arduinoespressif32 @ 3.20017.241212+sha.dcc1105b
- tool-esptoolpy @ 2.40900.250804 (4.9.0)
- tool-mkfatfs @ 2.0.1
- tool-mklittlefs @ 1.203.210628 (2.3)
- tool-mkspiffs @ 2.230.0 (2.30)
- toolchain-xtensa-esp32 @ 12.2.0+20230208
Also the driver seems to look good:
That’s pretty frustrating. I bought the new development PC mainly for that purpose, and now the most important feature doesn’t work 
