NODEMCU J-Link Debugging error

[Yuex.S]

<span id=”noHighlight_0.8454378732699729″>1, the software does not recognize my Jlink, modify C:\SysGCC\esp8266\esp8266-bsp\sysprogs\debug\core\QuickSetup\interfaces.xml content</span>

 

<ProgrammingInterface>
<ID>jlink</ID>
<Name>Segger J-Link</Name>
<ScriptFile>interface/jlink.cfg</ScriptFile>
<UsbIdentities>
<UsbIdentity>
<VID>1366</VID>
<PID>0101</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0102</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0103</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0104</PID>
</UsbIdentity>

<span id=”noHighlight_0.6847605044472554″>Here is a new</span>
            <UsbIdentity>
                <VID>1366</VID>
                <PID>0105</PID>
            </UsbIdentity>
        </UsbIdentities>
<UniversalDriverId>com.sysprogs.libusb.mini</UniversalDriverId>
</ProgrammingInterface>

<span id=”noHighlight_0.6304524722850114″>Can be identified after an increase, but debugging is always wrong。</span>

Open On-Chip Debugger 0.9.0 (2015-11-04-20:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
stop_wdt
adapter speed: 3000 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : J-Link V9 compiled Jun 16 2017 16:15:10
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 94000
Info : J-Link hw type J-Link
Info : J-Link max mem block 69848
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0xffffffff
Info : Vref = 3.296 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 1 TRST = 0
Info : J-Link JTAG Interface ready
Info : clock speed 3000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: esp8266.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Warning: Target not halted, breakpoint/watchpoint state may be unpredictable.
target state: halted
Info : halted: PC: 0x0
Info : debug cause: 0x0
Info : accepting ‘gdb’ connection on tcp/3333
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: esp8266.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
target state: halted
Info : halted: PC: 0x0
Info : debug cause: 0x0
Warn : xtensa_deassert_reset: ‘reset halt’ is not supported for Xtensa. Have halted some time after resetting (not the same thing!)
Warn : Cannot set a software breakpoint at 0x4010008c. Trying a hardware one instead…

<span id=”noHighlight_0.11851064176018544″>I refer to this link wiring</span>

https://visualgdb.com/tutorials/esp8266/nodemcu/jtag/。

 

[Yuex.S]

<ProgrammingInterface>
<ID>jlink</ID>
<Name>Segger J-Link</Name>
<ScriptFile>interface/jlink.cfg</ScriptFile>
<UsbIdentities>
<UsbIdentity>
<VID>1366</VID>
<PID>0101</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0102</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0103</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0104</PID>
</UsbIdentity>
<UsbIdentity>
<VID>1366</VID>
<PID>0105</PID>
<Interface>02</Interface>
</UsbIdentity>
</UsbIdentities>
<UniversalDriverId>com.sysprogs.libusb.mini</UniversalDriverId>
</ProgrammingInterface>

• This reply was modified 6 years, 10 months ago by Yuex.S.

[support]

Hi,

The “Error: JTAG scan chain interrogation failed: all zeroes” error almost always means wiring issues. Please double-check your connection, ensure no other peripherals share the JTAG lines. If nothing helps, please try using a logic analyzer to see if there is any JTAG activity on the corresponding pins.

[Yuex.S]

Thank you very much, it has been solved, it is JTAG connection line fault

• This reply was modified 6 years, 10 months ago by Yuex.S.

[Yuex.S]

Segger J-Link V9 Version
Hardware ID is VID：1366，PID：0105

I was manually modified to use the
Want to add to the hardware identification, now unrecognized
Thank you so much！

[support]

Hi,

You can do this by editing the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\QuickSetup\interfaces.xml file.

[Author]

Posts