Hello, I am looking for a sophisticated RAM-Check-algorithm, that does not only detect problems with one cell like a simple write and read back. It should also be able to detect short ciruits and breaks of address-lines and maybe timing problems on the address-bus. Thanks!
Dear Mr.Michael Barr, My RAM was showing 384 (128+256) earlier. Now it shows only 382. What went wrong with RAM? How to check that? Could you please help me on this. Thanks & Regards G.M.Rao
I will, again, ask WHY?. The likelyhood of a RAM error in a properly designed system is something like one failure in a million units per year. Note: this excludes "infant mortality" I just checked with our field service, they have never replaced a SRAM. Erik
addendum to the above I just checked with our field service, they have never replaced a SRAM. is correct, there has, of course, been SRAM failures on board that totally failed for reasons like shorted PS etc. Such boards, however waer trashed. What I refer to above is the SRAM failing on it's own, not due to overvoltage, static or such. In those cases a RAM check would be worthless since the device cheking the RAm is destroyed as well. Erik
"Dear Mr.Michael Barr" Why are you addressing Mr Barr? He is not a party to this discussion! His work has simply been referenced! Have you actually read his paper on memory testing? It explains quite clearly the types of errors that commonly occur in memory systems, and how his tests address them. With that knowledge, you should be able to run the tests and interpret the results.