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.
Glitched graphics. Screen changes as board is flexed. Moved around board pressing chips until pressing the custom surface mount chip at B6 changed the effect. Noticed that the corner most pins had come up from the board. After an unsuccessful effort to resolder them, I used some enameled 38 swg wire to solder from the…
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…
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…
One of the guns on a Time Crisis 2 was no longer registering shots on the screen. Following checks on wiring, cleaning lens, etc. it appeared that the optical sensor (opto) was dead. This is a small PCB in the gun, 2421961100, pictured above. I couldn’t find any schematics or information about the parts used,…
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…