Specifications

4 Filtering Trace

4.3 Filtered Trace Limitations

unique trigger event on the PST[0:3]/DDATA[0:3] lines. The debug exception is

written to the address defined by the CF WSPACE option. The size of the WSPACE

must be at least 1K bytes long and should be located in a free area of RAM. Also,

the exception vector table entries at the offset addresses 0x30 and 0x31 are written

with the address of the debug exception. The Vector Base Register (VBR) value

must also be set to a location in RAM prior to running code. The configuration

option

CF SET_VBR should be set to the same value that the code would set it to in

RAM, so that the exception vector table entries at offsets 0x31 and 0x32 can be set

to the address of the debug exception. The internal hardware code breakpoint

registers are used to generate the debug exception. The debug exception is

executed every time the event address in the internal hardware breakpoint

registers is executed.

As a result of the specific behavior of the V2, V3 and V4 Core ColdFire processors,

there are some limitations to filtered trace when using Wind River Trace.

V2 Core

Revision A Debug Modules:

MCF5202, MCF 5204, MCF5206, MCF5206E, MCF5214, MCF5216, MCF5232,

MCF5233, MCF5234, MCF5235, MCF5249, MCF5249L, MCF5250, MCF5251,

MCF5270, MCF5271, MCF5272, MCF5274, MCF5274L, MCF5275, MCF5275L,

MCF5280, MCF5281, and MCF5282

Unfortunately, the V2 core, with a Revision A Debug Module, keeps re-entering

the debug exception immediately after executing the RTE instruction at the end of

the debug exception. Thus the V2 Core, with a Revision A Debug Module, gets

stuck endlessly executing one debug exception after another, making it unusable

for Wind River Trace. As a consequence, there are no filtered trace options

supported by Wind River Trace for any ColdFire processors with a V2 Core and a

Revision A Debug Module.

Revision B+ Debug Modules:

MCF5207, MCF5208A, MCF5211, MCF5212, and MCF5213

MCF52221, MCF52223, MCF52230, MCF52231, MCF52233, MCF52234, and

MCF52235

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

B+ Debug Module, since it does not have the debug exception problem of the

Revision A Debug Module. The V2 Core, with a Revision B+ Debug Module, has

four internal hardware code breakpoints.