6 Slot – Memory test on power up giving error
Address Write Read
00008000 5555 55FF
Checking with Mame, the memory chips in question were only small, so looking at the board revealed two DIL 5814’s. Chip select signals to these were toggling as expected, so I needed to identify which ram chip was which. Using the test probe I shorted pins 11+12 on one chip, powering on the board now gave read as 51FF so I was looking at the wrong chip. Replacing the other (with a 2018-35) sorted the problem.
In normal mode, just had a blank screen. Enable test mode and you instead get an error message showing that the ROM test had failed (even though the rom itself checks out OK with correct content) This is because the custom Atari SLAPSTIC chip is not functioning correctly. It is used to page banks of…
Capacitor burnt. (game board), particularly at C37 the capacitor was showing signs of extreme heat. Replaced them all with 22uF 25V axial electrolytics. No Speech / Some SFX missing. (game board) Output from speech chip SC01 was OK, as was output from IO Custom (X3). checked transistors in output stage and 2N4401 was faulty. (Q2)…
Boot up with garbage, quickly clears screen and then nothing. Used Fluke with Z80 pod – read rom OK, and write ram OK, but timeout reading any Ram location. Check fluke status and ‘wait’ always set. Check pin 24 of Z80– stuck low, trace back through 7H,7C,6C1 to 6B1 pin 2 – always low, although…
Blank screen, Blanking line to output colour proms always enabled. Trace back to 74161 in timing circuit – output stuck, input clock all look OK – replace chip and picture appears. Blue video only – The video lines are controlled by three transistors near the edge connector, checking these revealed that 2 were not giving…
Ran through self test OK, came up with chequer board screen and then reset most of the time. Occasionally would start game, but with credit noise continually playing and credits rapidly counting upwards. This is caused by CPU 4 (E5) not running properly. checked the eprom and ram (C5,D5 and E5) and ram was faulty….
The board originally failed to get into the game, instead resetting just after drawing the ‘MISSILE COMMAND’ logo. Test mode faired a little better, managing to report RAM OK, MAP OK and ROM OK before resetting. Ram and Rom checked out OK using the Fluke. Measuring various CPU signals revealed that the interrupt seemed very…