Neo Geo

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.

Similar Posts

  • Galaxian

    No display – When move board, display flickers – go around board pushing each chip in turn, when press on 2E picture appears. Pin 16 rusted, only just in place. replace chip – picture back to normal. No star display. Board had been hacked to play an alternate game, pin 15 on chip 2B had…

  • Sega System 16

    Altered Beast – Colours missing, no reds, other colours looked like diminished palette (like windows in 16 colours) – used test mode to perform ram test, and one ram chip identified as faulty (I10). Replaced this and red was back, but still reduced pallette. Looking at colour circuit, and it uses resistor arrays driven by I11…

  • Pacman

    Screen filled with coloured lines, unstable, no sync (see above) – check clock signals from horizontal and vertical scan generators (74161’s at 2R,2S,3R,3S) – no signal feeding into pin 2 of horizontal generators. Follow trace back to 7474 at 3N, signal going in, nothing coming out – replace chip and screen display back to normal….

  • Gallag

    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….

  • Missile Command

    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…

  • Make Trax

    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…