I am using the external debugger Lauterbach to collect traces from the arm - M7 via coresight through the JTAG ports. While collecting the traces for the program loaded, the GUI of T32 displays FLOW ERROR (BAD TRACE PACKET ON D-SIDE) while stepping through the program. This is seen when the etm.dataTrace is set to anything except OFF.
What could this error mean?
Thank you.
A bad trace packet means in general that the trace decoder gets some ETM data, which is not known by the decoder at all. If the trace is transferred to the debug tool via dedicated parallel port (TPIU), this may be caused by electrical issues like crosstalk or bad terminations. It can also happen if your CPU core is newer than your TRACE32 version.
I recommend that you contact the Lauterbach support hotline for your specific request.