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 one of the inputs – WG (pin 4) was always low, so the NAND output was always high. WG signal is generated from the 74LS175 at U19 and sure enough, Q and /Q were static.

Replacing this chip returned the write signal to normal, and fixed the game.

Similar Posts

  • Namco Time Crisis 2 Gun

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

  • Hantarex MTC9000/A

    No picture, Hole blown through LOPT. Had problems tracking down replacement – little tip given to me by Hantarex engineer – you can use the LOPT from an MTC9000 as long as you cut pin 2 off. (If you leave it connected, you will get a direct short to GND)

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

  • Dark Seal

    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…

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