Tecmo Knight/Wild Fang PLD

 PAL Updates  Comments Off on Tecmo Knight/Wild Fang PLD
Mar 252014
 

Found a PAL chip on my Wild Fang PCB today.
Its labelled T-3 and is found on the CPU board.
All tested and confirmed working.

 Posted by at 7:09 pm

A Spy Hunter PLD dump

 PAL Updates  Comments Off on A Spy Hunter PLD dump
Mar 142014
 

Here is another dump/recreation from the Spy Hunter boardset.
This one is labelled 0066-316BX-XXQX and is found at location 13B on the main CPU board.

Only 3 more to go but they are gonna be tough.

 Posted by at 2:34 pm

Spy Hunter repair log #3

 PCB Repair Logs, Repair Logs  Comments Off on Spy Hunter repair log #3
Mar 122014
 

A quick one here.
Tested a CPU board with known good video gen board and SSIO board connected.
The game had no sync but it appeared the game was running.
Sync could be a bad fault to have as its heavily dependent on the PLD’s found on this board and I have yet to reverse them.
Luckily for me I found the last stage before being outputted to the monitor was to blame. The 7404 chip @ location C4 had stuck outputs, replacing this brought the sync back and the board was fine after that.

 Posted by at 7:47 pm
Mar 092014
 

On with the second Spy Hunter repair.
On boot the game displayed a screen of garbage and just sat in watchdog.
Having a look at the ROM’s showed that the EPROM at 6D was a 27128 and it should be a 2764. I pulled this and dumped it to find only half the chip was being used. In order to use a double size EPROM the data needs to be doubled up so this wouldn’t work. I also noticed that this board had the free play ROM’s installed. This needs the EPROMs at 6D and 10D replaced so without the correct ROM’s at both 6D and 10D the game wouldn’t boot.
I installed original ROM’s but the game still did not boot.
Plugging in the Fluke I found I couldn’t get a good read of the EPROMs.
So looking at the schematics I can see the address lines are buffered
spyhunt003

Probing the 74LS244 showed that although I had inputs pulsing away all the outputs were floating.
I removed this and replaced it for a new one and the game now boots.

I had a strange fault here that for some reason I didn’t take a picture of. The game booted but certain tiles from the background were being drawn in the wrong areas, This changed on each reset but I couldn’t understand how this happened.
I pulled all the EPROMs and checked them but they were OK. I pulled the video RAM chip and tested but that was fine too. I did notice the socket for the video RAM was very dodgy
IMAG0085

I replaced this but it made no difference.
As I was struggling to understand why this happened I thought Id check out everything associated with the video RAM chip.
shunt003RAM

The 74LS245 was the first check but this was fine.
The 74LS32 at 2F however had some strange behavior going on. Some of the pins looked to be stuck HIGH but then other times they appeared fine. I pulled the chip and it failed tests.
Replacing this fixed all the graphics faults.

On to the SSIO.
There were two SSIO boards with this set, the first of which works fine so ill write about the second one instead which was not fine.
So with this SSIO attached the game is in constant watchdog.

Here is where I got stuck for a little while. I couldn’t get consistent reads of the EPROMs with the Fluke. I could dump the chips no problem and they are checked out fine. Strangely replacing these chips made the error go away.

The last issue was with the sound itself.
Some of the sounds were missing and there was a constant tone in the background. Replacing the AY-3-8910 @ F7 fixed this up.

Everything is working fine and I can now test all the inputs too.

The SSIO board does not initiate a RESET to the main board at all but as it is directly connected to the main PCB’s address and data bus it has the ability to mess things up if there is a problem in those areas.
Using the Fluke I narrowed it down to one of six chips on the data bus as I found D4 was stuck HIGH. I eventually found the 74LS244 @ E2 was to blame. Replacing this allowed the game to boot again but I had a “Timeout Error”.

 Posted by at 1:56 pm