Corrado Tomaselli

No background in electronics. Learned everything by reading pdf books and expecially Video game logic Vol 1 by Atari and in general early Atari and Williams arcade manuals

Pacland repair log#2

 PCB Repair Logs, Repair Logs  Comments Off on Pacland repair log#2
Oct 282018
 

Received a pacland board for a repair which was stuck with a  0 2 0 error at boot.

Normally the middle digit means it’s an program rom error and infact the second prg rom @8D had no sticker  and I immediately checked it.

 

Romident showed it was a Pacland midway rom, but the other prg roms belonged to the japanes new version.

After burning the correct 2nd rom from the jap set I was welcomed with this screen which is the service one.

The dipswitches were all set OFF and after verifying they were working correctly I decided to change all the FUJITSU 74LS257 near them which had dead outputs infact.

In the end all the Fujistsu chips has been changed because faulty: @1L, 2L and 2J!

 

With good ones changed the game finally booted but the palette was very tinted and the sprites were corrupted:

 

Verifying the sprites roms 8,9,10 and 11 these were a mess of different revisions, so using a broken pacland I put the matching roms from the new japanese set

Still the sprites were corrupted and eventually I found a bad 74ls86 ( again Fujitsu) @10F

 

With good one installed I got finally good sprites but still the palette was tinted:

 

I proceeded on the colour prom section and found that the chip PL1-2 had some outputs dead

 

Using one from another Pacland board fixed the game 100%

 

 

 

NBA Jam repair log

 PCB Repair Logs, Repair Logs  Comments Off on NBA Jam repair log
Sep 042018
 

Bought this game for personal collection with a problem on the RED colour which was completely missing.

Checking the schematics there are some 74541 chips which are sending the colour bits to a resistor network for Dac conversion. The one on the red colour @UC4 was correctly working so I checked the 74ls07@UA4  involved in the blanking circuit.

Pin 2 was always below 0.5V  and muted the total red colour

 

After changing it I restored the red colour

Rastan repair log #6

 PCB Repair Logs  Comments Off on Rastan repair log #6
Sep 042018
 

Got another Rastan for a repair.

This one had some vertical black lines and some text was wrong

Piggybacking sram IC2 and IC4 with a good ram brought some better changings so I decided to desolder them and test out of circuit

Both were reported bad

Game was 100% fixed

Mag Max repair log

 Repair Logs  Comments Off on Mag Max repair log
Jul 112018
 

This game had been in my collection for about 14 years. I decided to make a play but the game displayed a RAM NG text and didn’t boot

 

After checking the schematics I decided to prove rams and some devices but the signals were healthy

Thanks to Kale from mame team, I discovered that the game does a simple check but decrementing some values in ram and read them back.

Therefore I decided to desolder the program srams to check if they were good. The game has only 2x 2016 toshiba rams.

This brand is known to be not really reliable in comparison to others

After checking the first one I got confirmation that it was bad

I resoldered it and this time the game booted with RAM NG briefly shown and behaved strangely. You couldn’t shoot and parts of the scrolling was repeating.

I decided to desolder also the second one since the game still complained about the ram.

Also the second one was bad!

After changing also this one, the game was 100% fixed

 

Rolling Thunder 2 repair log

 PCB Repair Logs, Repair Logs  Comments Off on Rolling Thunder 2 repair log
Jul 112018
 

Got this game for a repair.

At boot it displayed the following:

Using Mame source code with the memory map I could narrow down that RAM0044Eo20 was the colour BLUE ram

Desoldering it I could confirm it was bad

After replacing it I still got:

30TIP, 31TIP and 33TIP error

After discussing with Charles MacDonald he pointed me to the DUAL PORT RAM.

It checks if the last entry in RAM (460FFF) is zero, if so that’s an error (should be non-zero)
Then it checks if 460FF contains byte 6B, if it doesn’t that’s an error too

I started to probe around the dual port ram

Until I found a stuck bit on the Left side of the Dual port ram which came from a 74HC175.

After changing it, the game booted but still with TIP33 error which could be erased by pushing the start button.

TIP33 is the error related to the EEPROM which is not inizialized correctly or contain some corrupted data. Normally you inizialize it only one time but everytime

started the pcb, I got this error and offcourse all the dipswitch settings couldn’t be saved correctly.

To cut a long story short, some smart guy changed the original EEPROM with a normal 8k SRAM!

I took a spare from a faulty final lap 3  and I could finally fix 100% the game