ESP32 toolchain test failed

Sysprogs forums Forums VisualGDB ESP32 toolchain test failed


This topic contains 7 replies, has 3 voices, and was last updated by  esp32dude 3 years, 7 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
  • #27821


    When I try to creat a new project for ESP32, I always get an error that toolchain test failed.

    I already tried:

    • Run Visual Code as administrator
    • Delete ESP32 toolchain and re-installed it
    • Delete ESP32 toolchain and manually re-installed it via

    Here is the error log

    VisualGDB version:
    —————— jf2+f ——————
    jf2+f: Failed to start process (C:\SysGCC\esp32\opt\xtensa-esp32-elf\bin\make.exe -v): The system cannot find the file specified —> System.ComponentModel.Win32Exception: The system cannot find the file specified
    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at jf2.m()
    — End of inner exception stack trace —
    at jf2.m()
    at uh.v(ue2 b, String d, String a, String e, ExpandedEnvironment f, CommandFlags c)
    at d82.b2(String d, String e, String g, ModifiedEnvirionment c, t51 b, Int32 f, CommandFlags a)
    at p72.e(d82 b, String f, ModifiedEnvirionment e, Regex i, Regex c, Int32 d, t51 a, Boolean g, String h)
    at p72.c(d82 d, String b, ModifiedEnvirionment e, t51 a, Boolean c)
    at vh.n(wv1 a, Dictionary2 b)
    at gp1.k(wv1 a)
    at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass2_2
    —————— Inner exception ——————
    —————— System.ComponentModel.Win32Exception ——————
    System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at jf2.m()




    Please make sure you use the Advanced ESP-IDF Project Wizard instead of the regular Embedded wizard:



    I was following this tutorial:

    There it was suggested to use Embedded wizard.

    Anyways, for ESP-IDF wizard, I cannot connect to ESP32 over J-Link. I checked the pinning, it is correct.

    Here is the error log:

    C:\Users\XXXXX\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 50443” -c “telnet_port 50444” -f interface/jlink.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “echo VisualGDB_OpenOCD_Ready”
    Open On-Chip Debugger 0.10.0 (2019-10-24)
    Licensed under GNU GPL v2
    libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
    For bug reports, read
    adapter speed: 3000 kHz
    Info : Configured 2 cores
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 50444 for telnet connections
    Error: type ‘esp32’ is missing virt2phys
    Warn : Failed to open device: LIBUSB_ERROR_NOT_SUPPORTED.
    Info : J-Link V11 compiled Aug 14 2019 16:21:09
    Info : Hardware version: 11.00
    Info : VTarget = 0.000 V
    Info : clock speed 3000 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 50443 for gdb connections
    Info : accepting ‘gdb’ connection on tcp/50443
    Error: No symbols for FreeRTOS
    Error: Target not examined yet

    Error: Target not halted
    Error: auto_probe failed
    Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use ‘gdb_memory_map disable’.
    Error: attempted ‘gdb’ connection rejected



    No problem, we have updated the ESP32-WROOM tutorial, pointing to the Advanced ESP-IDF tutorial.

    If you cannot get the wiring to work, please consider using a board that includes a ready-to-use JTAG programmer, e.g. ESP32-WROVER.



    J-Link works with dev boards like ESP32-WROVER.

    The issue is, I have a custom board and only have the JTAG interface. Maybe you can have a look at the ESP32 schematic if you see any issue?

    • This reply was modified 3 years, 7 months ago by  esp32dude.


    Sorry, we are not able to review custom projects or board schematics as a part of our product support. If you would like to have your project reviewed via our paid consulting service, please contact our sales to get a quote.



    Did you install libusb driver for your debugger



    yes I did.

    In the meantime I found out what causes my issue:

    1. I forgot a decoupling cap at the ESP32 3.3V pin.
    2. The JTAG mini 10 pole cable/connector is a little bit unstable it seems.

    Now, sometimes the upload works, sometimes it does not. Not sure if OpenGDB combined with a non natively supported J-Link also add to this unstable behavior.


    • This reply was modified 3 years, 7 months ago by  esp32dude.
Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.