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.
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….
Crashing game. Game woud start attract mode, but shortly after would crash and boot loop. Entering test mode (hold player 1 start button whilst switching on) and it would pass first time around, but fail at random addresses on subsequent runs. The /WAIT signal on the main Z80 is handled by the IC at E2…
Totally dead, no screen display (blank white screen). For this I used the Fluke Z80-S2650 adapter to check out the ram and rom, and located two errors. The rom mapping was incorrect, with a large range of locations returning random values. Examining the board (since I have no schematics), all of the chip select lines meet up…
No Sound. Signal at output of SN76477 pin 13, follow through to input of sound amp, then from output until we reach electrolytic capacitor used to decouple connection to speaker. Signal going in, nothing coming out – replace capacitor sound back to normal. Only drawing a few pixels of player balloon sprite. Following the schematics,…
I had a spare bootleg replacement play pack from a Driving force on Galaxian hardware, so I proceeded to trace the circuit and try to identify the ICs used since they all have the IDs removed, other that the one attached as a later addition as IC7. Following the tracing, I used the pinouts to…
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…