Specifications

Wind River Trace for Wind River Workbench

Hardware Reference, 3.0

A debug exception can be used for filtered trace with the V4 Core with a Revision

D 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)

NOTE: When using both a Trace On (TE) and a Trace Off (TD), the processor must

execute the instruction at the Trace On address before the instruction at the Trace

Off address. This is because the first trace event encountered will be treated as the

Trace On event by the Wind River Trace module.

If the code to trace contains a loop, then both the Trace On and Trace Off instruction

addresses must be in the loop and the processor must execute the Trace On

followed by the Trace Off every time it loops. If the Trace On code executes more

than once before the next Trace Off code executes, you will not be able to get a valid

trace. Similarly, if the Trace Off code executes more than once before the next Trace

On code executes, you will not be able to get a valid trace

When tracing a small amount of instructions (less than 32) the Trace On and Trace

Off may not work. If this does occur, use the Trace Around with an After Trace (

AT)

Counter value set.

NOTE: When performing a filtered trace, do not refresh the Trace view while the

target is running. If the Trace view is refreshed while the target is running, the trace

capture will be temporarily halted. After refreshing, the trace capture will resume.

During the time the trace capture was halted, the condition that caused the trace to

either toggle on or toggle off may have changed, because the target is still running.

However, the trace capture will continue from its original state before it was

temporarily halted; this may no longer be valid, and may result in an invalid trace

being displayed.