Not trying to sound like an old nag, but the first step to trouble shooting the Asteroids Multigame is to throughly review the install instructions and double check all of your work checking for bent pins, checking that the kit is not overlapping the socket by one pin, checking for backwards CPU, and that the 2 wires are indeed soldered to the correct locations on the board. This is also a good time to review the multigame Power On Self Test (POST) and testmode procedures.
The two Start LEDs and audio sounds are used to help debug problems. It is essential that your machine's start LEDs and Audio are all fully working.
The general approach for trouble shooting the multikit is to determine what (if any) signs of life the game indicates and from that determine how far into the startup sequence the game as progressed. This can greatly narrow down the scope of the problem and how to debug it. The multikit has enhanced diagnostic functions not found on the original asteroids board and also performs diagnostic tests in a more extensive and exhaustive manner. In some cases it is possible the multikit will detect existing problems not previously detected by the original asteroids software.
Try putting the game in and out of testmode to see if there is any behavior change, such as LED patterns, audio tones, messages on screen. Attempt to get a full assessment of the state of the machine, then look over the following sections to see what topics match with the problem(s) seen.
Game appears dead - Both LEDs are always off
Game appears dead - Both LEDs are always ON
Game not running - LEDs flicker or flash quickly
Game not running - LEDs blinking slowly
Game not running - series of beeps in testmode
What are looking for in this section is for any signs of life such as even a brief flash of the start LEDS.
Check to see if the red +5V LED on the game board itself is on. Make sure the game board is probably installed with the correct orientation of the edge connector. If the pcb LED is off, the board does not have power
The game board will powerup with both the two Start LEDS ON. As well if the game is resetting (eg watchdogging), each reset should cause the LEDs to come back on, even if just briefly. Try both test mode on and test mode off switch settings.
If the LEDs do light, even if just briefly, check out the section Game appears dead - Both LEDs are always ON. If you cannot get the start LEDs to light at all, then focus back on the board installation, power supply, etc. As it appears the problem is probably not related to the kit.
The game board will powerup with both the two Start LEDS ON. As well if the game is resetting (eg watchdogging), each reset should cause the LEDs to come back on, even if just briefly. Look closely and see if the LEDs flash, even if very briefly. See if testmode switch on or off changes the behavior.
What we are looking for here is any sign that the 6502 CPU complex has started executing instructions. One of the very first things the multigame software does during bootup is to turn off player-1 start LED (but leave on the player-2 start LED). It does this very early in the bringup sequence to indicate the first signs of life. If the game board resets, it still should cause a quick flickering of LED-1. Determine if the LEDs never turn off or if they flicker or flash.
Try both test mode on and test mode off switch settings.
Game is probaby running for just a split second and then the watchdog is resetting the game (eg. watchdogging). Since the game powers up with both LEDs ON and the early boot sequence turns off LED-1, a reset can appear to make it look like LED-1 is flickering. If the game is resetting, the strategy is to figure out what is causing it to reset.
Try both test mode on and test mode off switch settings and see if that changes the behavior any. Testmode will do a series of exhaustive memory tests, and if any of the tests fail it will pulse out a code using high and low tones as well it will flash the LEDs in conjunction with the pulses. If you are seeing this behavior check out section Game not running - series of beeps in testmode.
The multigame diagnostic software makes many uses of the LEDs during selftest operations to indicate progress and or failures. The use of the LEDs is different for testmode versus the normal powerup boot sequence. In addition to the LEDs, audio tones may accompany the failure pattern to provide additional information. The following table shows the failure codes.
| Normal Bootup LED patterns | ||
| LED-1 | LED-2 | Notes |
| Off (never ON) |
Off (never ON) |
Most likely board does not have power. See dead. |
| ON | ON | Initial powerup status. CPU is not running. See stuck. |
| Off | ON | Game has started to run. Indicates progressed to state "running CPU tests". The game should not stay hung in this state. |
| Flickering | ON | Game may be watchdogging (resetting) and causing LED-1 to appear to flash very quickly. This is not the same as a slow blinking LED-1 pattern. It could be a CPU RAM failure. Put the game in testmode for more exhaustive testing, as testmode is able to better test and isolate CPU RAM failures. See flicker. |
| Off | Slow Blink | Game has failed atleast one of the CPU tests. It is likely the game may reset (watchdog) and thus interrupt this blinking pattern and restart the tests. Disabling the watchdog reset circuit may allow this pattern to be continually displayed thus giving information that there is a problem in the CPU area. Also trying testmode should provide additional information. |
| ON | Off | Game has passed the CPU tests. Indicates progressed to state "running VECTOR tests". The game should not stay hung in this state. |
| Slow Blink | Off | Game has failed atleast one of the VECTOR tests. |
| Slow Blink Alternating | Slow Blink Alternating |
Game has failed atleast one of the selftests, but the CPU and VECTOR tests passed. The test failure is displayed on the screen. The game is prohibited from entering gameplay mode due to the failing hardware and remains in this state. |
| Slow Blink Synchronized | Slow Blink Synchronized |
Selftest has passed and is performing the countdown while displaying the bootup splash screen test results. Or it has finished the countdown, transitioned to the multigame, AND the multigame is configured for FREE PLAY (default). The LEDs are flashing to indicate you may start a 1-player or 2-player game. |
| Off | Off | Selftest has passed and has finished showing the countdown bootup splash screen. It has transitioned to the multigame and the multigame is configured for coinage LEDs are off indicating that coins need to be added before a game can be started. |
| Test Mode LED patterns | ||
| LED-1 | LED-2 | Notes |
The multigame software has exhaustive memory tests which are run at the beginning of testmode on both the CPU RAM and the VECTOR RAM. The multigame completely tests all of the RAM and if there are any failures it beeps out a code using high and low tones just like the original asteroids testmode does. See section test mode memory failures.
When in configuration settings mode pressing LEFT + RIGHT + FIRE + THRUST will cause the entire contents of the serial eeprom to be completely erased. All high scores and settings will be lost! This is a hidden backdoor way to resetting the game to its factory defaults and should be used with caution.
This from REV-05 board. low beep good. medium tone beep bad. led2=on good. led1=on bad.
