Aliens repair log #2

 PCB Repair Logs  Comments Off on Aliens repair log #2
Oct 092016
 

Got this Aliens PCB for a repair.Board was not in great shape, quite dirty :

100_9009

When I powered it up I was greeted from this screen repeating in an endless loop sign that board was watchdogging:

fullsizerender

The self-test reported two bad devices, in the case a 1Mbit MASK ROM @C24 contaning program code and a 2018 palette SRAM @E15 :

c24_e15_devices

I dumped the MASK ROM and my programmer warned about a possible damage of the device:

insertion_error_romc24

I programmed an EPROM replacement and at same time replaced the palette SRAM @E15.The error @C24 was cleared but the SRAM was still reported as bad.Probing it revealed its PIN 21 (/OE) was stuck high.I could trace this signal back to pin 6 of a 74LS32 @E13, this was also confirmed by schematics (thanks again to ‘frsj8112’ for providing them)

oe_signal_e15_sram

I desoldered the 74LS32 and it failed when tested out-of-circuit (in gate n°2/pin 6, indeed):

74ls32e13

In this way I could succesfully pass the self-test and enter in game:

Some backgrounds and sprites were corrupted so I launched a MASK ROM check which reported bad devices:

mask_rom_check

Dumping them revealed they were really bad except for the ones @J2 and J8 which were good.I replaced them with 27C400 EPROMs.While I was doing my tests another RAM suddenly failed :

100_9037

I promptly replaced it:

100_9038

After reflowed the two custom ASIC sprites generator ‘051960’ and ‘051937’, MASK ROM check reported all devices as good:

100_9043

Backgrounds were perfect but some sprites were still garbled

Since the sprites MASK ROMs were all good and ruled out the two sprites custom generators as well as connections among them, I went to check the control lines of the MASK ROMs.When I probed the 74LS04 @F13 which generates the /OE signal for the devices @J2 and J8 :

j2_j8_oe__signal

 

my logic compator warned me about a trouble on pin 8:

100_9059

The problem was confimed by the scope (input pin 9 on the left, output pin 8 on the right of the below picture)

74sl04f13_analyzing

I removed the IC and it failed exactly in the pin 8 (the output of gate n°4)

74ls04_failedf13

Fitted a good IC and success!Board completely fixed!It was a long job but it was worth it to save this great classic.Ah, I forgot, obviously the two bad TTLs were from Fujitsu…

 

 Posted by at 11:12 pm

Champion Wrestler PAL dumps completed and tested

 PAL Updates  Comments Off on Champion Wrestler PAL dumps completed and tested
Oct 052016
 

Today ‘coolmod’ sent in dump of a PAL from a Champion Wrestler PCB.Original device was a PAL20L10, I took care of adapting fuse map to a GAL22V10 which he successfully tested back on PCB.Besides, he tested the two dumps we had in database confirming they both work fine.Thanks again to him.

 Posted by at 11:22 pm

Raimais repair log

 PCB Repair Logs  Comments Off on Raimais repair log
Oct 052016
 

Got for a repair this Raimais PCB , an obscure maze game released by Taito in 1988 :

100_8907

Board played fine but sound was totally missing.If I put my fingers  on solderside of the amplifier I could hear some noises, sign that it was still good.Someone replaced invain the YM3016 DAC but this was not the cause.Ruled out a problem is the analog section, I went to check the digital circuitry.Sound CPU is a Z80 with a ROM and a RAM.When I went to check the RAM @IC25 (a Toshiba TMM2063, 6264 compatible,  almost prone to failure in my experience like Fujitsu TTLs) I found irregular activity on some data pins (on the left of the below picture an healthy signal) :

data_lines_comparison

I desoldered the chip:

100_8906

and tested it out-of-circuit where it failed (my programmer went in protection due a possible short , indeed I could measure few Ohms of resistance across VCC and GND pins of the chip)

tmm2063ic25

Fitted a good chip restored the sound.End of job.

 Posted by at 10:48 pm
Oct 052016
 

Received today this Fire Shark PCB for a repair:

100_8995

According to the owner, board would sit on a “OBJECT RAM ERROR”  but instead,  once powered up, the board entered in game but sprites were almost absent,spread on screen in form of lines and garbage:

Like many other Toplan games, also this one uses the ‘FCU-2’ custom ASIC sprites generator which , due its package, is the first thing to check if you have sprites issue:

100_8998

Visually I couldn’t see anything wrong with it but when I tested the soldering of each pin with a needle, I found some loose legs on a side :

100_8996

I promptly reflowed them and sprites were back properly formed:

100_9005_

The other issue reported by owner was that player 2 controls were not responding except for BUTTON#2, COIN and START.The screen of the TEST MODE clearly showed the stuck inputs:

img_7861

I traced these inputs back to a 4.7K Ohm resistor array used as pull-up and I found it was cracked in two:

100_9001

The scope confimed that half of pins were floating and not in high state like they should be :

bad_resistor_arrayra8

I removed the broken resistor array:

100_9002

and, after installed a good one, all the player 2 inputs were correctly working again.Board 100% fixed.

 Posted by at 9:14 pm

Golden Axe 2 – The Revenge of Death Adder repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Golden Axe 2 – The Revenge of Death Adder repair log #1
Oct 042016
 

Got this Golden Axe 2 rom board (here plugged on a working Sega System 32 mother board from an Arabian Fight) with a black screen on boot:

goldenaxe2-1

I borrowed a friend’s working Golden Axe 2 rom board for tests and found out that the security board was the faulty part:

goldenaxe2-2

This board uses an encrypted V60 CPU to prevent conversions by swapping ROMs between boards. For example, there is the exact same board on Arabian Fight but CPUs have different IDs:
– 315-5533-01 for Arabian Fight
– 315-5533-02 for Golden Axe 2

So obviously, putting the security board from Arabian Fight didn’t make the game working, even with the EPROM from Golden Axe 2 plugged in.

ROM, PAL, oscillator and 75HC04AP were tested good but I found a few address lines which looked inactive with the scope. So the faulty chip could be either the CPU @U2 or the RAM @U1. As the encrypted CPU cannot be retrieved anywhere else than another Golden Axe 2, replacing the RAM was my only chance to repair it.

The RAM is a Fujitsu MB8421 (16 kb CMOS).

goldenaxe2-3

I bought a new one (got a MB8421-90L instead of the original MB8421-12L but not a problem as it is a faster 90 ns instead of the original 120 ns), replaced it and luckily the game booted with no other issue. 🙂

goldenaxe2-4