 |
|
Sourcecode-instrumenting for select. Trace
|
|
 |
How do I instrument my sourcecode for selective tracing?
|
| |
|
The sourcecode to be traced needs to be surrounded by the following
assembler instructions:
PEA.L 2(PC)
WDDATA.L (A7)+
-- your source code goes here --
PEA.L 3(PC)
WDDATA.L (A7)+
Naturally you can also use these in inline assembler code or maybe even tell your compiler
to add these instructions to the function prologue and epilogue automatically.
The basic principle of the above instructions is that the WDDATA.L needs to write out it′s own address. If bit 0 of the address is clear the trace will turn on, if bit 0 is set, the trace will stop.
Prerequisites:
- ColdFire CPU with PST3..0 and DDATA3..0 signals available and connected to the debug port
- T32 ColdFire Preprocessor from mid-2004 or later (reprogram maybe needed)
- T32 Software 2009 or later
- SYSTEM.OPTION TRACEWDDATA ON
|
|
|
eTPU Debugger (COLDFIRE)
|
|
|
Do you have any plan to support eTPU HLL debugger?
|
| |
|
Yes, eTPU debugging and tracing is supported with an additional SW package. The PowerPC core and both eTPU cores can be debugged and traced at the same time (one trace/debug box, one host, but different SW packages).
Demo scripts are available in \demo\etpu in the Trace32 installation folder or on the installation DVD.
Note: MPC563xM (Monaco) only supports NEXUS class 1 for eTPU. Tracing the eTPU on this processor is not possible.
|
