Specifications

Wind River Trace for Wind River Workbench
Hardware Reference, 3.0
70
The following filtered trace options are supported for ColdFire processors with a
V2 Core and a Revision B+ Debug Module:
■
One Trace On (TE)
■
One Trace Off (TD)
■
One Trace On (TE) and one Trace Off (TD)
■
One to Four Report Only (MK)
■
One Trace Around (TC)
■
One to Four Trace Trigger (TR)
V3 Core
Revision B Debug Modules:
MCF 5307, MCF5307A, and MCF5307B
A debug exception can be used for filtered trace with the V3 Core with a Revision
B Debug Module, since it does not have the debug exception problem of the V2
Core. There is only one internal hardware code breakpoint in the V3 Core with a
Revision B Debug Module. Unfortunately, trying to use a WDEBUG instruction to
modify the internal hardware code breakpoint registers inside the debug exception
to simulate more than one internal hardware breakpoint does not work. This is
because the execution of a WDEBUG instruction within the debug exception
causes the BDM debug port to stop communicating with Wind River ICE SX.
The following filtered trace options are supported for ColdFire processors with a
V3 Core and a Revision B Debug Module:
■
One Trace On (TE)
■
One Trace Off (TD)
■
One Report Only (MK)
■
One Trace Around (TC)
■
One Trace Trigger (TR)
Revision B+ Debug Modules:
MCF5327, MCF5328, MCF5329, MCF5372, MCF5372L, MCF5373, MCF5373L