NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
tsal_ has quit [Ping timeout: 246 seconds]
tsal has joined #openocd
gpol has joined #openocd
stefanct__ has joined #openocd
stefanct has quit [Ping timeout: 252 seconds]
stefanct__ is now known as stefanct
rixzo has joined #openocd
<rixzo> Hi!
rixzo has quit [Client Quit]
nerozero has joined #openocd
Hawk777 has quit [Quit: Leaving.]
Haohmaru has joined #openocd
nerozero has quit [Ping timeout: 272 seconds]
nerozero has joined #openocd
Haohmaru has quit [Quit: saionara]
nerozero has quit [Ping timeout: 246 seconds]
van has quit [Quit: WeeChat 4.2.1]
van has joined #openocd
joconor has quit [Quit: ZNC 1.8.2 - https://znc.in]
joconor has joined #openocd
balrog_ has quit [Ping timeout: 260 seconds]
balrog has joined #openocd
greyltc has joined #openocd
<greyltc> Hi, does will OpenOCD work with this tool? https://www.segger.com/products/debug-probes/j-link/models/j-link-pro-poe/
<greyltc> J-Link PRO PoE
<PaulFertser> greyltc: it probably should
<greyltc> i agree!
<greyltc> are there any known supported Ethernet-based adapters?
<PaulFertser> greyltc: I think jlink is the only one, and you can check libjaylink source and git log to see more about that.
<PaulFertser> greyltc: in general it's easy to add an SBC to a USB adapter and run OpenOCD on that SBC, and you get an Ethernet adapter :)
<karlp> ^^
<greyltc> i'll give it a whirl
<PaulFertser> greyltc: do you already have that adapter?
<greyltc> PaulFertser: no, i'm about to buy one though
<PaulFertser> greyltc: can't promise it's going to work with OpenOCD.
<zapb__> greyltc, the only limitation at the moment is that the device must be discoverable
<zapb__> greyltc, I have working J-Link setups over Ethernet
<greyltc> zapb__: discoverable? how so?
<greyltc> like avahi - mDNS/DNS-SD?
<zapb__> greyltc, UDP broadcast
<greyltc> can't you just tell OpenOCD its IP address?
<zapb__> greyltc, unfortunately not, that's not an issue with OpenOCD but how libjaylink handels device at the moment
<zapb__> greyltc, is this a limitation for you with your setup?
<greyltc> no
<greyltc> UDP broadcast should be no issue
<zapb__> greyltc, nice, I'm glad to hear that. I would like to have some time to improve this in libjaylink but it's not highest priority unfortunately
<greyltc> just odd since I figure all the working comms are via tcp
<zapb__> greyltc, yes, it's only that the libjaylink API design does not allow you to specify a device but you have to "discover" devices first
<zapb__> the communication is over tcp, correct
MrBIOS-_ has joined #openocd