> Other problem is that SPI analysis is done only by software. You CAN'T use
> the SPI readings as tringger. For example, you can't trigger the system when
> a SPI value was receveid. But others trigger possibility make this problem
> smaller.

One of the most common, and serious failings on devices like this, is
the absence of a "trigger out" pin.

I frequently want to see something with my scope in analog, which is
qualified by a logic sequence, or code sequence.  Trigger scope on the
start of instruction X, or when the LA says the long trigger thing has
happened...

I know I can add debug pin output to help when I'm looking for code
points, but the whole point is to not have to muck with the code while
also debugging it.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist