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

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

  • Mr Do!

    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…

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

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

  • The Invaders – Zaccaria

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