08:32 <dormito> Hmmm. Is there a way to run the openocd's gdb server on a specific IP (instead of local host), hopefully including ipv6 addresses?

08:39 <PaulFertser> dormito: there's "bindto" but IPv6 is not supported unfortunately.

08:41 <PaulFertser> I was working on it back then https://review.openocd.org/c/openocd/+/1939 but couldn't manage to finish

08:42 <dormito> PaulFertser: thanks. nice that someone was working on it. I have only poked a round a tiny bit in openocd, but assuming it uses standard(ish) libc calls, moving to ipv6 shouldn't be to hard.... (famous last works probably, espcially since it seems there was trouble.)

08:43 <PaulFertser> dormito: yes, the previous patch did just that.

10:22 <dormito> I'm looking at the a 2020 era i.mx rt 1170 evk gerrit patch set. And I notice that it's calling "dap create [elided] -chain-position $chip_name.cpu". I get an error messages about -chain-posiition being invalid. I'm still rather new to the debug terminology, but I think chain position is the index (numerical) in the scan chain? Is there any thing I can read up on to get a better grasp of the

10:22 <dormito> terminology?

10:29 <PaulFertser> dormito: I think it's the name of the tap, not number.

10:30 <dormito> ah, yeah. had a typo that cause the dap name to be wrong

11:14 <dormito> Hmmm. Is there a way to tell openocd to issue a reset? I requested a bus address that was invalid (backing IP block probably was unconfigured), which seems to have stalled the DP. so openocd fails to connect. The board has an on-board CMSIS/opensda adaptor (how I am conenctect), and I can see from the schematics that the opensda chip should be able to control the reset line, but I've not figured

11:14 <dormito> out how to get openocd to issue the cmd. I see several reset related cmds, but none look quite correct.

11:19 <PaulFertser> dormito: what do you mean with "reset" exactly?

11:22 <dormito> in this case, I think it will trigger a power on reset of the chip being debugged. I can see a "jtag_reset" signal that comes out of the opensda chip, goes throw what looks like an electrical isolation, and then goes to the micros POR signal. (not really sure why they called it "jtag_reset" since the procotol used defaults to swd ... oh well)

11:27 <PaulFertser> dormito: if you want to use additional hardware reset line, connect it and enable with "reset_config srst_only", then "reset" command will start using it.

11:34 <dormito> thanks. openocd seems to accept that, but somethings still wrong (and sadly my time with is up for now). Thanks a lot for the help