7 Oct
2005
7 Oct
'05
12:47 p.m.
--- "Dwight K. Elvey" <dwight.elvey at amd.com> wrote:
Well I do, but it sounds like everyone is complaining
about the LA setup time (bringing it out of storage).
Mine is a permanent fixture on my bench, with loads of
various sized test clips (and a full set of dip test
clips), in 30 seconds I can have it powered up and
tracing on 8 timing signals, little longer if I want
16 bits of address/data and a clock, can't remember
the last time I used a scope.
But I suppose it like comparing a table saw with a
band saw, what they can do overlaps, and one does
certain things much better then the other, but you use
what you are more familar with and have available and
solve the problem whatever its limitations.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
From:
"Hans Franke" <Hans.Franke at siemens.com>
---snip---
First thing would be
to connect a logic analyzer to see if the CPU is
still running
a programm in ROM or not.
Hi
What is it with logic analyzers. Why not just an
oscilloscope. In most cases, one can be farther
along
with an 'oscope in finding what is wrong by the
time one can get an analyzer connected and setup.
I've only had one time that I ever needed an
analyzer
and even that time, it didn't work well because
of the complexity of the problem ( design not
failure ).
I'll admit that I've often thought of making one
of those address compare circuits to trigger the
'scope
but by the time I'd get serious, I'd found the
problem.
Am I alone here or does everyone else think that an
analyzer is the ultimate tool?
Dwight