j-trace pro not recognized on usb

[wolpi]

Hello,

I tried to put in the known values,

<ProgrammingInterface>
<ID>jtrace</ID>
<Name>Segger J-Trace</Name>
<Identities>
<UsbIdentity>
<VID>1366</VID>
<PID>1020</PID>
</UsbIdentity>
</Identities>
<UniversalDriverId>com.sysprogs.libusb.mini</UniversalDriverId>
<AutoSelectPriority>0</AutoSelectPriority>
</ProgrammingInterface>

now you can choose it, but the test still fails:

C:\Users\bodo\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 53245” -c “telnet_port 53246” -f interface/jlink.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.9.0 (2019-01-11)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 3000 kHz
Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
esp32 interrupt mask on
VisualGDB_OpenOCD_Ready
Info : No device selected, using first device.
Error: No J-Link device found.

Do I have to change the script?

where do I find it?

 

[support]

Thanks for the update. Unfortunately this one is tougher. It looks like OpenOCD does not know how to interface with the J-Trace version you have. Given that it uses a different driver with the regular Segger setup, it might not be backward-compatible (and hence compatible with OpenOCD) at all. You could try hacking our OpenOCD port to update the J-Link USB IDs, however this may not work if the internal protocol is different.

As a quicker solution, please consider getting an FT2232-based debug probe (e.g. Olimex ARM-USB-OCD-H). Since ESP32 relies on OpenOCD anyway, there will be no usability difference between the more expensive J-Link probe and a cheaper FT2232-based one when debugging ESP32 devices.

[Author]

Posts