Re: [tracecompass-dev] Beginner's (to a point) help needed.

[Harvey white <madyn@xxxxxxxxxxxxxxxx>]

Replies interleaved, thanks:

On 5/30/2022 9:19 AM, Bernd Hufmann via tracecompass-dev wrote:

Hi Harvey,

thanks for the interest in Trace Compass.

    I was happy to find it, if I can get it to
      work, I'll save myself some time.  I rather refused to pay some
      3000 USD for a license to percepio.  If I can get this to work,
      I'll write up something for you on how to add tracecompass to an
      ARM project, more on a step by step (including the FreeRTOS part,
      not obvious), and why.

I was browsing the code to understand when this error message is created. I noticed that there might be some errors logged into the Error Log when getting an CTFIterator that will hopefully give us some more information about the root cause of the issue. Could you please provide the error log? It can be found in the Trace Compass workspace under ".metadata/.log". The Trace Compass workspace is, when running the Trace Compass stand-alone RCP by default, "$user.home/.tracecompass", which results in:

$user.home/.tracecompass/.metadata/.log

I've attached a zip of the error log.  I'd been trying various things, and have accumulated a list of error messages.  What I don't see (and I'm not sure why) is that in the import process, I'm not getting data copied, or links put in, so it seems.

The error message itself, while informative to the developers, does seem to be a trifle opaque to others (eg: me....). 

Thanks,

Harvey

Best Regards

Bernd

---

From: tracecompass-dev <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of Harvey white <madyn@xxxxxxxxxxxxxxxx>
Sent: May 22, 2022 4:23 PM
To: TraceCompass Development <tracecompass-dev@xxxxxxxxxxx>
Subject: [tracecompass-dev] Beginner's (to a point) help needed.

 

ARM processor running FreeRTOS.

I have the trace hooks worked out.  And that calls a specific routine to
generate a trace packet.

I did have it working for task_switched_in and task_switched_out.

Something broke.

The init routine writes the main header and packet context, then writes
one event packet per event.  The ARM processor is single core.

I get the usual error (I suppose): error initializing trace. "Failed to
get CTF Iterator for path (path)"  The path exists, the file is there.

I've searched for a set of error messages with causes, haven't found them.

I've gotten the same error regardless of a number of changes.  To me,
the error message says "file does not exist", which may really mean
"file can't be parsed".  The metadata file seems fine, doesn't generate
any error messages.

So something is wrong, but I'm not sure what, and at this point, don't
know how to find out what.  The binary file output seems correct to me. 
(maybe obviously not).

Processor dumps binary trace data to a 1 mbyte buffer (QSPI RAM), then
that's sent to a file by using the eclipse memory manager. File looks
good.  metadata looks good.

Assistance, please.


Harvey


_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tracecompass-dev

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tracecompass-dev

Attachment: .log.zip
Description: Zip compressed data