Juno First repair log #3

 PCB Repair Logs, Repair Logs  Comments Off on Juno First repair log #3
Jun 262014
 

Third repair log from the batch of Juno First boards.
On power up the board was completely dead. No clocks were present on the CPU or many other IC’s.
As this is a bootleg board the available schematics do not fully apply and the clock circuit is normally handled by custom chips so this was a bit of a learning experience.
To help in dealing with this problem I started making my own schematics up.
junobl

Using a logic probe I could see that the outputs of the 74LS161 @ H14 were all HIGH. As there is no clock present to this chip it should not have counted anything at this point and they should all be LOW. This meant to the board was booting up in an incorrect state and the clock circuit was never starting.
I desoldered and replaced the offending 161 chip.
IMAG0616

The clocks were now all present but I just got a static blue screen and the watchdog was constantly resetting the system.
Using my in circuit Arduino tester I knew the ROMs could all be read correctly by the CPU. I also knew all the program RAMs were fine.
Replacing the 6809 CPU allowed the game to boot properly.

Next problem was the sound or lack of it.
The sound CPU is a good old Z80 so I fitted the Fluke and did a ROM check. This reported back an incorrect signature and when I removed the ROM I see this
IMAG0618

The VCC pin was missing. I soldered a new pin onto this and this board is fully fixed.

The last bootleg board has been a major pain and at this point in time I have admitted defeat with it. I have also been harvesting parts from it to fix the others so it will be written off.

Juno First repair log #2

 PCB Repair Logs, Repair Logs  Comments Off on Juno First repair log #2
Jun 152014
 

So here is the second repair log.
Pretty simple this one but I never took any pictures of the actual fault so Ive taken a snapshot of the event in MAME to show it.

The game plays as normal but when the blue ball enemies spawn into the game the froze up on screen and did nothing as circled in red in the picture below.
juno2

On my visual inspection I noticed a 1K pull up resistor array next to the bank of 4116 RAM chips what cracked in half.
juno2-1

Replacing this fixed the fault.

I did initially think there was another fault as the ship movement in attract mode seemed a bit strange but after checking in MAME this is a characteristic of the non Gottlieb version. In the Gottlieb version this behavior is not present.

Jun 062014
 

This is hopefully one of five Juno First repair logs.
Thanks (I think) to muddymusic I have a stack of these needing repaired. There are two originals and three bootlegs altogether and decided to make a start on the originals first.

This one booted to an unsynced red picture.

Looking at the schematics I could see that the sync is generated by custom chip 082 at location EF13 on the bottom PCB.
Swapping this chip with the one from the other board set brought the sync back. That’s bad news for original board set #2.

So now I just had a red screen with nothing going on.
It was at this point that I learned this hardware uses a custom 6809 CPU known as Konami-1. I was originally going to try and borrow a 6809 pod for the Fluke but that put a swift end it that idea.
Now’s the perfect time to use my beloved Arduino again.
By hooking it up to the address, data, RW, BA and BS lines I wrote a program that would read the program ROM’s back and display the data as well as a bitsum for the ROM.
It worked really well and found my second issue.

This is the original HEX file

and here is what I was actually reading on the board

You can see that bits 0 and 1 are always on.

So the 74LS245 at location D7 on the lower PCB had a two stuck pins on D0 and D1.

Replacing this enabled me to read all the program ROM’s correctly.
I had at this point wanted to be able to test RAM too but due to the timings required and not knowing how those custom chips worked I left it alone.

So now I have a booting game but all the sprites and title screen graphics are missing.

First thing I did was see if I could replicate the fault in MAME.
By creating empty files to replace ROM’s 7C, 7D and 7E on the top PCB I got the exact fault.

Checking those EPROM’s with the probe revealed that none of the chips were ever being enabled.
Following the schematics back to where the ROM selection lines are generated I came to a 74LS273 at location 6D on the upper PCB. Pin 11 is the clock pin for this chip and I would expect it to be pulsing but it was stuck HIGH. Following the /SSEL line back to the lower PCB led me to a 74LS138 at location I6.

This had pulsing inputs but either stuck HIGH outputs or floating pins. Replacing this chip gave me the graphics back.

That’s one down.