2023 +0200
target/espressif: add system level tracing feature
Produces traces compatible with SEGGER SystemView tool.
Signed-off-by: Erhan Kurubas
Change-Id: If1057309edbb91ed2cf1ebf9137c378d3deb9b88
diff --git a/doc/openocd.texi b/doc/openocd.texi
index 4154e56b54..684c6e8256 10
2022 +0300
target/espressif: add application tracing functionality over JTAG
This feature allows to transfer arbitrary data between host and
ESP32 via JTAG.
The main use cases:
1- Collecting application specific data
2- Lightweight logging to the host
3- System
Sorry Tommy. I now understand your question. I am not interested in any
targets. Rather, we are figuring out whether we can use OpenOCD for an internal
project. -- Cinly
From: Tommy Murphy
Sent: Tuesday, August 2, 2022 8:54 PM
To: Ooi, Cinly ; OpenOCD
Subject: Re: Tracing
I'm stil
I'm still not clear what, if any, specific trace enabled RISC-V target(s?) that
you're interested in?
From: Ooi, Cinly
Sent: Tuesday, August 2, 2022 3:31:50 AM
To: Tommy Murphy ; OpenOCD
Subject: RE: Tracing
Many thanks for your reply Tommy. Sor
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
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/
Hi All
I have a question on Tracing. Does OpenOCD support tracing for RISC-V? and if
so, can you point me to the section of the code that enabled this.
The reason for asking is when I look at the code, I see that the adapter_driver
struct has config_trace and poll_trace. This suggests to me
ote:
hi,
This is a request for comments for adapting arm coresight tracing in openocd.
It is motivated by :
- Current implementation of CoreSight tracing on ARM was developed for
ARM7, ARM9 and ARM11. this is now outdated and few developers are using it.
- Currently, there is an ongo
hi,
This is a request for comments for adapting arm coresight tracing in
openocd. It is motivated by :
- Current implementation of CoreSight tracing on ARM was developed
for ARM7, ARM9 and ARM11. this is now outdated and few developers are
using it.
- Currently, there is an
https://sourceforge.net/p/openocd/tickets/_discuss/thread/6f40c90d/9808/attachment/jlink-swd-stm32f7x-gdb-load-tpiu-ok.txt)
(258.7 kB; text/plain)
---
** [tickets:#184] jlink: failure after `load` when `tpiu` is used to enable
tracing**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Apr 27, 2018 05:33 P
l.txt)
(859.4 kB; text/plain)
---
** [tickets:#184] jlink: failure after `load` when `tpiu` is used to enable
tracing**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Apr 27, 2018 05:33 PM UTC by Cody Schafer
**Last Updated:** Wed Aug 22, 2018 02:30 PM UTC
**Owner:** nobody
**Attach
:#184] jlink: failure after `load` when `tpiu` is used to enable
tracing**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Apr 27, 2018 05:33 PM UTC by Cody Schafer
**Last Updated:** Fri Apr 27, 2018 05:46 PM UTC
**Owner:** nobody
**Attachments:**
-
[openocd.log](https://sourceforge.
[RFC] stlink: add SWO tracing support
Enable reading the SWO trace output via STLinkv2 dongles that support
it.
This adds an optional initialization parameter "trace" with which the user
specifies a destination file where SWO trace output is appended as it
[RFC] stlink: add SWO tracing support
Enable reading the SWO trace output via STLinkv2 dongles that support
it.
This adds an optional initialization parameter "stlink_swo_trace"
with which the user specifies a destination file where SWO trace output
is appe
14 matches
Mail list logo
