Hi Weblacky!
Quote:That's very good write-up and great results!
Thank you much!
Quote:What gave you the idea that the SRAMs were related to the IC being called out in the diag?
I've read the Octane Technical Report (the one with Impact graphics) to get some clue of the architecture of the Impact graphics series. I remembered VC3 from this paper, as i read the error message. I was hoping to find this Chip and analyze the issue further down from there.
I am into hard- and software development for custom industrial automation and control for a living (and for life!!). I started with my electronics hobby at age 10 and got a leg into retro computing by designing/building a Z80 based CP/M System from scratch using enamelled copper wire and Xilinx CPLDs for the custom VGA and IDE interfaces at age 15 (took me around 3 years onwards to gather all skills for this though!). So i may have developed an eye (and some intuition) for what and how i am searching and how i track down problems systematically. Including what to look for, if it says "SRAM", how it looks physically and what it does technical wise. And gladly, this SRAM error was quite well to find due to the fact, that one (and every time the same) half of a 16 bit word was failing.
BUT!! It was a great portion of luck involved. Much of this was possible by lucky circumstances. If any of the BGA chips had failed, it would have been hands down impossible for me. All the other SMD parts are day to day business, but a BGA would have ended my hopes to get it up and running instantly. Not to say, impossible for me to find the majority of other failures deeper inside the pipeline because we have no schematics anyways. As such i was happy to experience this particular failure rather than any other else

My old SolidImpact was such kind of thing. I can't do anything about it. No informations, no readable error messages, nothing. no clue where to start: dead...
Quote:Did you find there were connected in a conductivity testing between the IC legs and the legs of the SRAM chips?
After finding these two chips be SRAM in general, i did some conductivity checks between VC3 and the control signals of the SRAMs. They were indeed connected to each other.
Unfortunately this didn't tell if the SRAMs were the problem or if the VC3 is faulty. My first theory was this: If this dust had conductivity to it, it may have pulled from VCC to /WE on the SRAM. This pins are located next to each other on Pin 28 (VCC) and /WE (WriteEnable) on Pin 27. This would not have damaged the SRAM itself. It is used to get driven from outside onto WE, as this is an input signal. But it most likely didn't got written at all. I can tell this, as the errornous half reads differently by a certain pattern in the message. If it would have been written, it would be more random than just 0x00 and 0xFF. Most/Some SRAMs have a property, to have a distinctive pattern of 00 and FF after power up. This is what we can see in the error-log on the console. All upper halves are fine, and all lower halves show a regular consecutive pattern of 0xFF and 0x00 on a per address basis. This also shows, that it can (and gets) be read. If the Databus of the SRAM was faulty or the ReadEnable was the problem, the lower half output would have been all zeros or all ones, depending what way the designers of VC3 pulled the bus in case of tri-state on the data lines.
So i suspected the VC3 itself first. It's output drivers would'nt be very comfortable with a (strong?) pull to VCC, that might have been there due to the conductive dust.
But i then found both SRAM chips control signals beeing connected to each other. This leads to the fact, that both SRAMs are read and written at once. Knowing one of them to deliver back the data correctly, the "VC3-Pindriver-is-dead-theory" can most likely be set back for later. After i got this far, the second theory: it is also possible, that the SRAM itself got a problem and simply does not react to write enable anymore.
With this beeing the defect most likely now, and the easier task to do, I decided to swap both SRAMs over from the Solid and took the system for a test. It came up on the first try!
I am now going to recheck the old SRAMs and try to find out what happened to this SRAM to fail and see what it does in the component tester.
But for now, there is a whole new thing: Learning IRIX
Installing the Demos was an experience for itself. Fighting network settings and depecies. Got some of them now, but i need to find out how to setup my network properly. This is my anti-boredom-activity for today and i am scrolling through the web and this forum at the moment :-)
Currently it won't install the Indigo2Impact Demos because of a missing Performer package, doesn't mind installing the Octane demos, etc. I may be a hardware guy, but i definitely have no clue on IRIX yet

If just everything would be as good described as the Reanimator IRIX install! This was a great step by step experience :-) I am going to start a new thread, if i dont get it with the existing infos, if i may :-)
Cheers!