16:03 <Guest94> Has anyone had any issues with getting openocd (0.10.0) to talk to a J-Trace Pro? I get a "No J-Link device found" even though J-Link commander can connect and talk to my target via SWD. I'm thinking it's a .cfg file issue, but I'm really new to this type of work.

16:13 <karlp> is it usb or ethernet connected?

16:14 <karlp> what's it's vid/pid?

16:23 <Guest94> USB, 1366:1020

16:31 <karlp> zapb_: that's a new usb pid?

16:32 <karlp> the 60-openocd rules file only includes up to 1018, then 1051 and 1061?

16:32 <zapb_> Hm, let me check

16:33 <karlp> hrm, it's in libjaylink file though

16:33 <karlp> Guest94: it _might_ be as simple as you don't have access to it?

16:33 <karlp> try adding a line for 1020 to your udev rules... (are you even in linux?)

16:33 <zapb_> Yep

16:33 <zapb_> Not a libjaylink issue

16:34 <karlp> sorry for bothering you, I wasns't finding the pids listed in the libjaylink at first

16:34 <zapb_> No problem :)

16:35 <karlp> (we should probably add 1020 to the rules file regardless though right?)

16:35 <Guest94> unfortunately I am under the tyranny of a windows OS.

16:35 <karlp> and 1055? that's also in the discovery_usb.c file.

16:35 <karlp> I'm afraid I pðersonally have no idea how permissions for that works on windows... or if it's even a thing

16:36 <zapb_> karlp, I'll push a patch

16:36 <zapb_> Actually we should ship the libjaylink udev rules ;)

16:36 <karlp> either way :)

16:37 <zapb_> Guest94, I'm not aware of an Windows issues

16:37 <zapb_> Guest94, do you have a different J-Link device that works?

16:38 <Guest94> Our lab ordered an older J-Link (edu version), but that won't get here for another few weeks. I have connected to openocd through a STLink-v2 and it worked swimmingly though.

16:39 <zapb_> Guest94, you could run openocd with the most verbose log output and paste in somewhere

16:40 <zapb_> maybe there is a hint

16:42 <Guest94> Let me look up the command to do that, still learning the ropes.

16:44 <zapb_> Guest94, -d4

16:44 <zapb_> openocd -d4 [...]

16:45 <Guest94> d4 didn't work but d3 did. Where should I dump the log?

16:46 <zapb_> Guest94, wait, why do you use 0.10?

16:46 <zapb_> Use the most recent version, better Git master

16:47 <zapb_> 0.10 was released 2017!

16:48 <Guest94> Haha, maybe I should update my version first before going further then

16:48 <zapb_> Yes, please :D

16:49 <Guest94> Let me get someone rq for admin rights. Is there an openocd command or do I need to do something crunchier?

21:22 <karlp> you'll probably find it "just works" with 0.11...

21:26 <orzel> Hello. On https://openocd.org/doc/html/Debug-Adapter-Hardware.html most of links for "usb ft2232" are down. Give 404, or are redirected to the main page of the site

21:28 <PaulFertser> orzel: hi

21:28 <PaulFertser> orzel: do you need a current ftdi hardware advice or probably a more generic question?

21:30 <orzel> I'm getting into openocd. I got enough hardware i guess. But those dead links, they make a bad impression, just wanted to report this.

21:32 <PaulFertser> orzel: you can help by sending a patch against doc/openocd.texi . The documentation is maintained the same way as the source code.

21:33 <orzel> Err.. sure, i guess. I've been in openocd for like 15 minutes, not feeling ready to send merge request, yet :-)

21:34 <PaulFertser> :)

21:34 <PaulFertser> In Gerrit it's called Patchsets.

22:57 <Guest94> Had to go do lab work, but I was just able to get some results now. I updated openocd, but it looks like there are some issues still. Looks like it's finding the J-Trace (VID:PID = 1366:1020) but maybe I have a problem with my target .cfg? I copied over the debug  messages https://pastebin.com/t7au1ZVG

23:13 <PaulFertser> Guest94: I'd say looks like libjaylink call just hangs

23:13 <PaulFertser> Before anything target-specific happens

23:31 <zapb_> Guest94, it stops after "Found device (...)" ?

23:36 <Guest94> yeah, that's all of it

23:46 <zapb_> That's very strange