What's new

CPS-1.5: Punisher Conversion

AlxUnderBase said:
@Sbarb18 i think you didnt did exactly what djsheep did . Try to use the exactly eproms and see if will powers us (at least , 4096 aren’t same with 400’s or mx4100)🤷🏻
Click to expand...
My B-Board is a JEDEC Type so it takes different mask rom chips than his MASK Type B-Board.

P.S. I realized I didn’t make it clear my board is JEDEC, so I made a note in a previous post.
 
Last edited:
I was looking into the board revisions. My B-Board is a 91634B-2. I found the following under punisherj which also uses this board:

ROM_REGION( 0x400000, "gfx", 0 )
ROM_LOAD64_WORD( "ps_01.3a", 0x000000, 0x80000, CRC(77b7ccab) SHA1(e08e5d55a79e4c0c8ca819d6d7d2a14f753c6ec3) ) // == ps-1m.3a
ROM_LOAD64_WORD( "ps_02.4a", 0x000002, 0x80000, CRC(0122720b) SHA1(5f0d3097e097f64106048156fbb0d343fe78fffa) ) // == ps-3m.5a
ROM_LOAD64_WORD( "ps_03.5a", 0x000004, 0x80000, CRC(64fa58d4) SHA1(d4a774285ed15273195b6b26d2965ce370e54e73) ) // == ps-2m.4a
ROM_LOAD64_WORD( "ps_04.6a", 0x000006, 0x80000, CRC(60da42c8) SHA1(95eec4a58d9628a2d9764951dd8dc11e4860a899) ) // == ps-4m.6a
ROM_LOAD64_WORD( "ps_05.7a", 0x200000, 0x80000, CRC(c54ea839) SHA1(0733f37329edd9d0cace1319a7544b40aa7ecb0b) ) // == ps-5m.7a
ROM_LOAD64_WORD( "ps_06.8a", 0x200002, 0x80000, CRC(04c5acbd) SHA1(fddc94b0f36d4d22d7c357856ae15b7514c342d3) ) // == ps-7m.9a
ROM_LOAD64_WORD( "ps_07.9a", 0x200004, 0x80000, CRC(a544f4cc) SHA1(9552df8934ba25f19a22f2e07783712d8c8ef03c) ) // == ps-6m.8a
ROM_LOAD64_WORD( "ps_08.10a", 0x200006, 0x80000, CRC(8f02f436) SHA1(a2f0ebb7e9593469c7b843f8962a66f3d77f79e5) ) // == ps-8m.10a

If using the world romset, does this mean the graphics chips preceded by "//==" go in the position of the ones in quotes? Sorry if this is a dumb question. I'm trying to troubleshoot.

EDIT: I reprogrammed the GAL chips, and now I get a quick flash of graphics on the screen when powering on. I don’t know if this is a step in the right direction or not…
 

Attachments

  • IMG_3670.jpeg
    IMG_3670.jpeg
    319.8 KB · Views: 6
Last edited:
I’m still not the best at reading MAME, perhaps someone else can lend a hand.

Also checking that you have an openkey for kabuki and the c-board installed, set correctly and that the battery is removed from your B-board?
 
I reckon it’s something to do with the wrong chips in the wrong places. Or wrong programming.

Hopefully someone can chime in that can read this one better. Don’t worry. Will get it going and be good to document the issue and fix here for others.
 
Sbarb18 said:
I was looking into the board revisions. My B-Board is a 91634B-2. I found the following under punisherj which also uses this board:

ROM_REGION( 0x400000, "gfx", 0 )
ROM_LOAD64_WORD( "ps_01.3a", 0x000000, 0x80000, CRC(77b7ccab) SHA1(e08e5d55a79e4c0c8ca819d6d7d2a14f753c6ec3) ) // == ps-1m.3a
ROM_LOAD64_WORD( "ps_02.4a", 0x000002, 0x80000, CRC(0122720b) SHA1(5f0d3097e097f64106048156fbb0d343fe78fffa) ) // == ps-3m.5a
ROM_LOAD64_WORD( "ps_03.5a", 0x000004, 0x80000, CRC(64fa58d4) SHA1(d4a774285ed15273195b6b26d2965ce370e54e73) ) // == ps-2m.4a
ROM_LOAD64_WORD( "ps_04.6a", 0x000006, 0x80000, CRC(60da42c8) SHA1(95eec4a58d9628a2d9764951dd8dc11e4860a899) ) // == ps-4m.6a
ROM_LOAD64_WORD( "ps_05.7a", 0x200000, 0x80000, CRC(c54ea839) SHA1(0733f37329edd9d0cace1319a7544b40aa7ecb0b) ) // == ps-5m.7a
ROM_LOAD64_WORD( "ps_06.8a", 0x200002, 0x80000, CRC(04c5acbd) SHA1(fddc94b0f36d4d22d7c357856ae15b7514c342d3) ) // == ps-7m.9a
ROM_LOAD64_WORD( "ps_07.9a", 0x200004, 0x80000, CRC(a544f4cc) SHA1(9552df8934ba25f19a22f2e07783712d8c8ef03c) ) // == ps-6m.8a
ROM_LOAD64_WORD( "ps_08.10a", 0x200006, 0x80000, CRC(8f02f436) SHA1(a2f0ebb7e9593469c7b843f8962a66f3d77f79e5) ) // == ps-8m.10a

If using the world romset, does this mean the graphics chips preceded by "//==" go in the position of the ones in quotes? Sorry if this is a dumb question. I'm trying to troubleshoot.

EDIT: I reprogrammed the GAL chips, and now I get a quick flash of graphics on the screen when powering on. I don’t know if this is a step in the right direction or not…
Click to expand...
The comments on all those entries in mame are just saying the roms from that punisherj romset are the same crc/data as another romset. ie:

from punisher romset
ROM_LOAD64_WORD( "ps-3m.5a", 0x000002, 0x80000, CRC(0122720b) SHA1(5f0d3097e097f64106048156fbb0d343fe78fffa) )

from punisherj romset
ROM_LOAD64_WORD( "ps_02.4a", 0x000002, 0x80000, CRC(0122720b) SHA1(5f0d3097e097f64106048156fbb0d343fe78fffa) ) // == ps-3m.5a

Since you burned these roms

ps-1m.3a
ps-2m.4a
ps-3m.5a
ps-4m.6a
ps-5m.7a
ps-6m.8a
ps-7m.9a
ps-8m.10a

The punisherj romset is saying you should actually install them in this order in your 91634B-2 board

ps-1m
ps-3m
ps-2m
ps-4m
ps-5m
ps-7m
ps-6m
ps-8m

Curious if you get any sound if you do an insert coin? having the graphics roms in the wrong order shouldn't prevent the program code from running.

A black screen can be caused by there being something wrong related to the kabuki cpu or qsound code. One of the first things the game code does is go into a loop waiting for the kabuki to write a specific value to a memory location that is shared between the main cpu and the kabuki. If that never happens the game will be stuck in that loop causing the black screen.
 
Thank you. This helps a great deal. I’ll try reprogramming the qsound chip in the morning and post my results
 
After reprograming the q-sound code chip (ps_q.5k) there was still no change. I tried reprogramming the GAL chips as well with no luck. Maybe I have bad chips. Its just weird because I've verified multiple times and reseated multiple times.

At this point I would love if someone might look at my boards and chips for me to find a solution. If anyone is local to Bucks County, PA, or I can even ship. I really want to get this to work.

Thanks.
 
@ack might be able to chime in. But the new revision of the openkey-cps1 holds reset for longer.

I had an issue with the Punisher convert on a Supergun where I had to reset a few times before it would write the key.

Can you try another Supergun or cab perhaps?

Is your kabuki in the openkey in the right orientation? Kabuki’s have been known to die. I had one once that was gone. Can you try use the one from your other working set (change the dips for punisher).
 
I don't have another supergun or cab to test it out on. I tested the Tenchi wo Kurau II and that still runs just fine, so the Kabuki should be good. I'm going to double check my program roms and the others on the q-sound board just in case I have bad dumps or something.
 
@djsheep Do you have the CRC codes for your 22 and 23 slot programs? I want to check it against mine that I interleaved and concatenated. Thank you.
 
My suggestion would be to burn the punisherj 21/22/23 roms and test with them. If that fixes the issue you know the problem is with your 22/23 roms, if you still get a black screen then its likely pointing at an issue with the kabuki/qsound roms or maybe the GAL on the D board..
 
ack said:
My suggestion would be to burn the punisherj 21/22/23 roms and test with them. If that fixes the issue you know the problem is with your 22/23 roms, if you still get a black screen then its likely pointing at an issue with the kabuki/qsound roms or maybe the GAL on the D board..
Click to expand...
I’ll give the punisherj program roms a try. I’ll report back.
 
ack said:
My suggestion would be to burn the punisherj 21/22/23 roms and test with them. If that fixes the issue you know the problem is with your 22/23 roms, if you still get a black screen then its likely pointing at an issue with the kabuki/qsound roms or maybe the GAL on the D board..
Click to expand...
I programmed the psj_22 and psj_23 roms and still no change. I reprogrammed ps_q1 through ps_q4 and no change.

I’m ordering new GAL16V8 chips to see if this changes anything. I have suspected they might be the problem, but because the verification was successful I thought it might be something else. Will report back once the chips are in and I test them.
 
Sbarb18 said:
I’m ordering new GAL16V8 chips to see if this changes anything. I have suspected they might be the problem, but because the verification was successful I thought it might be something else. Will report back once the chips are in and I test them.
Click to expand...
On JammaArcade is a tool , called Porchy tool called BINman . Try that tool to compare your programmed chips (of course , after you save as from the software of the programmer what is writed on the chips , gals , eproms) . This way, you can see if the files are the same as in MAME set 🤷🏻
 
AlxUnderBase said:
On JammaArcade is a tool , called Porchy tool called BINman . Try that tool to compare your programmed chips (of course , after you save as from the software of the programmer what is writed on the chips , gals , eproms) . This way, you can see if the files are the same as in MAME set 🤷🏻
Click to expand...
I’ll definitely do that. Thanks!
 
You must log in or register to reply here.
Back
Top