Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
Board ID 8016 : Falcon version ?
Static graphics on screen, dead – pin 24 low on Z80, /WAIT signal. Trace signal on board to 74LS74 at E7. Signal incorrect for inputs. Replace with new one, board fixed.
Missing Chip. This was a converted moon cresta board. The IC at 1.2S (shoehorned in sideways between rows 1 and 2 by the sprite ram) was missing. This was not featured on any schematics I had, so I traced the connections to see what it could be. It basically takes the output from the sprite…
Screen filled with coloured lines, unstable, no sync (see above) – check clock signals from horizontal and vertical scan generators (74161’s at 2R,2S,3R,3S) – no signal feeding into pin 2 of horizontal generators. Follow trace back to 7474 at 3N, signal going in, nothing coming out – replace chip and screen display back to normal….
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)
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…
6 Slot – Memory test on power up giving error Address Write Read 00008000 5555 55FF Checking with Mame, the memory chips in question were only small, so looking at the board revealed two DIL 5814’s. Chip select signals to these were toggling as expected, so I needed to identify which ram chip was which….
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…