This information is provided "as-is" without warranty.  If you find any errors please contact me.
Help improve the database! Sign up today and start contributing!

Looking for a different game? Use the Browse Games page!

Dig Dug
Platform: Arcade  
Game: Dig Dug   Display Type: raster  
Manufacturer: Namco (Atari license)   Resolution (W x H): 288 x 224  
Year Released: 1982   Orientation: V  
Main CPU: Z80   Audio Channels: 1  
# of Players: 2   # of Buttons: 1  
# Simul. Players: 2P alt   Genres: Maze, Digging  
Controls: 4 way Joystick  
MAME Driver Status: good   MAME Driver Emulation: good  
MAME Driver Sound: good   MAME Driver Color: good  
MAME Driver Graphics: good    
MAME Source File: \src\mame\drivers\galaga.cpp  

Dip switches used by this game

The link below will take you to another page that shows all the dip switch settings for this game.  Dip Switches have their own page to make it more printer friendly.

Memory Map for this game

If you need a memory map for your game that you are working on repairing, you can view that with the link below. 

ROMS used by this game

The following is a list of ROMS that are used by this game.  Many games had multiple versions of ROMS.  If you are not sure which version of ROM you have, you can use the ROM Identification Page to upload an image and find out. 
Rom Name Ascending
Rom Size 
Expand Dig Dug (Atari, rev 1) found in MAME ROM Set: digdugat1 Released in 1982
Expand Dig Dug (Atari, rev 2) found in MAME ROM Set: digdugat Released in 1982

PCBs for this game

The following is a list of the PCB's used by this game.  Many games had multiple versions of the different PCB's.  For more detailed information about a PCB, click on the Part # link for that PCB.
Part Number 
Stack Part Number 
Pcb Function 
A035435   PowerSupplyArcadenut
The are two versions from Atari and one version from Namco.  The two pictures here are the Atari Versions.  Each board has a distinctive layout.
When looking on for the RAM and ROM failures you'll need to figure out which PCB you have and match it either to Type "A" or Type "B".  This will give you the physical location of the RAM/ROM chip that is reported as bad.
For example, a bad RAM of 3L is physically located at 9H/J on a Type "A" board and 7L on a Type "B" board.

Parts for this game

The following is a list of the Parts that can be used by this game.  Many games used the same parts.  For more detailed information about a Part, click on the Part # link for that Part.
Part Number 
Part Type 
Part Group 
A038297-01 Harness Atari GamesDig Dug

Repair Logs for this game

The following is a list of the Repair Logs for this game.   For more detailed information about a Repair Log, click on the Title link for that Repair Log.
Scrambled video, ROM issues Powers up to scrambled video and watchdogs.
Game appears to be booting, but video output is non-functional. Probing /CSYNC shows it stuck low. Tracing sync back from the test lug, found a broken leg on R86. Fixed, but still no video.
/CSYNC originates at LS368 @4E, with /CMPSYNC output on pin 3 and input coming from pin 2. Continuity from the sync pin to 4E's output was good, so started probing with a scope. Signal on /VSYNC and /HSYNC test lugs looked good, but output on 4E was not correct — H sync was present, but there was no V sync added.
Per the schematic, input to 4E comes from a LS00 @6H, LS74 @6C, and LS86 @4A. 4A is not populated on this PCB, and 6C's outputs connect directly to 4E's inputs. 4A is driven by /VSYNC and the 4V line from the 07xx custom @4C. Both these inputs appear good, but output lacks V sync, so the LS74 is suspect. Comparing in-circuit against known good part with a logic comparitor confirms a fault. Socketed and replaced the part, and video is now present.
While there is video, the board is watchdogging. It gets through most of the power-on tests, prints "RAM OK," and resets, which is a good indication that there is a ROM problem. Put it on the Fluke and ran ROM tests, which returned the correct signatures, but at the wrong locations. Visual comparison against another board showed that the -205 and -206 ROMs had been installed in the wrong sockets. Swapped them into the correct locations, and the board boots and plays.
Page 1 of 1 (1 items)< < Prev1Next > >
© Copyright 2009-2019, ClassicSoft, LLC. All rights reserved
Powered by the ClassicSoft Web Content Framework V3