On Tue, May 18, 2021 at 8:10 PM Tim Newsome wrote:
>
> OpenOCD kills itself instead of exiting normally. This prevents coverage from
> working, and profiling might have the same problem. Here's what I did for
> coverage:
OpenOCD kills itself only if it has been closed with Ctrl-C.
This is a req
OpenOCD kills itself instead of exiting normally. This prevents coverage
from working, and profiling might have the same problem. Here's what I did
for coverage:
- Runtime coverage testing
Apply the following patch to prevent OpenOCD from killing itself:
@code
--- a/src/openocd.c
+++ b/src/op
it sounds like any previou latencies might be
at/below your driver level so that the best place to start and focus on?
From: Ooi, Cinly
Sent: Tuesday, May 18, 2021 3:51:56 PM
To: OpenOCD
Subject: Profiling Tool for OpenOCD
Hi
Does anyone has experience
Hi Cinly,
I think you need to go in the route you are already in (gprof, etc).
As a side note, for those trying to profiling the target board instead
of the host, please take a look at this project:
https://github.com/orbcode/orbuculum
Using it the author was able to profile the NuttX RTOS to tr
Hi
Does anyone has experience profiling OpenOCD and can share the experience, i.e.
tools etc?
The reason for asking is the driver that I am developing, aji_client
(https://github.com/intel/aji_openocd) is slow under some circumstances. Good
news is those circumstances are consistently reproduc
