Sep 11th, 2026 at 12:41pm (UTC)
 
 

Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
  		Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
  VS Arduino › › › ESP-WROVER-KIT and Debugging
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: [1] 2  Send TopicPrint
Locked Topic ESP-WROVER-KIT and Debugging (Read 19141 times)
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
ESP-WROVER-KIT and Debugging
Jul 28th, 2019 at 8:12am
 
Hello the ESP-WROVER-KIT supports FTDI Debugging. Is there any support vMicro ??
https://www.visualmicro.com/page/ESP32-Debugging.aspx
I don't see the Menu Debug Hardware. Do I have to install an extra Addon ?
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #1 - Jul 28th, 2019 at 9:39am
 
The image you posted if of the tool bar which you might not have visible. Did you look on the vMicro>Debugger menu?

Always best to post the info requested in the yellow box then we don't have to check your verion numbers etc.?

Which version of Visual Micro are you using? see "extensions and updates>installed>arduino ide for vs"


note: the debug menu has been in visual micro since it's release over the past month. There is an update about to be released with fixes for the WROVER debug. This has nothing to do with your being able to see the debugger.s menus. The update is already available in the releases section of this forum.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #2 - Jul 28th, 2019 at 12:35pm
 
Oh Sure Sorry
I use to have Ver 1903.16.0 and updated it to 
Ver 1907.25.0
I was unable to install Ver. 1907.26.2 for Studio 2019
I got this 
Code
Select All
Program ESP32_SSID_Table size: 665.898 bytes (used 34% of a 1.966.080 byte maximum) (5,15 secs)
Minimum Memory Usage: 39620 bytes (12% of a 327680 byte maximum)

# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination:

Uploading 'ESP32_SSID_Table' to 'ESP32 Dev Module' using 'F2232H Dual RS232'
« Last Edit: Jul 28th, 2019 at 1:04pm by Tim@Visual Micro »  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #3 - Jul 28th, 2019 at 1:07pm
 
Thanks for the note about the vs2019 install. The latest release has been updated.

I see you have enabled the programmer option, you certainly need the latest release for that but you do not need it to test debug. The choice of debugger and choice of programmer are seperate.

It's important also to be clear about the hardware (debugger/programmer) you actually have.

When we have a working config all tools should automatically be available or automatically download.


« Last Edit: Jul 28th, 2019 at 1:48pm by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #4 - Jul 29th, 2019 at 4:43am
 
If I try to downlad the latest Version 
from this site
https://www.visualmicro.com/page/Arduino-Visual-Studio-Downloads.aspx
I get this
rror>
<Code>BlobNotFound</Code>
<Message>
The specified blob does not exist. RequestId:88e131ed-001e-0037-41c7-45653f000000 Time:2019-07-29T04:40:51.0121216Z
</Message>
</Error>
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #5 - Jul 29th, 2019 at 9:57am
 
I forgot to point out that new releases go into this forum before being published to the gallery. https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Gallery

Yes microsoft have a gallery issue at the moment. When we make the next upload it might fix it. However installing from inside the ide using "extensions and updates" works.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #6 - Jul 29th, 2019 at 12:17pm
 
Thank you I installed Ver 1907/28/0
Still the same 

Info : Configured 2 cores
esp32 interrupt mask on
****[vMicro]**** Uploading App :Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error during upload using programmer
The uploader process failed

The uploader process failed
The uploader returned an error
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination: 

I put Jumpers an TCK TDI TDO TWS 
Any other clue !!!
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #7 - Jul 29th, 2019 at 1:05pm
 
There is a new config file missing from the install. The debug team will give you some workaround later today.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #8 - Jul 29th, 2019 at 1:50pm
 
Sound fair for me Thank you I looking forward
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: ESP-WROVER-KIT and Debugging
Reply #9 - Jul 29th, 2019 at 2:53pm
 
Could you try adding a local board.txt to the project and add the below lines (For the Dual RS232H Debugger):

Code
Select All
tools.openocd.debug.openocdscript=esp32-wrover.cfg
tools.f2232h.server.build.openocddebugger=ftdi/esp32_devkitj_v1.cfg


Then try attaching the debugger again, and it should attach correctly.

Further configuration may be needed to get the upload to work via the programmer (again add into local boards.txt):-

Code
Select All
tools.openocd.program.pattern="{program.path}/{program.cmd}" {program.verbose} -s "{program.path}/share/openocd/scripts/" -f "interface/ftdi/esp32_devkitj_v1.cfg" -f "board/{upload.openocdscript}" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {{runtime.platform.path}/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program }.bin} 0x1000"  -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program {{build.path}/{build.project_name}.bin} 0x10000"  -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program {{build.path}/{build.project_name}.partitions.bin} 0x8000 reset; shutdown"
tools.openocd.upload.pattern="{program.path}/{program.cmd}" {program.verbose} -s "{program.path}/share/openocd/scripts/" -f "interface/ftdi/esp32_devkitj_v1.cfg" -f "board/{upload.openocdscript}" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {{runtime.platform.path}/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program }.bin} 0x1000"  -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program {{build.path}/{build.project_name}.bin} 0x10000"  -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program {{build.path}/{build.project_name}.partitions.bin} 0x8000 reset; shutdown"

Edit: Update to debug configuration to remove interface select

If you have any issues can you confirm the specific Devkit version you have, just in case there is another element we are missing.
« Last Edit: Jul 29th, 2019 at 3:40pm by Simon@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #10 - Jul 29th, 2019 at 7:46pm
 
First Thank you foe helping second there is no file board.txt
only boards.txt but I thing you mean platform.txt
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #11 - Jul 29th, 2019 at 7:57pm
 
Simon was referring to the "vMicro>Add Code>Board.txt" or you can create one manually. Visual Micro supports a board.txt in the project folder with overrrides.

However since then Visual Micro 1907.29.1 has been published to the new releases section of this forum and includes the missing info. Please install and give it a try.

Thanks
« Last Edit: Jul 29th, 2019 at 8:45pm by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #12 - Jul 29th, 2019 at 8:36pm
 
###############################################
# DEBUG TOOL
###############################################
# Test VMicro
tools.openocd.debug.openocdscript=esp32-wrover.cfg
tools.f2232h.server.build.openocddebugger=ftdi/esp32_devkitj_v1.cfg 
tools.openocd.program.pattern="{program.path}/{program.cmd}" {program.verbose} -s "{program.path}/share/openocd/scripts/" -f "interface/ftd
Code
Select All
i/esp32_devkitj_v1.cfg" -f "board/{upload.openocdscript}" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {{runtime.platform.path}/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program }.bin} 0x1000"  -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program {{build.path}/{build.project_name}.bin} 0x10000"  -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program {{build.path}/{build.project_name}.partitions.bin} 0x8000 reset; shutdown"
tools.openocd.upload.pattern="{program.path}/{program.cmd}" {program.verbose} -s "{program.path}/share/openocd/scripts/" -f "interface/ftdi/esp32_devkitj_v1.cfg" -f "board/{upload.openocdscript}" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {{runtime.platform.path}/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program }.bin} 0x1000"  -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program {{build.path}/{build.project_name}.bin} 0x10000"  -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program {{build.path}/{build.project_name}.partitions.bin} 0x8000 reset; shutdown"


##### GDB with Interface Specified for custom external debuggers
tools.openocd.debug.path={runtime.tools.openocd-espressif-esp32-10.0.1.path}
tools.openocd.debug.cmd=bin/openocd
tools.openocd.debug.cmd.windows=bin/openocd.exe
tools.openocd.debug.params.verbose=-d2
tools.openocd.debug.openocdscript=esp-wroom-32.cfg
tools.openocd.debug.args={params.verbose} -l "{{build.path}/{build.project_name}_DebugOpenOCD.log}" -s "{path}/share/openocd/scripts/" -f "{path}/share/openocd/scripts/interface/{build.openocddebugger}" -c "set ESP32_RTOS none" -f "{path}/share/openocd/scripts/board/{openocdscript}" -c "init"
tools.openocd.debug.address=localhost:3333

# debug.tool=f2232mm



# ESP32 PROG (Identical to  F2232H Dual RS232)
###tools.esp32prog.server.build.openocddebugger=ftdi/minimodule-lowcost.cfg
tools.esp32prog.args=-ex "set remote hardware-watchpoint-limit 2" -ex "mon reset halt" -ex "flushregs" -ex "thb app_main" -ex "c"
tools.esp32prog.path={runtime.tools.xtensa-esp32-elf-gcc.path}/bin
tools.esp32prog.cmd=xtensa-esp32-elf-gdb.exe
tools.esp32prog.pattern="{path}/{cmd}" {args}
tools.esp32prog.server.tool=openocd

# F2232H Dual RS232
### tools.f2232h.server.build.openocddebugger=ftdi/minimodule-lowcost.cfg
tools.f2232h.args=-ex "set remote hardware-watchpoint-limit 2" -ex "mon reset halt" -ex "flushregs" -ex "thb app_main" -ex "c"
tools.f2232h.path={runtime.tools.xtensa-esp32-elf-gcc.path}/bin
tools.f2232h.cmd=xtensa-esp32-elf-gdb.exe
tools.f2232h.pattern="{path}/{cmd}" {args}
tools.f2232h.server.tool=openocd

I tried this in platform.txt but I still get

but Studio is still asking for "interface/ftdi/minimodule-lowcost.cfg"
I remarked all Textfiles where does Studio gets this message. Could you be a little bit more specific please.
« Last Edit: Jul 29th, 2019 at 8:45pm by Tim@Visual Micro »  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12210
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP-WROVER-KIT and Debugging
Reply #13 - Jul 29th, 2019 at 8:46pm
 
Please undo whatever you have changed and install the latest release which has been published to the gallery.

« Last Edit: Jul 29th, 2019 at 9:26pm by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #14 - Jul 30th, 2019 at 7:10am
 
I installed
Visual.Micro.Arduino.Studio_1907_29_3
same. I can't find the file board.txt. In what folder should it be.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: ESP-WROVER-KIT and Debugging
Reply #15 - Jul 30th, 2019 at 8:14am
 
Once you have the new one installed, you wont need the boards.txt or the lines of config supplied before as they are now built in.

Simply select the ESP32Wrover board, and the ESP32 DEVKIT Debugger / Programmer and attach / upload as before.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #16 - Jul 30th, 2019 at 11:29am
 
Code (CSS)
Select All
Uploading 'ESP32_SSID_Table' to 'ESP32 Wrover Module' using 'ESP32 DEVKIT'
Uploader started for board ESP32 Wrover Module
Uploader will use programmer name: esp32devkit
C:\ProgramData\vmicro\tools\openocd-espressif-esp32-10.0.1\bin\openocd.exe -d2 -s s/" -f "interface/ftdi/esp32_devkitj_v1.cfg.cfg" -f "board/esp-wroom-32.cfg" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {D:\Arduino.IDE\hardware\espressif\esp32/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program {D:\Arduino.IDE\hardware\espressif\esp32/tools/sdk/bin/bootloader_qio_80m.bin} 0x1000" -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program er\Debug/ESP32_SSID_Table.ino.bin} 0x10000" -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program er\Debug/ESP32_SSID_Table.ino.partitions.bin} 0x8000 reset; shutdown"
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Error during upload using programmer
The uploader process failed

The uploader process failed
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
embedded:startup.tcl:63: Error: Can't find interface/ftdi/esp32_devkitj_v1.cfg.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 63
The uploader returned an error
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination:

We are coming closer  Cheesy Cheesy
dubble Extension ????
esp32_devkitj_v1.cfg.cfg
  
Back to top
 
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #17 - Jul 30th, 2019 at 12:01pm
 
I changes in programmers.txt the line
esp32devkit.openocddebugger=ftdi/esp32_devkitj_v1.cfg.cfg to
esp32devkit.openocddebugger=ftdi/esp32_devkitj_v1.cfg
and then I get this again

Code (CSS)
Select All
Uploading 'ESP32_SSID_Table' to 'ESP32 Wrover Module' using 'ESP32 DEVKIT'
Uploader started for board ESP32 Wrover Module
Uploader will use programmer name: esp32devkit
C:\ProgramData\vmicro\tools\openocd-espressif-esp32-10.0.1\bin\openocd.exe -d2 -s s/" -f "interface/ftdi/esp32_devkitj_v1.cfg" -f "board/esp-wroom-32.cfg" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {D:\Arduino.IDE\hardware\espressif\esp32/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program {D:\Arduino.IDE\hardware\espressif\esp32/tools/sdk/bin/bootloader_qio_80m.bin} 0x1000" -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program er\Debug/ESP32_SSID_Table.ino.bin} 0x10000" -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program er\Debug/ESP32_SSID_Table.ino.partitions.bin} 0x8000 reset; shutdown"
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
none separate
adapter speed: 2000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
****[vMicro]**** Uploading App :Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error during upload using programmer
The uploader process failed

The uploader process failed
The uploader returned an error
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination:


Cry Cry Cry Cry Cry
  
Back to top
 
IP Logged
 
ZenForAll
Junior Member
**
Offline


Posts: 34
Joined: Jun 30th, 2018
Re: ESP-WROVER-KIT and Debugging
Reply #18 - Jul 30th, 2019 at 12:01pm
 
I changes in programmers.txt the line
esp32devkit.openocddebugger=ftdi/esp32_devkitj_v1.cfg.cfg to
esp32devkit.openocddebugger=ftdi/esp32_devkitj_v1.cfg
and then I get this again

Code (CSS)
Select All
Uploading 'ESP32_SSID_Table' to 'ESP32 Wrover Module' using 'ESP32 DEVKIT'
Uploader started for board ESP32 Wrover Module
Uploader will use programmer name: esp32devkit
C:\ProgramData\vmicro\tools\openocd-espressif-esp32-10.0.1\bin\openocd.exe -d2 -s s/" -f "interface/ftdi/esp32_devkitj_v1.cfg" -f "board/esp-wroom-32.cfg" -c "echo -n {****[vMicro]**** Uploading App :}" -c "telnet_port disabled; program {D:\Arduino.IDE\hardware\espressif\esp32/tools/partitions/boot_app0.bin} 0xe000" -c "echo -n {****[vMicro]**** Uploading Bootloader :}" -c "program {D:\Arduino.IDE\hardware\espressif\esp32/tools/sdk/bin/bootloader_qio_80m.bin} 0x1000" -c "echo -n {****[vMicro]**** Uploading Sketch :}" -c "program er\Debug/ESP32_SSID_Table.ino.bin} 0x10000" -c "echo -n {****[vMicro]**** Uploading Partitions :}" -c "program er\Debug/ESP32_SSID_Table.ino.partitions.bin} 0x8000 reset; shutdown"
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
none separate
adapter speed: 2000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
****[vMicro]**** Uploading App :Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error during upload using programmer
The uploader process failed

The uploader process failed
The uploader returned an error
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination:


Cry Cry Cry Cry Cry
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2962
Joined: Feb 13th, 2019
Re: ESP-WROVER-KIT and Debugging
Reply #19 - Jul 30th, 2019 at 1:26pm
 
This is still failing to connect to the ESP Chip via the debugger, but as it is built into the board its unlikely the connections between the ESP and the debugger.

Can you confirm you arent using the MicroSD Functionality, and you don't have anything attached to the below pins:
EN
GPIO15
GPIO12
GPIO13
GPIO14

Can you also confirm which version of the Wrover-Devkit board you have (is it the 4.1 board as detailed below?)

https://docs.espressif.com/projects/esp-idf/en/latest/hw-reference/get-started-w...
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
Page Index Toggle Pages: [1] 2 
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

VS Arduino » Powered by YaBB 2.6.12!
YaBB Forum Software © 2000-2026. All Rights Reserved.