Hmm. WHAT trace buffers? I guess a full-scale ICE might
have a significant trace history, but I'm using the internal BDC;
In any case, the problem is detecting that a reset has occured.
It seems that usinga debugger based on BDC/DBG, an internally generated
reset like COP reset will reset the internal registers that would normally
let the debugger software know that anything had happened. So I can be
sitting in the debugger happily thinking I have three hardware breakpoints
set (one in BDC, two in DBG?), while a COP reset might have caused them
to be removed entirely...
(Of course, you an just disable COP reset when debugging, or you can
manually put BKGD (breakpoint) instructions in your init code, but I
was hoping for something more elegant?)