[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?

 

[wolpi]

Hi,

I tried that, but it also gives me an “Access denied”.

Also to mention that the tool versions displayed differ from the ones on your webpage.

Regards

Bodo

Attachments:

You must be logged in to view attached files.

[wolpi]

Hi,

sorry to reopen this issue again …

but I just tried to debug an Arduino esp32 with the j-trace debugger, but it does not show up as an usb debugger in the VisualGDB settings ..

Same problem as we had above, but now with Arduino as project configuration.

Another xml to edit?? 🙂

Regards

Bodo

 

[wolpi]

Hi,

good news, I found the mistake!

USB\VID_1366&PID_1020

I corrected it in the first try, but forgot to do it in the second.

now everything is working smoothly with j-trace!

here is the code:

		<ProgrammingInterface>
		  <ID>com.sysprogs.debug.jlink.jtrace</ID>
		  <Name>Segger J-Trace</Name>
		  <Identities>
			<UsbIdentity>
			  <VID>1366</VID>
			  <PID>1020</PID>
			</UsbIdentity>
		  </Identities>
		</ProgrammingInterface>

Thanks for the fast help!

Regards

Bodo

[wolpi]

Hi,

we are getting nearer …

1. it’s listed, but as unavailable
2. there is still an error message when I start debugging

If I ignore it, debugging starts.

 

btw, I added the missing </Identities> tag ….

Attachments:

You must be logged in to view attached files.

[wolpi]

Here are some more hints:

Unlike j-link, the driver for j-trace is not the native segger driver, but the Microsoft WinUsb driver.

it’s listed in JLink.inf:

; 0x1020: J_LINK_WINUSB_DRV

so no J_LINK_SEGGER_DRV is loaded here.

I’m using: J-trace pro V2 Cortex (https://www.segger.com/products/debug-probes/j-trace/models/j-trace-cortex-arm/)

Current SW: 6.41a

I wish everybody a happy new Year!

Attachments:

You must be logged in to view attached files.

[wolpi]

Hello,

thanks for the quick reply in the middle of holiday season!

hope u had a nice X-mas!

The j-trace is now listed in the usb devices (as j-link).

Unfortunately it seems, segger has changed the complete interface structure.

The driver for the j-trace is listed in the USB devices, but starting the debugger gives the following error messages (see attachment).

Interesting enough, after it, the debug session starts normally.

Attachments:

You must be logged in to view attached files.

[wolpi]

Hi,

In the screenshot i had plugged in both.

for j-Trace I got the following ID’s:

USB\VID_1366&PID_1020&REV_0100

USB\VID_1366&PID_1020

Interesting enough, the j-link is listed under Universal Serial Bus controllers, while j-Trace is listed under  Universal Serial Bus devices.

Regards

Bodo

[wolpi]

Hello,

thanks for the hint, it did the trick half way!

Now I can enable real-time tracing and everything on that side is working fine.

But still it does not recognise the j-trace as a valid debugger on usb (see attached picture)

(also it can use it by selecting it after debug start!)

It’s good to go for me now, I will buy VisualGDB!

If I can help fix the last issue, please let me know.

Thanks for the fast support and everybody a happy new Year!

Bodo

 

Attachments:

You must be logged in to view attached files.

[Author]

Posts