Specifications

4 Filtering Trace
4.3 Filtered Trace Limitations
71
4
A debug exception can be used for filtered trace with the V3 Core with a Revision
B+ Debug Module. The V3 Core, with a Revision B+ Debug Module, has four
internal hardware code breakpoints.
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 Trace On (TE) and one Trace Off (TD)
■
One to Four Report Only (MK)
■
One Trace Around (TC)
■
One to Four Trace Trigger (TR)
V4 Core
Revision C Debug Modules:
MCF5407
A debug exception can be used for filtered trace with the V4 Core with a Revision
C Debug Module, since it does not have the debug exception problem of the V2
Core. The V4 core has four internal hardware code breakpoints.
The following filtered trace options are supported for ColdFire processors with a
V4 Core and a Revision C 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)
Revision D Debug Modules:
MCF5470, MCF5471, MCF5472, MCF5473, MCF5474, MCF5475, MCF5480,
MCF5481, MCF5482, MCF5483, MCF5484, and MCF5485