Hi
As request, post email communication of TD command result here,
==============================================================================
Hi Thomas,
I have tried with TD command to parse trace.bin.
c:\ti\ccsv5\ccs_base\emulation\analysis\bin\td.exe -procid 64x -bin D:\SCT_Workspace\Tools\Profiling\AutoTrace\trace.bin -app D:\SCT_Workspace\Tools\Profiling\AutoTrace\core3.out -rcvr pro -format CSV_NO_TPOS_QUOTE -output D:\SCT_Workspace\Tools\Profiling\AutoTrace\mytrace.csv
rem -format CSV_NO_TPOS_QUOTE -timestamp abs -seekpos 10 -samples 100000
Output,
Bad PC, current export frame processing aborted, Sample not verified, The causes of this may be a possible bad branch pointer, corrupted trace data, wrong program file used during post-processing, unintended corruption of program image, use of non-traceable program image overlay, or self-modifying code. |
Sample not verified |
Bad data trace, Bad trace data packet sequence
From parser result trace.bin are bad trace, so now problem should be located in one of below, trace catch issue;trace parser issue.
And I have another questions that, in mytrace.csv, there is no cycle data,
Program Address | Load Address | Program Data | Read Address | Read Data | Read Size (In Bits) | Write Address | Write Data | Write Size (In Bits) | Cycles | Trace Status |
which command that we can get functional level CPU cycle in script?
Thanks,
-David