Sky Kid (Namco) help

andrew96

Unfixable? What's that word mean?
Feedback
1 (100%)
Credits
899CR
Hi
can anyone help with this problem i am having with this board??

switch on and the rug pattern

IMG_1318a.jpg


and that's how it stays, BUT it does appear to be running to some extent under that as i can coin it up and get the sound of it coining up!! it is also reading the dip switches as the display invert dip works too, so processor is running as is the sound, it just appears to bet he graphic section that's got the troubles!!

Now on the top of the board is a switch that is not fitted! but if I bridge it display flickers and it displays this!!

IMG_1317a.jpg


So can anyone help on the error code 0 1 1 or where to go on this as it does seem to have custom chips and I am not really sure where to start!!

Hoping someone can help!!

thanks

Andrew
 

Equites

Chief Sheesher®
vacBacker
Feedback
33 (100%)
Credits
3,294CR
Have you tried the 'Service Mode' via the dips to see what you get?

I believe RAM/ROM is checked here.
Equites2013-09-10 00:53:23
 

andrew96

Unfixable? What's that word mean?
Feedback
1 (100%)
Credits
899CR
Hiya

I have turned on dip 1 on bank one which I believe to be the test mode, but it just produces the first rug pattern on boot and that's it, nothing more is seen or shown apart from that. its a bit of a nasty one!!

many thanks for the help

Andrew
 

Zabanitu

User
Credits
330CR
from a PacLand repair log by IronGiant:

Code:
Symptom: Assorted colours wrong
Cure: Two faulty chips the LS298 at location 1P had pin 12 stuck high, and the MB7132 PROM at location 4N was faulty

Symptom: Error 3 0 0 on boot up
Diagnosis: Error indicates that
	the 6116 RAM at location 9P is faulty (and running a RAM test on the
	sprite RAM (2000 to 37FF) on my Fluke 9010A gave an error at address
	2800 BTS 08). Replaced that RAM but the fault remained. So replaced the
	LS245 at location 8P that the aforementioned RAM�s data lines connect to
	 and that fixed the fault
Cure: Replaced faulty LS245 at location 8P

Symptom: Board booting and is playable but a lot of moving garbage
	obscuring and corrupting most of the background and some of the sprites
Diagnosis: Piggy-backed the 6116 RAMS and the LS245's besides them and found that the LS245 at location 8S was faulty
Cure: Replaced faulty LS245 at location 8S

Symptom: Board booting but giving a 5 0 0 error indicating a faulty
	6116 RAM at location 9S and the game displayed some garbage on the
	background
Diagnosis: Decided to double check the error using my
	Fluke 9010A on testing the Video RAM in address range 0 to FFF I was
	getting a decode error for bit 3 and as the RAM warmed up the errors
	became more numerous in all areas associated with the RAM at location 9S
	 � piggy-backing a good 6116 on top of the suspect one made the Fluke
	errors disappear. Removed the suspect RAM and put it into my Wellon
	VP-280 programmer to test it the VP-280 indicated that there was a
	problem with pin 6 of the RAM
Cure: Replaced faulty 6116 RAM at location 9S

Symptom: Board tries to boot but just displays 5 0 5 0 and constantly resets
Cure: Bad outputs on the LS373 at location 2D - replaced

Symptom: Some background graphics were corrupted
Diagnosis: pin 2
	of the 2764 EPROM (PL4 13) at location 6T wasn't giving a reading with
	the logic probe, and on tracing this back it was found that it came from
	 pin 5 of the LS174 at 7P. This is an output pin all inputs were good.
Cure: Replaced the LS174 at 7P

Symptom: Dotted lines vertically down far left side of display and within some sprites
Cure: Replaced faulty 2148 RAM chip at location 3S

Symptom: error 1 0 0 on power up
Cure: Faulty 6116/2016/M58725 RAM at location 9M replaced

Symptom: 2 0 0 appearing on power up then hanging
Cure Bad LS32 at location 5B replaced

Symptom: All sprites moving vertically upwards
Cure: Re-seated Custom 12xx at location 7H

Boot up error codes:

x1 x2 x3

x1 = RAM related
x2 = ROM related
x3 = RAM at 4E ? EG if RAM at 4E is removed or faulty on boot up the error code will be 0 0 1

Examples:

2 0 0 = LS32 at 5B (but would usually be the RAM at 9N)
9 0 0 = customs 2B or 3F removed

RAM Errors:

On boot up, if one of the main cluster of seven 6116 RAMs is faulty
	you will get an error indicating which RAM is at fault; counting top to
	bottom (with the board component side up, edge connector to the right),
	see info below.

So RAM 1 is at location 9M, 2 at 9N, etc. The error code is followed
	by x where x is a number from 1 to 7, RAMs arranged as follows (as
	mentioned, with the board component side up, edge connector to the
	right):

1
2
3
6 4
7 5

An error code of 0 0 1 indicates that the 6116 RAM at location 4E is faulty

Customs:

12xx at 7H sprites, if faulty sprites may scroll upwards
11xx at 6H sprites, if faulty sprites are black blocks
13xx at 9L background scrolling, if faulty background details, etc
04xx at 10M if absent gives error 2 0 0 then 2 0 1

Some EPROMs and PROMs:

PL4-13 removed lots of vertical white lines
PL1-5 removed most text missing
PL2-12 removed most graphics missing
PL1-4 removed some background graphics missing
PL1-3 removed no sprites
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,876CR
Zan has it right - I was about to search for PL repair logs when I saw your first post.

Plus this is PacLand hardware and from time spent working in MAME debug to help my dad fix a recalcitrant PL, I know the POST code is pretty simple to marry up with the onscreen images. If you've got any experience of 6809 assembly (and even if not, pretty much any 8-bit assembly) then you'll probably find stepping through the PL/Skykid boot up in MAME debug helps, especially if you don't get definite answers from the hardware investigation.

cmonkey is also the man who can on this platform, particularly software-wise.

(FWIW our fault turned out to be a dodgy pin connection on a custom. The 6809 was reading RAM which turned out to be a memory mapped register and the iffy pin was masking one bit of the data, so the compare never succeeded. Unless the wind was blowing or a probe was resting on the chip package! I jumped over subroutines in debug that matched the rugs we could see on the board, then single stepped when MAME was showing the hardware-hung screen.)

Anybody think they'd want to read a MAME debug tutorial - something along the lines of using it to augment/narrow down a test bench investigation?
 

Equites

Chief Sheesher®
vacBacker
Feedback
33 (100%)
Credits
3,294CR
trm said:
Anybody think they'd want to read a MAME debug tutorial - something along the lines of using it to augment/narrow down a test bench investigation?

Definitely!

I forgot about Ade, our resident Pac-Land expert.
 

cmonkey

Active member
vacBacker
Feedback
2 (100%)
Credits
1,622CR
Quick code reversal reveals :-

first digit is rom check error code
-----------------------------------
1 0 0 = bad program rom at 6b
2 0 0 = bad program rom at 6c
3 0 0 = bad program rom at 6d

second digit is ram check error code
------------------------------------
0 1 0 = bad ram that covers CPU address space $2000 to $27ff (video ram)
0 2 0 = bad ram that covers CPU address space $2800 to $2fff (video ram)
0 3 0 = bad ram that covers CPU address space $4000 to $47ff (text layer)
0 4 0 = bad ram that covers CPU address space $4800 to $4fff (work ram)
0 5 0 = bad ram that covers CPU address space $5000 to $57ff (work ram)
0 6 0 = bad ram that covers CPU address space $5800 to $5fff (work ram)
0 7 0 = bad ram that covers CPU address space $6800 to $6bff (shared ram with sub CPU)

third digit is sub cpu problem
------------------------------
0 0 1 = sub cpu didn't wake up
 

andrew96

Unfixable? What's that word mean?
Feedback
1 (100%)
Credits
899CR
WOW I have just got in and seen all the replys!!

many thanks to you all! that gives me something to digest! just wished I had the fluke 6809 pod but that one continues to elude me!

many thanks again, will post if I manage to get anywhere with this

Andrew
 

andrew96

Unfixable? What's that word mean?
Feedback
1 (100%)
Credits
899CR
woooohooo!!

was going round data lines on the various ram/rom chips with a scope tonight and found 'weird' signals on ram 8N, so that led back to 7N a 74LS245 fujitsu chip! took it out and tested, bang on faulty!!! so replaced it along with the other 74LS245 fujitsu chips at 7P and 7R (which were good but changed anyway!

powered up and.........
smiley36.gif


IMG_1353a.jpg


then noticed no background!!
smiley6.gif


game coins and plays! so getting there!! just the background to sort now

IMG_1356a.jpg


andrew962013-09-23 00:10:01
 
Top