Brian E. Brzezicki
Copyright 2013
Version 1.00 04/06/2012

Disclaimer
Use this at your OWN risk, do NOT sue me if it breaks your board... if your doing this your board is probably already broken though ;)

Trouble shooting information

Game Board #1 March 2013

Problem:

    Missile command screen comes up, but no explosions, immediately resets, with dots going through the graphics

    Troubleshooting/dianosis steps:

    1. Put game into test mode, it says the POKEY is bad
    2. Swapped with a known good POKEY, same issue and still say POKEY is bad
    3. Probed the POKEY select pin on the POKEY, it's messed up
    4. Traced back to where POKEY select is driven from, noted the inputs did not match the outputs
    5. Removed chip, noted that somethign is still driving the POKEY select line
    6. Found POKEY select line shorted with an adjacent line, removed metal that was shorting the two wires
    7. Put POKEY back in
    8. Game works!
Game Board #2 April 23 2013

Problem:

    Missile command is missing bases

    Troubleshooting/dianosis steps:

    1. Put board into test mode, noted that one of the dip switches is physically broken, replaced
    2. Looked at color ROM, all pins that should be flipping are
    3. Went back to 74LS166 @ P6, noticed the output (pin 13) is stuck low
    4. Replaced 74LS166 @ P6
    5. Everything works, P6 pin 13 is no longer stuck... game works for a while.. then stopped working. Noted that when things are not working, pin 13 at P6 is stuck low again
    6. Noted game is resetting, noticed voltage on my test bench is low, fixed voltage, everything works again.. for a while then stopped working...again
    7. Noted if I touch the crystal the game resets, replaced crystal, I think one of the legs was broken or lose
    8. Game stops resetting when I touch the crystal, but still no bases
    9. hit reset a few times, then the system locked up with a yellow screen...tried replacing the CPU incase the CPU is causing these wierd issues... no change ...got angry and went to bed
    10. Turn it back on the next day.. everything is working again properly
    11. Hooked up Fluke 9010A and ran long RAM test on entire memory region.. everything came back fine
    12. Reset the game a few times as this before caused it to lock up with a yellow screen... everything still working
    13. Noticed the game often resets, especially when resetting, get's into a reset loop, also noticed when hitting reset, sometimes the game will pause, give a yellow or color screen, and hang for a while before resetting, someetimes the screen will reset multiple times. Theorized that somethign is causing the watchdog to reset probably memory corruption.
    14. Replaced all big 100uf power capactitors on the board, seems to fixed the problem, game now seems stable and constantly hitting the reset button gives consistant clear resets
    15. Game fixed
Game Board #3 Aug 18 2013

Problem:

    When turned on there is just a solid yellow screen that shakes. Board just not do anything in self test mode. (same thing)

    Troubleshooting/dianosis steps:

    1. Pulled POKEY
    2. Tested memory with fluke (long RAM test), multiple bit errors
    3. Tested ROMs with fluke, verified expected signatures, except one ROM with legs fell off when I pulled it out to validate.
    4. Manually tried writing to address 0, bit errors seem to occur on bits 0,1,2 and 4, probing with a logic probe and looping on reading and writing to address 0, found bit 4 (4116 @ L4) had a dead output, bits 0,1 and 2 seemed to be stuck regardless of input (validated input pattern "sounded" the same)
    5. replaced chips for bits 0,1,2,4 and 7
    6. now can write to memory address 0 ok
    7. getting DCD errors on bits 3,6
    8. diagnosed the memory decoder circuit, replaced an LS157 and LS153, looks like the data from the 153s are OK, additional testing looks like the signals are getting there OK, perhap an issue with the write select circuitry?
    9. replaced two more of th 4116s, have to still run a full long RAM test, but memory issues seem to be gone now.
    10. Replaced PROMS at np1 and r1 with 2732s (double programmed) (one was broken, the other was the wrong PROM)
    11. "fixed" broken 6502 CPU by soldering pins onto broken pins and putting in a socket
    12. Board resets after playing for a while
    13. Replaced a 74LS14 that was old and used and put in a new 74LS14
    14. Upgraded to version 3 code
    15. reflowed ROM socket solder
    16. Installed new 74LS244 and socket at NP/3
    17. Installed new socket for CPU
    18. Board is now working!
Game Board #4 Aug 19 2013

Problem:

    When turned on there is just a solid colored screen. Board just not do anything in self test mode. (same thing)

    Troubleshooting/dianosis steps:

    1. Notcied 10Mhz crystal was missing, installed new crystal
    2. Pulled POKEY
    3. Tested memory with fluke (long RAM test), bit errors 0xD3
    4. Replaced the 4116s corresponding to bit locates 0xD3
    5. Did long fluke memory test for range 0x000-0xEFF, now getting DCD errors address bit 3
    6. diagnosed the 4116 related to data bit 0x04 is bad, replaced
    7. getting new memory errors, replaced last 2 4116s
    8. board clears fluke long RAM test for addresses x0000 - 0x3FF
    9. Burned new ROMS (version 3)
    10. Sockets seem flakey, and one pin of one rom got bent putting it in
    11. board boots up to a white screen, no watchdog resetting
    12. Pulled ROMS
    13. board boots up to a white screen, still no watchdog resetting
    14. Examining counter at D4.
    15. Traced dead line back to pin 11 on D8, pulled chip, found chip is a 7474 NOT an 7400.
    16. socketed D8 and replaced, no change
    17. Found counter at D4 is not getting a 128H signal.
    18. Replaced counters (72LS191s) at A4 and B4, replaced counter (74LS93) at D4, verified that the watchdog circuitry is working.
    19. Game is booting up, but only showing yellow color and scrolling "Atari" text at bottom, in demo mode can see when missile shots got up but only a centimeter or so, and shot color is yellow.

    20. Traced from color RAM @ L7 back to 74LS175 @ C7 which had it's pin 10 (LO2COL) stuck low, removed, resocketed and replaced.
    21. Game is now working!
Game Board #5 Aug 23 2013

Problem:

    When turned on there is just a colored stripped screen

    Troubleshooting/dianosis steps:

    1. Pulled POKEY
    2. Pulled ROMs
    3. Tested memory with fluke (long RAM test), bit errors 0x40
    4. Replaced the 4116s @ n4 which corresponds to data bit 0x40
    5. Did long fluke memory test for range 0x000-0xEFF, OK
    6. Reinstalled ROMS and POKEY
    7. Board works!
Game Board #6 September 30 2013

Problem:

  • When turned on there is just a colored stripped screen
  • CPU socket plastic fell off when removing CPU, snapped back in, will probably want to replace that.

    Troubleshooting/dianosis steps:

    1. Pulled POKEY
    2. Did a RAM LONG test with Fluke 9010a, returned BTS 02 error, that's chip H4
    3. manual read/write test shows bit is stuck high, verified with read loop value 0x00 that and logic probe that input (pin 2 @ H4) toggles correctly but output (pin 14 @ H4) is stuck high
    4. removed 4116 @ H4 and installed socket and new 4116 RAM
    5. Board passes RAM long test for range 0x0000 - 0x3FFF
    6. Board boots up fine and passes self test mode!
    7. Board works!
Game Board #7 October 22 2013

Problem:

  • When turned on there is just a colored white screen

    Troubleshooting/dianosis steps:

    1. Did RAM long test on Fluke 9010a for range 0x0000 - 0x3FFF, got back RAM DCD error bit 8
    2. verified writes to 0x0000 and 0x0200 were the same for all bits (which means it's not a RAM issue it's a addressing issue)
    3. Found 74LS244 on F2 was stuck high, replaced.
    4. Board works!
Game Board #8 November 12 2013

Problem:

  • When turned on there is just this crazy multicolored zig-zag screen

    Troubleshooting/dianosis steps:

    1. Did a RAM long test on 0x0000-0x3FFF and immediately got back ALL BITS BAD, which is highly unlikely.
    2. Tried reading from a ROM location, got back 0xFF, tried another, same thing... this along with the memory points to an address decoding issue
    3. Tried reading RAM and ROM areas and checked the RAM and ROM select lines.. they didn't enable!
    4. Found a bad 7414 at position J6, socketed and replaced
    5. RAM now seems to be working, need to do a long RAM test.
    6. Put game into self test mode, got ROM 2 error, but OK sounds and RAM test
    7. pulled ROMS verfied in burner
    8. put ROMS back in game did fluke signature test, rom at JK1 was coming back bad with signature 0000
    9. Replaced 74LS244 @ BC/1, no change
    10. tested voltage across ROM, was less than 1V, swapped into another position and tested, still bad
    11. burned new ROM and re-installed
    12. All ROMS verify OK
    13. Game Works!
Game Board #9 November 13 2013

Problem:

  • Game seems to work and pass self tests, but the video is all snowy, and messed up and shifted 1/2 into the screen horizontally, additionally monitor has a wierd sound

    Troubleshooting/dianosis steps:

    1. Resocketed a couple chips (3) and tried replacement chips in timing circuits
    2. Found bad 7474 @ A9, socketed and replaced witha 74LS74
    3. Game works!
Game Board #10 December 23 2013

Problem:

  • Junk on screen, game not playing

    Troubleshooting/dianosis steps:

    1. Verified Clock signal
    2. Game is resetting
    3. performed long RAM test with Fluke 9010A on 0x000 -0x3FFF - OK
    4. Verified ROMS in burner, noted sockets are lose and some ROMS had bent pins, but
    5. Game still did not work after straigtening ROM legs
    6. Pull 6502 CPU, found it came out way to easy
    7. Put in new 6502, games worked
    8. tested OLD 6502 in another game with ZIF socket, it worked
    9. Pull old CPU back, game did not work, noted it went it way too easy and seemed lose
    10. Looked at socket, looked liek pins are white in some areas
    11. removed CPU socket, noticed green corrosion underneath socket, cleaned off with rubbing alcohol and toothbrush
    12. Soldered on new socket
    13. Put back original (old) CPU
    14. Game works!
Game Board #11 December 24 2013

Problem:

  • Game dead

    Troubleshooting/dianosis steps:

    1. Noticed crystal was missing, replaced
    2. game works!
Game Board #12 December 29 2013

Problem:

  • Game reported dead

    Troubleshooting/dianosis steps:

    1. Noticed crystal was missing, replaced
    2. Edge connector had dirt and solder on traces, desoldered, found a bunch of pads completely lifed. Put on new edge connectors
    3. Verified ROMS, found 2 bad ROMS, replaced
    4. Did fluke long RAM test immediately found bits 0x10 (4114 @ L4) and 0x80 (4116 @ P4) bad, replaced
    5. Did another long RAM test, got DCD errors, did some testing found 2114 @ M4 to be likely bad, replaced
    6. Board boots and tests OK, now but missing the color of the BASES. Seems similar to a problem I had on another board where ONLY the bases where there!

    7. After tracing back chips from P6 found bad 7474 @ A7, replaced
    8. Game works!
Game Board #13 March 10 29 2014

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. Fluke RAM long tests shows bit 2 is dead.
    2. Replaced, no change
    3. After much work, found that a reistory between the write enable control and the RAM was broken, but not visibly noticible.
  • Game works!
Game Board #14 March 10 29 2014

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. Fluke RAM long tests shows bit 5 is dead.
    2. Replaced, no change
    3. Found bad 74LS244
  • Game works!
Game Board #15 March 14 2014

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. BUS test failed multiple errors
    2. ROM test succeeded
    3. reading RAM at 0x0000 showed fluxuating numbers, looks like somethign is writing to the databus along with the RAM.. probalby a ROM
    4. Found programmmemory1 line was being actived
    5. Found a bridged trace on sockets near B5 and C5, resocket, BUS test succeeded
    6. RAM test failed with BTS 0x0C
    7. Found those chips where not getting the write signal
    8. Traced problem back to socketed PROM at L6, no continutity between output pins and WE pins. Removed old socket, put in new socket.
    9. Game works!
  • Game works!
Game Board #16 March 25 2014

Problem:

  • Wierd lines in graphics

    Troubleshooting/dianosis steps:

    1. Fluke ROM long test succeeded
    2. Replaced 74LS10 @ R5 - no change
    3. Cut power to 74LS125 - lines went from stripped to solid blue
    4. Replaced 74LS125 @ R6 - no change
    5. Pulled 7575 @ R7 - no change, put in socket and put back original
    6. Replaced 74LS153 @ P7 - fixed!
    7. Game works!
Game Board #15 March 18-23 2014

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. Fluke ROM long test succeeded
    2. Put game into test mode got ROM2 error
    3. pulled all ROMs, labeled with Fluke signature and tested
    4. Found ROM2 was bad, (all 0xFFs)
    5. Burned a new ROM and replaced
    6. Game boots up but when trying to enter test mode would constantly reset
    7. Reverified all ROMS, all succeeded except last ROM (range 0x7800 - 0x7FFF), it would read different each time
    8. pressed down on ROM socket for the last ROM, it passed fluke test and booted
    9. Removed socket and installed a new socket
    10. Game works!
Game Board #16 March 5/3 2014

Problem:

  • Game is dead Board has had all 4116s pulled and socketed

    Troubleshooting/dianosis steps:

    1. Fluke gives RAM error on BTS 0x40 all addresses
    2. Tried swapping out known good RAMs to no avail
    3. Used oscope tnd fluke 9010a in a write loop at address 0x0000 to find that the chip that holds the data for D6 (N2) has all kinds of other signal on there
    4. Found a small solder glob connecting the trace for the data input bit connectting to the pin for A0 (pin 5) on the chip at N2, removed the solder glob.
    5. No longer getting RAM BTS 0x4000 errors
Game Board #17 March 8/5 2014

Problem:

  • Game is dead
  • Screen is solid yellow

    Troubleshooting/dianosis steps:

    1. Verified +5V power
    2. Attached Fluke 9010A 6502 POD, it failed to connect. Assuming the POD is working this usually means
      • Bad +5V power or
      • Bad clock
    3. Probed pin #37 on 6502 socket (clock input) this is what I got

      That's not a proper clock signal.
    4. Verified signals from clock through D6, D5 and E5 where good (10Mhz -> 1H -> 128H -> HBLANK)
    5. Decided to look backwards from the CPUs side, noted input into pin #2 @ C4 was not what it should have been (it should have been about 1.25Mhz)
    6. Went backwards from there, noted circuit consist of 7474 @ A7, 74S74 @ B8 and 74S00 @ A8. checked A7 with logic comparator, looked bad, checked 74S75 @ A8 looked good, checked 74S00 @ A8, looked good.
    7. Replaced 7474 @ A7 with 74LS74 (don't have any 7474 but the 74LS74 is a modern replacement.
    8. Now there is a good clean 1.25Mhz signal on pin #37 on the 6502 CPU
    9. Game works!
Game Board #18 March 2/8 2015

Problem:

  • Game plays blind, owner reported there monitor had blown out other games syncs.

    Troubleshooting/diagnosis steps:

    1. Measured VSYNC line, it was all off.
    2. Looked at input to 74LS08 @ H7 pin #9, signal looked good,
    3. Looked at input to 74LS08 @ H7 pin #10 (VBLANK), signal looked good
    4. Looked at output of 74LS08 @ pin 8, all messed up
    5. Removed 74LS08 @ H7, noted there was still a signal on pin #8 (there should not have been as the chip creates the output signal on pin #8
    6. Tracked the trace from pin 8 to J7 which had been previously replaced by owner. Noted pin #12 was tied to pin 8 on J7 (it should not be)
    7. replaced socket on J7
    8. put back chips from H7 and J7
    9. Game works!
Game Board #19 March 08/09/2015

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. Noticed that LCD on test bench was not syncing
    2. Touched crystal, it was clear that it was broken, rattled and was lose when touched, replaced
    3. LCD now syncs however game is not working correctly, sometimes get garbage on screen that disappears, pressing ROMS changes sometimes.
    4. Did Fluke 9010A ROM test on all rom ranges, found JK1 did not give correct reading, pressed down then got correct reading.
    5. Removed all 6 ROM sockets and replaced, game boots now!
    6. Trackball however does not work, no movement at all
    7. Replaced MC14584 @ C9 just because that's usually the issue and I didn't have a way of spinning the trackball and measuring out output at the same time. No change, put back original chip @ C9
    8. I did not have a way of probing the circuit while I moved the trackball so I wanted to try to isolate the possible chips simply by using logic. There is only a few chips in the trackball circuitry. 74LS157 @ D9, 7474 @ J8, 74LS191 counter at K8 (verticle), 74LS191 at K9 (horizontal) 74LS244 @ L9. Now counters usually are common failures, howevever there are 2 counters eone controlling the horizontal and one the vertical direction. it's unlikely they BOTH went bad at the same time (since NO direction works).
    9. J8 is used by both of the direction circuits so it could be a failure, and also a common failing chip. However 74s are fairly easy to check as for each output there is an inverted output, so if you measure both outputs at the same time and they are OPPOSITES this chip is usually working (especially if the outputs changes over time. In this case the chips inputs were static indicating no input, and the outputs WERE inverted, so it was unlikely it was this chip.
    10. the 74LS157 @ D9 also can effect both directions. The 74LS157 is a quad dual input multiplexer. A dual input multiplexer has 2 inputs and 1 output. When the chip is enabled (pin 15 is ground) and the select (pin 1) is also at ground, then the output will match the first input. On Missile Command in upright mode the enable and select with both be at ground, so the input and the output should match. However when measuring input 1 (pin 2) and output 1 (pin 5) I found them to NOT match. I pulled the chip and put in a new socket and replaced. Now the trackball works!
    11. Game works!
Game Board #20 08/2015

Problem:

  • Game is dead

    Troubleshooting/dianosis steps:

    1. Noticed crystal is missing, replaced
    2. saw 3 really really bad 25V @ 100U caps, replaced just for good measure
    3. cap at c4 is broken in half, replaced
    4. chip is CPU socket is 40 pins, but doesn't even look like a 6502s label of any 6502 I've ever seen, label is faded out. tested CPU in another known working board and it did not work, replaced
    5. getting just a flashing screen
    6. did a RAM long test with Fluke 9010A in RAM range 0x0000 - 0x3FFF, all addresses give BTS 0x20 error, testing that bit is always low
    7. found bad prom @ L6, replaced
    8. RAM now is OK, game boots, but sounds are scratchy and quiet
    9. Replaced LM324
    10. Game works!
Game Board #21 10/7/2015

Problem:

  • Garbage on screen, the garbage changes ever so often

    Troubleshooting/dianosis steps:

    1. check reset line (pin #40 of CPU) it is watchdogging
    2. checked CPU clock (pin #37 it's OK at about 1.25Mhz)
    3. did RAM long check with Fluke 0x0000 - 0x3FFF - OK
    4. pulled out all ROMs and tested with ROM reader - all OK, MC version 2
    5. put ROMS back in game and tested with the Fluke. The first 5 ROMs (0x5000 - 0x77FF were OK) Howver the last ROM (R1, 0x7800 - 0x7FFF) was getting bad checksum from the CPUs standpoint.
    6. Did a read at address 0x7800 in looping mode, the low byte was changing... something is interfering on the bus when only the ROM should be talking.
    7. Pulled ROM and tested again, signal was stable
    8. Pulled POKEY, no change, but found cut trace under POKEY
    9. removed POKEY socket, fixed trace and put on new socket
    10. one at a time removed and replaced a few 74LS244s that tie directly to the unbuffered data bus to try to isolate the bus issue, to no avail.
    11. noticed owner had replaced sockets at C11, C9 and M9, pulled sockets, found a few bridged traces under the sockets repaired


    12. after testing for a while game lost it's yellow
    13. Found the color ram (82S25 @ l7) was never getting a write signal (write stuck high pin #3)
    14. trace back to find what generates the color ram write, it's 74LS42 @ E8, it was bad, replaced
    15. Game works!
Game Board #22 10/6/2015

Problem:

  • Game does not work
  • Nothing on screen
  • LCD monitor is syncing

    Troubleshooting/diagnosis steps:

    1. reset pin #40 on CPU is transitioning
    2. ROMS have been replaced with machined sockets... argh.
    3. Running fluke RAM long - ok
    4. read roms on programmer and then verified with ROM test on fluke - OK
    5. disabled watchdog and game boots up but with wierd color pattersn on the top and bottom.
    6. watchdog is never getting a clear signal
    7. reset game and not colors are bad
    8. looked at address decoding circuit to see what triggers the watchdog write, ls42 @ l8, definitely looks bad, replaced
    9. Game works!
Game Board #23 10/11/2015

Problem:

  • Game does not work
  • LCD monitor is NOT syncing
  • Game board seems to be hacked up with many poor repair attempts

    Troubleshooting/diagnosis steps:

    1. Fluke long 0x0000 - 0x3FFF gives BTS errors 0xFF
    2. Read with loop on 0x0000 shows all digits changing. must be bus issues
    3. ROMs checks with Fluke are OK
    4. Checked address decoders @ e8 and n2 both seem to be OK
    5. H and V sync chains seem OK
    6. found machined socket @ f4, carefully removed, horribly damanged traces EVERYWHERY
      • fixed traces and added socket


      • removed socket @ L6 and replaced just because
      • game boots up now but wierd little dots near the missile counters on the bases
      • Fluke long on RAM 0x0000 - 0x3FFF shows BTS error 0x40 starting at address 0x0300, this is 4116 @ N4
      • Verified with read and write loops that write signal is correct while looping read and write at address 0x0300
      • Pulled N4, socketed and replaced
      • Game works!
Game Board #24 11/11/2015

Problem:

  • Game does not work, solid yellow screen with white "noise" on top 15% of screen
  • Game is missing the CPU
  • Game board seems to be hacked up with many poor repair attempts

    Troubleshooting/diagnosis steps:

    1. Did Fluke long RAM on RAM range 0x0000 - 0x3FFF, got back BTS errors immediately, BTS errors changed for each address
    2. Did a looping read on 0x0000, both digits were changing rapidly, meaning the bus is messed up most likely
    3. Noted all RAM chips had been socketed, some looked questionable, note to self, will look at this more once I do other tests.
    4. Did ROM test to try to isolate bus issues to the RAM, ROM tests came back fine, which leads me even more to believe there is damaged to the socketed RAMS.
    5. Made sure address decoders at e8 and n2 were ok, they had been previously pulled. tested with HP 10529A and oscope in looping read, both looked fine
    6. Pulled both e8 and n2 and did a looping read on 0x0000, stable at 0xFF
    7. put back n2 and did a looping read on 0x0000, back to being messed up
    8. Pulled POKEYs no change, wasn't expecting a change, but figured good to rule out
    9. pulled ROMS, again not expecting a change but it's easy to test, still having issues with looping read @ 0x0000
    10. Pulled RAMS out of sockets, starting to check continuity of pins that are common and also to make sure there were not continuity on pins that should not be connected, found pin #4 and #13 are tied on the RAMS, which means there's got to be a bridged trace under one of these replaced sockets.
    11. used Hakko 808 to remove solder on pins #4 and #13 on each ram, still got continuity
    12. Pulled 4 the sockets that looked the most questionable after looking carefully at multiple angles to look for bridges underneath sockets.
    13. Found M4 had some damaged and smashed together traces, fixed.
    14. verified bridge fixed, checked for more bridges, didn't find any
    15. replaced pulled sockets
    16. Reinserted RAM
    17. Fluke passes RAM tests, and game boots with Fluke in it
    18. Put in replacement CPU (CPU was initially missing)
    19. Game works!
Game Board #25 11/15/2015

Problem:

  • This board was a PAIN with MULTIPLE failures
  • Game does not work
  • LCD test monitor is not syncing

    Troubleshooting/diagnosis steps:

    1. clock looks good, no reset either
    2. pulled cpu then got reset, game must be playing blind
    3. checking sync circuits, horizontal OK
    4. b4 has been previously socketed with a machined pin and has a bad signal on #2.. mixed signal need to investigate.
    5. pulled chip from socket, its got a signal 2Khz on pin #2, it should not have any which means there is a bridge somewhere. probing other pins and signal lines near the chip doesn't look like its a bad solder job on the socket, will verify with continuity test.
    6. found a trace back to B7 where the chip goes pin #11 and has a 14ohm resitance next to the next pin #12 going to pull that one, it's a 7427 which I don't have :( signals look sthe same, pulled chip and now mysterious signal on b4 is gone
    7. dont' have a new 7427 but pulled one off a donor board and replaced, gmae is OK!
    8. Explosions on attract screen anre NOT random, this is almost certainly a bad POKEYbad pokey, replaced with a used POKEY, Game is working correctly!!! OK!
    9. during LONG ram test board died, ram errors, not syncing to monitor, looks like VSYNC is messed up, incorrect values.
    10. 74LS08 @ D7 had a wierd VSYNC output, pulling, still same wierd signal
    11. D8 pin #2 seems to be connected to b4 pin #5?!? traced on end of D8 pin #2 to machine socketed chip @ D9 pin #1 - OK why is the flip signal going crazy? its flipping and it should not, ok maybe it should be its tied to reset, disabled watchdog now I have sync
    12. RAMS are getting 0xFFFF BTS errors, RAMs are recieving write signal, ROMS seem to be OK at least in range 0x5000 - 0x57FF
    13. watchdog writing is working
    14. replaced E2 and P5 to no avail.
    15. Board had previous work done on it, a few machined sockets in the areas I was looking at, pulled machined socketed pins and soldered in directly
    16. looking for something that can affect all rams, MADSEL... and MADSEL is not getting set, replaced R4 as 15 and 11 are dead... no change
    17. tested input #2 clock - OK, only thing left is LD pin #9 which is fed from pin #8 on E3
    18. ! MADSEL is never going high, WHY?!?
    19. looking at flip from output circuit
    20. tried replacing F9 (273) no change
    21. it has to be something talking on the bus??? since D0-D4 affect MADSEL? but I'm pretty sure the BUS is good... argh
    22. Decided to go down the BUS rabbit hole... pulled all 244s on data bus no change :(
    23. getting 0x8a after write of 0x00 to any ram address
    24. getting 0xff after write of 0xFF to any ram address
    25. why is the ROMs buffer interferring with the RAM when in, but still have such wierd ram errors on write, multiple issues maybe? (hint, yes tehre were_
    26. h6 tested bad pins 8 and 9, socketed and replaced, ram long test seems to be working now, RAMs test OK
    27. now ROMS are testing wrong!?!
    28. ROM at H1 should be f25a - NOT
    29. ROM at JK/1 reading 3977 - ok
    30. ROM at KL/1 should be e850 - reading 5893
    31. ROM at LN/1 should be ef62 reading EFC2
    32. Pulled H1 and rested the H1 Rnage (0x5000 - 0x57FF) I should not get ANYTHING, but I get the correct signature for the ROM at JK/1 ?$?
    33. checked JK1s enabled line it's ALWAYS enabled
    34. pull JK1 now H1, KL1 and LN1 are working! (which makes sense)
    35. eanbled pin on KJ1 is always high, this traces back to pin #3 on J6
    36. output of J6 (08) does not match inputs, pulled and replaced j6 fixed that problem
    37. Game works!
Game Board #26 11/10/2016

Problem:

  • Game does not work
  • No video sync

Troubleshooting/diagnosis steps:

  1. Tested watchdog, it is constantly resetting
  2. Tested CPU clock - OK
  3. Grounded watchdog, the video syncs and I get just a blue screen
  4. Did a Fluke 9010a RAM test for range 0x0000 - 0x3FFF - BTS FF @0x0000, which means the RAM is not working all bits reporting bad, at the first address tried. This is highly unlikely that ALL 8 RAMs went bad. So going to testsupporting hardware, especially the address decoding circuitry and the RAM write enable circuitry as that's often problematic
  5. First though I like to check all sync signals as they are needed throughout and often go bad
    • ALl H outputs in SYNC including E7 !HBLANK - OK
    • ALL V outputs in sync, chips A4, Br and #10 on !16V - OK
  6. So the SYNC circuits look good, check the address decoding circuits
  7. Address decoder @ N2 reseponds OK for a looping ram read @ 0x0000
  8. OK Address decoder for the RAM range looks OK, let's look at the RAM input / output circuitry
  9. did a looping write @ 0x0000, checked pin #3 (!write enable) on rams, they are getting the signal.
  10. did a looping write @ 0x0000, I do seem to get data bits on pin #2 of all 2114 chips.
  11. p5 (Ram buffer, getting enable signal OK during looping read), all inputs are low (inputs are pins 2,4,6,8, 11,13,15,17,19)
  12. wrote 0x55 to 0x000 and did looping read, all inputs bits still low
  13. Validated inputs to RAMs they are getting the correct signals on the write..., but outputs of read are always high impediance/floating
  14. piggybacked a 2114 since all ram outputs seemed floating, 1 bit got better.
  15. Pulled that one RAM chip and replaced, now that bit is OK
  16. Pulled another RAM chip and replaced, that bit is OK
  17. replaced all RAMS, memory tests run OK.. odd that they ALL were bad!
  18. Board is now booting but trackball doesn't move left correctly AND the soudns is all messed up, staticy
  19. replaced the LM324 because that usually is the static problem - no change
  20. Tested with a known good POKEY, as that's the only thing left in the sound circuit - NO change. Put back original POKEY
  21. MC14584 @ C9 had already been socketed and replaced, tried a known good MC14584, no change
  22. Pulled 7474 @ J8 - no change, put a socket in and replaced original
  23. Issue must be on data bus, tried to track down issue, ended up replacing 2 74LS244s before I noticed that under the POKEY socket there seemed to be some damage
  24. Pulled pokey socket, saw some smashed traces, found one trace was cut. Repaired, replaced socket and re-inserted POKEY
  25. Sounds are OK and trackball moves correctly
  26. Game works!
Game Board #27 4/10/2016

Problem:

  • Game does not work
  • Game missing all EPROMS
  • Game missing CPU
  • Game missing POKEY
  • Game missing bipolar PORM @ L6
  • Game missing 10Mhz crystal

Troubleshooting/diagnosis steps:

  1. replaced missing 10Mhz crystal
  2. replaced missing PROM @ L6
  3. still no clock on pin #37 of CPU
  4. no signal on 10Mhz test point
  5. tried another crystal, no change, put back first crystal
  6. pulled first chip to interact with 10Mhz crystal, 74H04 @ B6 didn't have a 74H04, used a 74LS04
  7. had some noise on CPU clock switched to a 74S04, fixed that problem.
  8. now have clock and video sync
  9. doing RAM long @ 0x0000 - 0x3FFF - OK
  10. all socketed chips missing (CPU, ROMs, POKEY) - replaced
  11. game still not syncing
  12. checking ROMs in circuit
    • h1 0x5000 - 0x57FF - f25A - ok
    • jk1 0x5800 - 0x5Fff - 3977 - ok
    • lk1 0x6000 - 0x67ff - cbe2 - ok
    • ln1 0x6800 - 0x6FFF - ef62 - ok
    • np1 0x7000 - 0x77ff - b25d - ok
    • r1 0x7800 - 0x7fff - B888 - ok
  13. odd watch dog is still going off
  14. checking sync circuit
    • D5 and E5 seem ok
    • vertical syncs b4 and a4 seem fine
  15. getting both watchdog and no syncing (sync returns when watchdog is disabled)
  16. Tested some 74ls74s in circuit with HP logic comparator, last one I checked @ F7 was bad (7474) - replaced with 74LS74
  17. game boots! thought screen to "big" might be LCD, adjusted out, looks good
  18. caps were pretty ugly
    • replaced all 100uf @ 25v caps
    • replaced all 10uf @ 25v caps
    • replaced all 1uf 25V caps
    • replaced 22uf 25V cap
  19. game boots and tests ok, but trackball doesn't move right or left
  20. replaced MC14584 @ C9 - fixed!
  21. Game works!
Game Board #28 4/16/2016

Problem:

  • monitor is not syncing
  • Game does not work

Troubleshooting/diagnosis steps:

  1. Board is very clean
  2. noticed L6 is in backwards, put back now get junk on screen
  3. put in known good L6
  4. Game boots but get ROM error 5 in test mode
  5. Tested the ROM in circuit, it is missile command v2
  6. all rom ranges tested fine except ROM range 0x7000 - 0x77ff is bad just as the test mode indicated
  7. Found that ROM MN1/ and LM1 were swapped
  8. Swappd back
  9. found that ROM MN/1 was bad
  10. replaced
  11. test mode OK now!
  12. did a long fluke RAM test just to make sure RAM is solid - OK
  13. game works!
Game Board #29 8/20/2016

Problem:

  • crosshairs is leavinga solid blue trail, blue bakcground over bases and arrows

Troubleshooting/diagnosis steps:

  1. 74LS153 @ P7 tested bad, replaced
  2. Game works!
Game Board #30 10/15/2016

Problem:

  • crosshairs is leavinga solid blue trail, blue bakcground over bases and arrows

Troubleshooting/diagnosis steps:

  1. looks like someone replaced the socket on P7 which holds a 74LS153
  2. That's a good diagnosis, and would be the first thing I tested.
  3. unfortunately the repair was questionable, not horrible mind you, but just not clean enough that I though it might be the issue, so I figured I'd pull it and make sure it was ok.
  4. ended up the repair was OK, but I cleaned it up and resoldered in a new socket anyway - no change
  5. swapped out the 74LS153 with a new one - no change
  6. Put back the original 74LS153
  7. OK so the 74LS153 is one of the last chips in the circuit that usually causes this issue, so worked back to chips that influence the 74LS153, immediately saw a signetics chip (they seem to be 90% of the bad chips in my repair) at C5 (72LS00). Tested it, it tested bad in circuit.
  8. Removed the 74ls00 @ C5, it also tested bad out of circuit
  9. Installed a new 74LS00 @ C5 - fixed the video problem!
  10. Game works!
Game Board #31 3/31/2017

Problem:

  • Static garbage on screen

Troubleshooting/diagnosis steps:

  1. Weird stuff on screen
  2. Fluke bus test OK
  3. Boards ROMS have had jumpers modified
  4. Missing a few caps
  5. Some corrosion near CPU
  6. CPU clock ok
  7. RAM long 0x0000 -0x3FFF BTS err 0xff @ 0x0000, this means none of the RAM chips are working or there's an issue with the control circuit... often the socket @ l6 on the PROM that controls ram writes is an issue.
  8. Going to replace PROM socket @ L6 as it's original and that's often a problem
  9. Replaced ROM socket @ l6
  10. Game works!
Game Board #32 4/7/2017

Problem:

  • Static garbage on screen

Troubleshooting/diagnosis steps:

  1. CPU clock ok
  2. Replacing prom socket @ L6, no change
  3. CPU bus test - data bit 0 - 7 tied high got to be the buffer
  4. Pulled 74ls244 @ e2, no change
  5. Could be B/C1 or N/P3 also or p5 or POKEY or M9 or P10, or L9
  6. Pulled pokey not that
  7. Looked started probing enabled on the various 74ls244s above
  8. 74LS244 @ BC1 is ALWAYS active (on) when it should NOT be
    • 74LS244 @ BC/1 is turned on by the 74H04 @ B6 pin #4, which is always LOW
    • B6 pin #4 is controlled by the input pin #3 on B6 it is floating.
    • B6 input pin is generated by the output of 7400 @ c5 pin #11. It is floating, it should NEVER be floating. The inputs to it (pin 12 and 13 are high), being a NAND gate, output pin #11 SHOULD be low when inputs are high, NOT floating.
    • replaced 7400 @ C5 with 74S00, bus test passes.
  9. Replaced pulled 74LS244 @ e2 with pulled chip
  10. Fluke short RAM test 0x0000 -0x3fff - ok
  11. Fluke long RAM test 0x0000 - 0x3fff - ok
  12. Game works!
Game Board #33 4/26/2017

Problem:

  • Blank yellow screen

Troubleshooting/diagnosis steps:

  1. Tested CPU reset line, it is NOT resetting, which means either it's working (playing blind) or the watchdog circuit is not working.
  2. Tested CPU clock, - OK
  3. Fluke 9010A CPU bus OK
  4. Flude RAM long test 0x0000 - 0x3fff - ok
  5. H sync oK
  6. V sync is MISSING!
  7. Vertical counters A4 and B4 outputs look ok
  8. Lets go backwards on the vsync circuit, 7408 @ h7 output pin 8 - dead, input pin 9 ok, input pin 10 is dead (VBLANK)
  9. VBLANK is generated by 74S260 @ a5, verify output pin 5 is dead, it is
  10. Check inputs (12, 1, 2, 3, 13), inputs look ok, lets remove this chip, chip tested bad out of circuit
  11. Replaced, game now boots up fine
  12. Game works!
Game Board #34 5/20/2017

Problem:

  • black screen will not sync

Troubleshooting/diagnosis steps:

  1. Board is missing EPROM @ h1
  2. Board has braze multi-missile command kit installed
  3. board set is Missile command version 2
  4. Disabling the watchdog I get a green screen
  5. Remove Braze kit and EPROMS
  6. Fluke 9010 Bus test ok
  7. Ram long 0x0000 - 0x3FFF - ok
  8. Tested EPROMS, 1 missing, 1 bad. replaced h1 and jk1 with newly burned ones, no change, still reseting
  9. ROMS tested with Fluke in circuit, all OK
  10. Replacing POKEY socket as it fell off
  11. Tesetd pokey, OK
  12. Game still resetting, with reset signal
  13. Tried writing to loop at watchdog address - this DID NOT stop the watch dog reset signal - thats a problem
  14. E8 (7442) pin #5 controls watchdog reset, it tested bad in circuit and out of circuit, replaced, game works!
  15. game works!
Game Board #35 10/07/2017

Problem:

  • black screen.

Troubleshooting/diagnosis steps:

  1. Checked voltage - low but OK
  2. Checked Clock - OK
  3. Checked /RESET - it is watchdogging
  4. Fluke BUS test - OK
  5. Fluke RAM long 0x0000 - 0x3FFF - failed DCD bit 0 @ 0x0000
  6. Removed POKEY and resetted RAM long - still same
  7. DCD bit 0 @ 0x0000 means that RAM address 0x0000 and 0x0001 should be "tied together, reading and writing to either will appear to affect the other with the same value
  8. Wrote 0 to 0x0000 - read back 0 - ok
  9. Read 0x0001 - was NOT 0 (something like 0xFD I think)
  10. Wrote 0xFF to 0x0001, read back OK
  11. Read back 0x0000 - now it's 0x01, that definitely doesn't look like a true DCD error
  12. write 0x00 to 0x0000, 0x0001, and 0x0002
  13. Write 0xFF to 0x0002
  14. Read back 0x0001 and 0x0002 both are now 0x01
  15. write 0x00 to 0x0002, 0x0003 - read back to verify - OK
  16. wrote 0xFF to 0x0003 and verified
  17. Read 0x0002 - it read 0x01 - looks like data bit 0 is bad which really is a BTS error 0x01
  18. Revmoed the RAM that corresponds to data bit 0 (4116 @ F4)
  19. Socked and replaced F4
  20. Game works!
Game Board #36 11/18/2017

Problem:

  • Game not working

Troubleshooting/diagnosis steps:

  1. game does not work
  2. Voltage OK
  3. Clock OK
  4. Reset not stuck low
  5. Fluke Bus test - ok
  6. Fluke RAM long 0x0000 - 0x3FFF - failed BTS FF @ 0x1000
  7. not likely to be an actual RAM error, more like an address decoding error dealing with address bit 12
  8. when reading/writing to 0x1000 hit bit is correct on both sides of F2
  9. /RAM at M3 pin #6 is incorrect
  10. Found 74LS42 @ n2 was bad
  11. Video of this fix at https://www.patreon.com/posts/15205858
  12. game now passes RAM test and ROM test, and is not resetting, but all you can see is a yellow stripe at the bottom of the screen
  13. found bad 74LS04 @ k7, replaced
  14. Game works!