>
> I liked the below article of yours, since it described in
> detailed steps how
> you debugged a given boardset. Your focus on what you used
> and why was
> great! Thanks!
>
> Steve Ozdemir
>
>
> ps - I know it takes a bit of time to type all this up, but I
> wish we had
> more of this stuff on the vector email list. Mark Jenison
> gave us a summary
> a week ago, and I wish there'd been a bit more detail about
> how he tracked
> down the broken part.
Unfortunately, being mostly a software guy, I couldn't tell a data bus from
a school bus :-). All I can really says is "if you look at the
schematics..." (which I did), but I know not everyone has the schematics for
Eliminator at their desk ;-). Just trust me, replacing U6 fixes it :-)
ps. I absolutely agree with Steve on this; I love reading debugging logs.
The problem I hate though is when debugging logs go like this: "Then, take
your $1000 piece of test equipment that you don't have and that you can't
solve this problem without...." D'Oh! ;-)
-- Mark Jenison "Hmm...that line goes to that box...replace box...goto next line..." --------------------------------------------------------------------------- ** To UNSUBSCRIBE from vectorlist, send a message with "UNSUBSCRIBE" in the ** message body to vectorlist-request . Please direct other ** questions, comments, or problems to neil .
