I plugged the ESP32 in first. The light lit before I powered the Prog.
That looks good except for as I said, you shouldn’t try to power the ESP32 via the ESP-PROG, so not conenction between VDD (1) and 3V3.
I’ve also seen issues regarding internally broken wires many times.
And per this “Unload driver in Windows” youi’ve loaded WinUSB drivers fro “(Interface 0)”, not another one, right?
I checked and checked, and there were three wires when I pulled out the red and the black wires. Pin 14 was missing this time.
Bottom half of the output:
DEPRECATED! use 'adapter speed' not 'adapter_khz'
.xt.prop._ZNSs4_Rep10_M_disposeERKSaIcE
48 0
adapter speed: 500 kHz
.xt.prop._ZNSsD5Ev
0 0
.xt.prop._ZNSs12_S_constructIPKcEEPcT_S3_RKSaIcESt20forward_iterator_tag
84 0
.xt.prop._ZNSsC5EPKcRKSaIcE
0 0
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
.xt.prop._ZNSsD2Ev
36 0
Info : clock speed 500 kHz
.xt.prop._ZNSsC2EPKcRKSaIcE
36 0
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
.xt.prop._ZNSs4_Rep20_S_empty_rep_storageE
12 0
Error: Trying to use configured scan chain anyway...
.xt.lit._ZN2fs4File9readBytesEPcj
0 0
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
.xt.prop._ZN2fs4File9readBytesEPcj
36 0
Warn : Bypassing JTAG setup events due to errors
.xt.prop._ZTVN2fs4FileE
12 0
Warn : target esp32.cpu0 examination failed
.xt.lit._ZNKSt8functionIFvPvP11AsyncClientEEclES0_S2_
0 0
Warn : target esp32.cpu1 examination failed
Info : starting gdb server for esp32.cpu0 on 3333.xt.lit._ZNSt8functionIFvPvP11AsyncClientEEaSERKS4_
8 0
Info : Listening on port 333
3 .xt.prop._ZNKSt8functionIFvPvP11AsyncClientEEclES0_S2_
48 0
fo
r g.xt.prop._ZNSt8functionIFvPvP11AsyncClientEEaSERKS4_
72 0
db
c.debug_frame
139824 0
on
ne.debug_info
5893053 0
ct
io.debug_abbrev
476805 0
ns
Error: JTAG scan chain interrogation failed: all ones
.debug_loc
1056367 0
Error: Check JTAG interface, timings, target power, etc.
.debug_aranges
53488 0
Error: Trying to use configured scan chain anyway...
.debug_ranges
141520 0
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
.debug_line
2373771 0
Info : esp32.cpu0: Debug controller was reset.
.debug_str
596626 0
Info : esp32.cpu0: Core was reset.
Total
11555823
<lambda>(["upload"], [".pio\build\esp32dev\firmware.bin"])
AVAILABLE: cmsis-dap, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esp-prog
openocd -d2 -s C:/Users/joema/.platformio/packages/tool-openocd-esp32/share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg -c "adapter_khz 500" -c "program_esp {{.pio\build\esp32dev\firmware.bin}} 0x10000 verify" -c "program_esp {{C:/Users/joema/.platformio/packages/framework-Error: Couldn't halt target before SoC reset
arembedded:startup.tcl:1162: Error: ** Unable to reset target **
duiin procedure 'program_esp'
noein procedure 'program_error' called at file "C:/Users/joema/.platformio/packages/tool-openocd-esp32/share/openocd/scripts/target/esp_common.cfg", line 93
sprat file "embedded:startup.tcl", line 1162
essif32/tools/sdk/esp32/bin/bootloader_dio_40m.bin}} 0x1000 verify*** [upload] Error 1
" -c "program_esp {{C:/Users/joema/Documents/PlatformIO/Projects/Phoenix_Dashboard_Receiver/.pio/build/esp32dev/partitions.bin}} 0x8000 verify" -c "program_esp {{C:/Users/joema/.platformio/packages/framework-arduinoespressif32/tools/partitions/boot_app0.bin}} 0xe000 verify" -c "reset run; shutdown"
============================= [FAILED]
and
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
.xt.prop._ZNSs4_Rep20_S_empty_rep_storageE
12 0Hello, I had a massive headache with ESP-Prog, at the moment I am using it with visual micro in debugging mode, still the best way to debug esp is still with Serial.prinln() for me
To make it work you can have a look at their guide and at my issue.
Video guide:
Issue solved
With PlatformIO I quit.