It's not a complete IDE so it's not as heavy as other Microsoft products such as Visual Studio Professional. Visual Studio Code is an open source editor that's already in the market and already being used for many developers from NodeJS to Python projects. Remember - If you have installed a new driver, you may have to do it again if you connect the debugger to a different USB port next time.Arduino IDE is a great tool, but if you need to use Arduino more than just blinking LEDs, you most probably will need a better editor that supports intellisense. You may need to install an additional USB Driver on Interface 0 of your debugger to allow it to function with this software - check in the debugger list here

NOTE - The vMicro > Debugger > Compiler Optimization MUST be set to 'No Optimization' for this board to function with the debugger Open your Sketch and select the Debug > Hardware, and the relevant Debugger you have available There is also a video guide to the software and driver setup described belowĮnsure you have Visual Studio and the vMicro Extension Installed Then you will also need to connect your Debugger to the PC on one USB port, and the ESP32 on another USB Port NOTE: Pinouts for connections differ between boards - See Images & Links To connect your JTAG debugger to the ESP32 board you will need to connect the below pins:ĮSPPROG Connected to ESP32 Wiring Diagram Wiring Diagram (+Serial)į2232H Dual Connected to ESP32 Wiring Diagram Wiring Diagram (+Serial)ĮSP Devkit to External ESP32 Wiring Diagram NOTE: If using External JTAG debugging any SDCard functionality will need to be removed as this conflicts with the JTAG pin assignments.Īll boards support the vMicro Software Debugger which only requires the Serial interface to work To see a list of all debuggers currently supported within vMicro please click here. If you are using 'Upload via Programmer', ensure you do not use v2.0.4 as this has an issue with bootloaders.

Roll Back to v2.0.0 to ensure this is reliable, or use v2.0.3 onwards which have the issue resolved. If you are using ESP32 Core v2.0.1 or 2.0.2 there is an issue with the GDB.exe reported here.

Esp32 visual studio code