MSV11-D debugging question

Brent Hilpert hilpert at
Wed Feb 4 21:01:19 CST 2015

On 2015-Feb-04, at 2:57 PM, Noel Chiappa wrote:
> Finally getting back to this:
>> From: Brent Hilpert

>>> Again, I have a sitation where a bit is stuck on, and I'm curious to
>>> see if anyone has any insight into which chip (of 3) might be causing
>>> it (in an attempt to not have to try replacing them at random :-).
>> (Are they 4116 memory chips in use?)
> Yes.
>> a means to isolate which of the 3 points (ICs/pins) is the problem
>> might (not guaranteed) be:
>> ...
>> If the state is only faulty after one of the accesses it suggests the
>> according mem chip is the failure point. ... distinguish the accesses
>> to the upper and lower bank to try to isolate when the circuit enters
>> the faulty state, and see whether it's common to both banks or only one.
> Thank you! Thank you!! Thank You!!! That worked a treat; found the bad chip
> first time! Thanks again!

Thanks for the update, nice to know it worked out.

More information about the cctalk mailing list