Black Tiger NOW FIXED!!!

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Right one thing at a time I know, but when I moved my garage around I had to move my boards around, so I seem to be getting a couple of faulty ones!
smiley7.gif


Just put my Black Tiger marquee in one of my jamma cabs and thought lets have a blast.

First I found one of the ribbon edge connecter sockets needed a reflow as everytime I breathed near it the board was trying to reset. And look at the sprites!

So reflowed the connector, that's all good now but it didn't cure the sprites.

I have very limited knowledge but I do listen, just from what I read from you guys and watching others, reading repair logs etc... Would I be right in saying the first thing to look at would be the character sprite ram/rom? Or what say you?

If so which chip/rom is it???

Voltage is spot on at 5v and it's the same in two different cabs and on my test rig.

Please see video and pics...

Any advice of where to start and things to try, I have a programmer and a logic probe + multimeter.

Could I also ask for ultra idiots guide, like even which pin to probe and why and what the logic probe should do etc....
smiley9.gif
Sorry!


Black_Tiger_11.08.10.jpg
Black_Tiger_11.08.10_1.jpg
Black_Tiger_11.08.10_2.jpg
Black_Tiger_11.08.10_3.jpg
Black_Tiger_11.08.10_4.jpg
Black_Tiger_11.08.10_5.jpg

paulcan692010-08-25 15:38:13
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
If this has happened after moving the board(s) around then the first thing I would look out for before getting too distracted with anything else is to give all the RAMs and ROMs a good press down to make sure nothing has worked it's way a little loose.

If you have access to schematics then obviously concentrate on the sprite ROMs and RAMs but I don't know if they're even in circulation as I've never looked at Black Tiger - looks too modern for my tastes
smiley36.gif
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
I did give them all a press down, no change.

I know it is a bit new, but give it a go, it's a great platformer.

schems hmmm anyone? I'm not sure if they are out there?

This board has been repaired before, Phil done it for me about 1 to 1 and a half years ago, the board was in a bad state, he said a few tracks were bad and had to do a lot of work to it.

It has some patch wires etc... As it was getting late when I discovered this I shall have a closer look tomorrow (Huh tonight now!) Make sure it's not something simple.

I was so careful when I moved all the boards, but sometimes they just don't like it do they?

I shall report back!

Thanks

paulcan692010-08-25 00:54:03
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Nah, boards shouldn't generally be that picky. Ok so you don't want to be dropping them but you shouldn't need to treat them like they're made of porcelain or anything. If you've already already made sure nothing's got dislodged then it genuinely sounds like something's gone down. It happens all too often unfortunately
smiley6.gif


I shall see what I can find "in my detailed files" as they say. Ok, so as Bazfish would say!
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Hmm, I only have the instruction manual and that says licensed from Capcom which more than likely rules out schematics which is a pain in the arse. Someone might have them though.
 
G

Guests

Guest
have you tried test mode? switch 8 on bank B according to the manual i have
 

DanP

Administrator
Staff member
vacBacker
Feedback
5 (100%)
Credits
2,232CR
Yeah I second what AnDyC says, looking in MAME theres a step in the test that shows the sprites individually.

Secondly rather than just press down on the socketed chips it might be worth removing them, cleaning the the legs (carefully) with a pencil rubber and reseating them.

Finally check that all the track repair wires are still working ok, these are the most likely things to come loose when moving boards around if they aren't glued.

HTH

Cheers,

Dan
 

karlcdoe

Active member
vacBacker
Feedback
8 (100%)
Credits
887CR
As ever, check for chips that are physically hot, thats how I fixed my last board, nearly took the skin off my finger it was so hot. Secondly if there are no schematics it's worth continuing to fish to see if anyone has any repair logs indicating what does what. I don't have an eprom reader but they are a good idea as you can then rule out the roms if they're socketed. After that I'd get creative, you need to rule out cetain parts of the board, getting rid of some the sound stage isn't too hard, generally I'd look for traces from the sound amp to the nearest cips, probably a z80 for sound and some logic and rams. You could go for the classic nasty hack of identifying the ram chips and then grounding the data address lines to see if you can create a 'similar' fault, I think that might pin it down to a section of the circuitry but obviously carries some risk. I've also identified some boards by looking at some of the mame dev notes as they tend to identify major components, RAM, CPUs, etc.

K
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
AnDyC said:
have you tried test mode? switch 8 on bank B according to the manual i have

Good call Mr C, I didn't realise Black Tiger had a test mode.

Unfortunately (or not as it maybe???) it came back as OK, OK, OK for vram etc... all tests OK.

Plugged it in tonight and now I have jail bars as well, hmmm nice!

OK will have a damn good look at it this weekend, do all of the above and report back

Thanks all of you for the advice, I will be back with this one as I love this game.

Ta

Paul.
paulcan692010-08-12 17:55:23
 
G

Guests

Guest
if the fault has changed to jail bars, it might just be a ribbon cable, thats dirty/loose take them all off and refit them
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
It looks to me as though this is going to be an issue with the sprite multiplexing. This is when the sprites are "stamped" on top of the background image to produce the final image which is then rasterised. At some points it looks as though the mask data (data used to indicate which parts of the sprites are visible and which are transparent and should let the background show through) is actually being rasterised.

I'd be suspecting things like '245s (buffers which gate the ROMs on and off the cpu bus), '166 (shift registers, sometimes used to mux the sprites into the data stream that makes up the display) and '139s (multiplexers which control whether the data should be read from the background image RAM or sprite RAM) around the sprite data. You should be able to tell from MAWS what ROMS hold the sprites. In fact, I've just gone and looked and found this:

ROM_REGION( 0x40000, "gfx3", 0 )

Code:
	ROM_LOAD( "[color="#FF0000"]bd-08.5a[/color]",   0x00000, 0x10000, CRC(e2f17438) SHA1(3e5fdae07d40febedc59c7c7c4d9c6f0d72b58b5) )	/* sprites */
		ROM_LOAD( "[color="#FF0000"]bd-07.4a[/color]",   0x10000, 0x10000, CRC(5fccbd27) SHA1(33c55aa9c12b3121ca5c3b4c39a9b152b6946461) )
		ROM_LOAD( "[color="#FF0000"]bd-10.9a[/color]",   0x20000, 0x10000, CRC(fc33ccc6) SHA1(d492626a88565c2626f98ecb1d74535f1ad68e4c) )
		ROM_LOAD( "[color="#FF0000"]bd-09.8a[/color]",   0x30000, 0x10000, CRC(f449de01) SHA1(f6b40e9eb2471b89c42ab84f4214295d284db0c3) )
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]The key data is that in red - those should match up with ROM labels.[/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"](I got this data by googling MAWS, then entering the game name, following the link at the top for the game, clicking the link for the game driver which will be a filename ending in .c and then clicking the source: link on the final page. Scroll down and you can see the memory map and which ROMs are loaded into what memory addresses. Happily, most of the MAME drivers indicate what type of data is concerned.) All of that led me to [/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"][url="http://maws.mameworld.info/maws/mamesrc/src/mame/drivers/blktiger.c"]http://maws.mameworld.info/maws/mamesrc/src/mame/drivers/blktiger.c[/url][/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]So, I'd be looking at any chips of those type which are nearby the above ROMs. You might have to use a continuity tester (or visual trace) to trace the data lines from the sprite roms to the logic as they could be on separate boards. [/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]Best bet is to google the datasheets for those 3 logic chips and have a read, then with the datasheets in hand use your logic probe to test each pin. It'll start becoming obvious where you should expect data (pulses on the probe) and give you clues when you don't see it, either a static high or low. In the datasheets the symbol / means active low. For example, /RESET is active low, so in normal use the game will dip it low at startup, then hold the line high unless it needs to reset the game.[/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]Just one caveat to mention - I'm on a conf call whilst writing this and I occasionally have to speak so I may have got the specific 74 series IC numbers wrong as I wrote them off the top of my head, plus various manufacturers accomplished this in different ways using different logic. Regardless, you know which ROMs hold the sprite data so locate them, locate the logic which is attached to them, get the datasheets and get probing to see what activity you can find. Sadly, this is probably not going to be a good starter board as having schematics (and a single PCB) would make things a lot simpler for people to help. But let's give it a bash first :)[/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]tim[/font]
Code:
[font="Verdana, Arial, Helvetica, sans-serif"]PS Obviously, follow the other suggestions about checking that everything is seated cleanly and that you've not got oxide coatings on the ribbon cables or IC legs first before you start in-depth work like this. I've fixed a surprising number of faulty boards just by reinserting interboard connectors a few times to scrub the oxide coating.[/font]
Code:
PPS I'm currently writing some docs on how to start fixing things and have written some of the section that deals with sprites e.g. what they are, why they're used and so on. If I get time to polish it up I'll post that as knowing what a sprite is and why they're used is useful background. In very short summary, a sprite is data that is added to the bit stream that makes up the video just before it's converted into RGB signals. This means that if you disabled the sprites, you'd just see the background elements of the gfx.
Code:
The reason sprites are useful is because the sprite data is merged with the background and then sent to the raster (the display producing hardware) so having a sprite on the screen means it's[b] not overwriting any of the RAM which holds the background image[/b]. This is beneficial because when you move a sprite, you don't have to replace the bits of background that were obscured by the sprite in its previous position as the sprite data was never "stamped" into the RAM holding the background image.
Code:
Imagine a game without sprites - when you moved your character you'd leave a trail of images behind. That would be unacceptable, so the game hardware would need to look where the character had been, rebuild the background image and then stamp the character into RAM at the new location. As soon as you move, it has to recheck the background image and rebuild it. This takes lots of CPU cycles which is bad.
Code:
Whereas using sprites all you need to do is enable the rasteriser (the bit which reads the video RAM and generates the image for the screen) to know when a sprite should be drawn. When it knows a sprite is to be drawn, the rasteriser flicks from reading the background image RAM to reading the sprite RAM, so the sprite appears in the video stream.
Code:
On the next frame, if you've moved the sprite you don't have to touch-up the background image RAM, you just tell the rasteriser that the sprite is now to be drawn at new coordinates. Blammo! Loads of CPU cycles saved and a lot less juggling of image data.
Code:
Finally, this is a terribly condensed explanation of what sprites are and how they work, but hopefully it's good enough to explain the concept.
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Wow thanks, that does explain loads.

That totally makes sense regarding how sprites are drawn, instantly you have painted a picture which I can see in my mind now, which helps me understand how and why a fault occurs.

That gives me a great starting point.

I will get this board out on Saturday and cover everything I can from all of the above

I'm just getting my head around maws at this exact moment.

paulcan692010-08-12 20:05:43
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
Any update on this young man? I don't seem to have time to do much fixing of my own so I have to do it vicariously through others
smiley4.gif
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
smiley9.gif
I really wanted time with this at the weekend, I've even been playing Black Tiger in my lunch break on my PSP to sooth my craving for it until I get this board fixed.

Had a crew of fellow arcade heads over Fri night and they stayed till 4am, then Sat busy doing our garden, then a BBQ with a few people over who again stayed on the cabs until 2am, Sun again very busy, last night I was knackered and tonight I drove 12 miles to fix a dear old ladies computer then 12 miles home just got back and although I want to fix it now I haven't got it in me.

Not making excuses....but I am making excuses aren't I?

I promise tomorrow evening I will spend some time on this and get you the screen dump of the failed chip with the other tech thread I have on the go.

Please don't think I don't want the help, or I'm never gonna do anything about it, just a mad week that's all, I love black tiger I had just put the marquee in the cab and was itching to play it then this happens.

I think I'll be home at about 6:30pm tomorrow, I will go into the garage get my test rig and monitor bring it all indoors with the Black Tiger board get my soldering iron etc... set it all up in our spare room then I have warmth, good lighting and tea (provided by the mrs) then I stand a chance!

I have earn't a little bit of bonus this month, I will buy a wellon vp280 to check TTL and RAM, and also I will buy a Aoyue 474 desoldering station as I suck at removing chips myself, then I think I can really do some pcb damage, I mean repair.
paulcan692010-08-18 11:03:51
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
You star, ok that's very good to know!! (Would like an original, just let me see if it's anything easy first, if not may have one from you and then try to fix this one... then sell the fixed one!)
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Well ok, had a good look at what you said as a starting point,

BD07, BD08, BD09 and BD10 all live in a row on a Capcom Black Tiger board and control sprites as you say.

Pulled them one at a time read them on the Galep4 then use Winromident to compare to the roms on the net for Black Tiger.

Interestingly enough BD08 came back as not found!! + the other 3 all ok, exactly the same as what Winromident expects.

Hmmm, so I pulled out BD08 and booted the board, believe it or not the fault gets better.
smiley17.gif


i.e instead of the sprites being messed up with a cube around any sprite (player, enemy, collectable item) the sprites all go perfect other than they are then transparent and the colours are wrong. I think that may just be progress!!

Compare to first pics in the post...

BT18.08.10.jpg
BT18.08.10_1.jpg
BT18.08.10_2.jpg


Well I'm going to try to prog the rom with the copy of BD08.bin from the internet, am I right in saying that's not actually illegal as I own the board?

We shall see what happens.

Lastly again embrassing noob question, this eprom has no window, I take it that it's a eeprom which means I can erase it electronically via Galep32 software?? Can anyone confirm this just before I try it?

Many thanks all!!!!
smiley27.gif

paulcan692010-08-18 21:28:40
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
Hi dude,

Don't worry about the legal aspects of burning ROMs. Nobody is going to come after you, but as far as the law goes you've probably got the right as you own the PCB.

The chip is very unlikely to be an EEPROM as they're expensive and would have been INCREDIBLY expensive when the board was fabbed. It's either a mask ROM (which means the data is printed onto silicon like other chips are made) or a OTP - One Time Programmable EPROM. Much more likely to be an OTP. These are identical to a normal EPROM, but without the window so you can't expose it to UV to wipe it. They used OTPs as they're cheaper due to the lack of a quartz window.

Also, I'd be dubious about trusting winromident as I suspect it's database of ROM hashes is very out of date. Romidenting works by reading every byte of data and performing a mathematical operation (aka hash) on the data. You are essentially guaranteed that no two sets of input data will produce the same hash output, even if the input differs by a single bit. So the romident hashes the data in the EPROM then compares to a known list. The problem arises when this known list is out of date and doesn't include your variant of the board so it shows up as unknown.

Far better is to grab the mame dos executable from the mamedev.org site, stick it in a folder on your PC and then open a command prompt, change directory to the folder where mame.exe is stored and then run "mame -romident MYFILE.BIN". Each version of MAME includes the latest known hashes, so you're getting a good chance of identifying a variant as the actual game, rather than as a bad ROM.

I've got to finish some crap at work now, but I'll be back later on to comment on the results of pulling the EPROM, but for now I'd strongly suggest a) not trying to erase the OTP EPROM ;) and b) grabbing mame and trying the romident I suggested above.

cheers
tim
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Ok how do I erase this chip?? Does it still need time in the eraser even without a window in it??

If I try to blank it in Galep32 it says error.

If I try to write to it, again error, I can screen dump the pics if someone wants to see?

Thanks for any advice, I really need to learn how to use this programmer so I'm ok with what I'm trying but I guess this is the fastest way I will learn, head on into a brick wall.

paulcan692010-08-18 21:52:33
 
Top