j-trace pro not recognized on usb

[wolpi]

Hello,

I tried with V5.3 and 3.4p1:

I have j-link and a j-trace (connected via usb)

In the Debug settings, the j-link is recognised w/o problems under “Debug using”.

The j-trace does not show up.

On debug start, the j-trace can be choosen for debugging.

But j-trace features are not available (in 5.4p1).

Any ideas?

Regards

Bodo

Operating system is Windows10, Visual Studio 2017

[support]

Hi,

Please try updating the Segger debug plugin via Tools->VisualGDB->Manage VisualGDB Packages.

If this doesn’t help, please attach a screenshot of the settings page with the missing settings.

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

[support]

Hi,

Sorry for the confusion. The screenshot looks like J-Trace is actually recognized (it is shown as J-Link due to backward compatibility). Do you mean that you would expect it to be shown as “J-Trace”, not “J-Link”, or do you have both J-Trace and J-Link plugged in at the same time? In the latter case, what is the USB VID/PID of J-Trace?

[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

[support]

Hi,

Thanks for checking this. It indeed looks like your J-Trace is using a USB ID that is not listed in the regular J-Link driver files and hence not being recognized by VisualGDB.

You can work around this by adding the following entry to %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp\edp.xml:
<UsbIdentity>
  <VID>1366</VID>
  <PID>0120</PID>
</UsbIdentity>

Let us know if this works and we will update the file on our end.

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

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.

[support]

Hi,

Happy New Year!

Thanks for the update. This indeed looks different from the J-Trace PRO unit we used to do our tests. Please try adding a separate ProgrammingInterface element for the J-Trace:

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

This will let VisualGDB use the existing USB driver instead of trying to install the regular Segger driver.

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

[support]

Hi,

Looks like your project properties still references the old device type (requiring the Segger driver). Please try reselecting the debug interface via Debug Settings (or creating a new project).

[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

[support]

Hi,

Thanks for confirming this. We will include the new device ID in the next release of our debug package for J-Link/J-Trace.

[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

 

[support]

Hi,

Yes, the ESP8266/ESP32 devices use a separate debug method package (%LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core). Also as the Segger GDB stub does not support the ESP8266 and ESP32 devices, they use OpenOCD that only works with the WinUSB driver. Please try adjusting the edp.xml and QuickSetup\interfaces.xml files to reflect your device ID. Feel free to post the necessary modifications here and we will update our packages accordingly.

[Author]

Posts