00:06 <zapb_> karlp, how could we make swo easier to use? :)

00:06 <zapb_> more default configs?

01:25 <c4017w__> I'm using cross-build.sh. I want to use -O0 temporarily, but unsure how to add just that one flag. I tried `export CFLAGS="-O0"` before running the script, but it appears to remove other cflags (specifically '-g'). It's not a big deal as I can just do `export CFLAGS="-g -O0"`, but I'm wondering if there's a way to add a flag without the others being removed?

10:10 <jancoow> Mmh okay so. I start openOCD as a subprocess in my python code and connect to the 6666 port. However, after 18~20 minutes, openOCD does not give a response to my command on this port. The code does restart the process then and it works, but I was wondering why this is happening

10:11 <jancoow> maybe the python process is not kept alive or something?>

11:22 <zapb_> jancoow, I never had problems like that and I use Python + OpenOCD a lot

11:22 <zapb_> jancoow, can you provide more information?

12:02 <jancoow> zapb_ unfortunally, no. I can ony see my own python logging so I am limited to that. The only thing I see is that I'm trying to send a command, and that command timed out because I dont receive a response

12:03 <jancoow> I was wondering if it was any openocd specific so ye

15:08 <karlp> zapb_: openocd not an awful lot, but yes, having easier defaults that can be found and turned on would be great. probe-rs expanded their scope a bit to include trace, and integrates a few things a little neater, so it's "discoverable" somewhat.

15:09 <karlp> it's kinda ecosystem as a whole expanding trace usage.

15:09 <karlp> many of the rust demos use swo ch0 printf just out of the box, so people see it and start to remember it exists.

15:10 <karlp> st cube for isntance it's kinda awkward to use it, even if you know what you're doing.

15:10 <karlp> even though _all_ demo boards have swo connected to the stlinks.

16:33 <zapb_> karlp, yes, I tried swo/tpiu today

16:33 <zapb_> Actually it was a pita

16:33 <zapb_> Even if you're familiar with OpenOCD

16:53 <zapb_> jancoow, what target? is openocd responsive via telnet?

18:54 <jancoow> zapb_ im not sure; it's hard for me to debug

21:27 <karlp> bleh, riscv-openocd fork works, openocd plus https://review.openocd.org/c/openocd/+/6704 fails, but... opening the cmsis-dap?! not what I expected... https://paste.jvnv.net/view/8BI20

21:27 <karlp> was expecting changes in teh gd32v bits, not the cmsis-dap bits :|

21:29 <karlp> $ src/openocd -s tcl -f interface/cmsis-dap.cfg -c "adapter speed 2000" -f target/gd32vf103.cfg -d2

21:29 <karlp> huh, adding adapater speed manually works?!

21:29 <karlp> that... can't be the intended behaviour of cmsis-dap right?

21:29 <karlp> is that a bug in some cmsis-dap refactoring we did?

21:32 <karlp> wow, no, andreas complained about in.... 2016.... https://sourceforge.net/p/openocd/mailman/openocd-devel/thread/1354fef1-849f-856c-6001-0b5ff35aa690%40suse.de/

21:35 <karlp> well, great, even with that, now it _claims_ to have flashed things, but doesn't...

21:35 <karlp> ok, this needs more debugging and testing behviious than I have time for tonight :|