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. Using the test probe I shorted pins 11+12 on one chip, powering on the board now gave read as 51FF so I was looking at the wrong chip. Replacing the other (with a 2018-35) sorted the problem.
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)
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…
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…
On power up – black screen, no sign of life at all. I removed the 68000 CPU and fitted a socket, so I could use the Fluke on it. This revealed that the main program ram ($10C000-$10FFFF) was totally dead. Replacing the two ram chips IC25 and IC26 solved this problem. Board now started up,…
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….
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…