Re: Tracing

[Tommy M. <tom...@ho...>]

I'm still not clear what, if any, specific trace enabled RISC-V target(s?) that you're interested in?
________________________________
From: Ooi, Cinly <cin...@in...>
Sent: Tuesday, August 2, 2022 3:31:50 AM
To: Tommy Murphy <tom...@ho...>; OpenOCD <Ope...@li...>
Subject: RE: Tracing


Many thanks for your reply Tommy. Sorry for the late response. Monday was a holiday here.

No worry Tommy, I am just working out which debugger has Trace support. As you noted, it is very new.

Part of the reason is I was wondering whether OpenOCD was one of the debugger used to enabled Tracing during standard development.


Best regards

Cinly



From: Tommy Murphy <tom...@ho...>
Sent: Friday, July 29, 2022 8:28 PM
To: Ooi, Cinly <cin...@in...>; OpenOCD <Ope...@li...>
Subject: Re: Tracing



As far as I know, there is no RISC-V trace support in OpenOCD. In fact, RISC-V trace (or maybe only parts thereof - e.g. trace data protocols as opposed to trace transport(s)?) was only formally standardised recently:



https://wiki.riscv.org/plugins/servlet/mobile?contentId=26574878#content/view/26574878



There are some implementations in existence but they are most likely custom. For example, UltraSoC (now Siemens) do have an implementation for their flavour of trace but that's only of relevance if one's target implements their IP in hardware (the ust_* files here).



https://github.com/ultrasoc/riscv-openocd/tree/master/src/jtag/drivers



Others may also have custom trace IP and maybe OpenOCD forks too, but UltraSoC is the only one that I have ever worked with.



What RISC-V trace implementation are you looking at/interested in?