Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
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…
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….
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….
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…
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…
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…