10:04 <uuser> Hello everybody, I am new in this domain and currently using a JLink probe to access the SWD interface on a Raspberrypi Pico with openocd to extract the content of the trace buffer MTB/ETB/ETF or TMC (I think they are all the same only a different name). Therefor I use the target config rp2040.cfg and the interface config jlink.cfg. Do I have to define additional stuff in these configs to get access to this buffer? Commands to address the etb

10:04 <uuser> like etb config are not accepted by openocd in my case. I can't find any helpful documents or something to get a tip for moving on. Maybe it is not possible or I can't understand what is necessary. I would appreciate any tip/help. Thanks in advance.

10:09 <PaulFertser> uuser: yes, "etb config" commands are all meant for very old ARM targets like those before Cortex-A/M was introduced.

10:10 <PaulFertser> uuser: you can extract and configure manually by direct manipulation of memory with mdw/mww and dump_image etc.

10:13 <uuser> PaulFertser: ahhh ok that s why it didn't work. Then I have to manipulate the memory of the chip to activate the trace functionality (set the correct register entry)?

10:13 <PaulFertser> uuser: since you're using jlink probably the most practical way is to use their proprietary tools...

10:13 <PaulFertser> uuser: or implement it for OpenOCD, yes, and you can prototype easily with Tcl or interactively over Telnet.

10:14 <Haohmaru> <stallman_propriatary.jpg>

10:17 <uuser> PaulFertser: even if I use a JLink I prefer software like openocd. Is there a more suitable probe to work with in combination with openocd which is also capable of doing this?

10:17 <PaulFertser> uuser: if you're interested in tracing https://orbcode.org/orbuculum/ has plenty of amazing material

10:18 <PaulFertser> uuser: configuring and extracting data from MTB should be possible with any probe, just nobody implemented it for OpenOCD.

10:18 <uuser> PaulFertser: Thank you very much, I will check it out.

14:27 <karlp> hrm, with openocd-esp32 I get much faster with jlink than cmsis-dap as well, same openocd though, just s!interface/jlink.cfg!interface/cmsis-dap.cfg!