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 on the board, which has the ID sanded off (as does several other chips), however the schematics for the other games (Mr Do’s Castle), and the silk print on the PCB show this as being a 74LS01 – replacing this with a new 74LS01 fixed the problem. (incidentally, it has to be a 74LS01 as it wire-ORs three of the outputs together.
Similar Posts
Make Trax
ByadminBoot 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…
Missile Command
ByadminThe 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…
Neo Geo
Byadmin6 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….
Carnival
Carnival on a Gremlin / Sega Vic Dual PCB. Just had blue bars on screen, although probing the Z80 showed it was trying to run code. Using a logic probe I discovered that the /WRITE signal of the ram chips was always high. This signal comes from a 74LS10 at U77. Checked this chip and…
The Invaders – Zaccaria
ByadminTotally 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…