SnakeGrunger
Professional
I get the same thing as well.
I just tried this.Ok, ok, ok. Found an additional write to the KeyCus when EEPROM isn't initialised:
filedropper.com/nr2mpru_3
I see a starfield for a second, then the "version mismatch" message for a split second and then the board reboots, and it gets stuck in a boot loop like this.
I can actually coin it up and start a game while the star field is displayed if I'm fast enough but then it just resets. I can't get it to go into test mode though.
Here comes the pain of remote troubleshooting again...I get the same thing as well.
if you're willing to do the work to patch these games then I'm more than happy to do the work testing themSorry for wasting your time guys...
I do. I was quite annoyed to see the patch didn't work when protection seemed easy to bypass. I guess this is because a lot is going on regarding hardware part which isn't understood/needed/emulated in MAME.if you're willing to do the work to patch these games then I'm more than happy to do the work testing them
I get the same.I can add credits or enter the service menu for a few frames until it reboots again.
I'm honestly surprised you found the time to work on this at all, I thought you were taking a few months off.Anyway, this weekend is the first with 2 days off (I've worked the past 5 Saturdays) but I'm on-call and have to support my customer, first remotely with my computer and then on site if I can't fix the issue. Being basically on my laptop the whole day I thought I could spent some time to fix this patch between 2 calls.
According to what I've found in MAME I'd say it clears by itself if not properly initialised.Seems still stuck in a loop. I can add credits or enter the service menu for a few frames until it reboots again.
Could it be that I have not cleared the nvram ? How do you re-initialize it ?
I'm stuck in front of my computer...I'm honestly surprised you found the time to work on this at all, I thought you were taking a few months off.
I'm using KEYCUS C434 which is from MAME ROM sws97 (Super World Stadium 97)Can you guys please give me what donor game you used (MAME romset name).
The number written to RNG varies from KeyCus to KeyCus so maybe the conversion needs to be adapted for each donor.
I've patched all accesses to the KeyCus in MAME and it works perfectly so I think there's something going on with the hardware part.it's not a matter of jumpers, the patched code is simply not good.I have two ROM sets, one requires the KEY CUSTOM IC from Point Blank and the other runs with no KEY CUSTOM installed and they both works fine.But I can't release them for obvious reasons (neither sell them so don't ask in private)
MAME is NOT a good way to test conversions since it's only emulation which, as name tells, can't reproduce hardware 100% faithfulI've patched all accesses to the KeyCus in MAME and it works perfectly so I think there's something going on with the hardware part.There seems to be a link between the KeyCus and the watchdog, that would mean conversions made without any KeyCus installed rely on hardware modding.it's not a matter of jumpers, the patched code is simply not good.I have two ROM sets, one requires the KEY CUSTOM IC from Point Blank and the other runs with no KEY CUSTOM installed and they both works fine.But I can't release them for obvious reasons (neither sell them so don't ask in private)
I've done dozens of tests, disabling RNG, running patched ROMs with a different romset, disabling KeyCus area, etc. And I was never able to fault the code in MAME.
With the hardware in my hands it would have been solved quickly.MAME is NOT a good way to test conversions since it's only emulation which, as name tells, can't reproduce hardware 100% faithful Your patched code is bugged, that's all.The one I have has been not prepared by me but it works perfectly.
I pulled the KEYCUS and it boots without restarting! I'm able to coin up and play.@twistedsymphony can you take a video with the KeyCus installed and then with no KeyCus?
The KEY CUSTOM must be always removed when using code that bypasses itI pulled the KEYCUS and it boots without restarting! I'm able to coin up and play.
This is probably an issue with board, check the SMD filters near the JAMMA connector (they lose contact very easily) as well as the multiplexers.for some reason though the right direction on both joysticks does not register. Also settings in test mode are not saved (for instance I enabled screen flip and as soon as I exit test it is flipped back).
So you mean it actually works better with no KeyCus installed?I pulled the KEYCUS and it boots without restarting! I'm able to coin up and play.@twistedsymphony can you take a video with the KeyCus installed and then with no KeyCus?
for some reason though the right direction on both joysticks does not register. Also settings in test mode are not saved (for instance I enabled screen flip and as soon as I exit test it is flipped back).
Damn, this is useful information I wish you had posted earlier.The KEY CUSTOM must be always removed when using code that bypasses it
yes. with KEYCUS it reboots, without KEYCUS it worksSo you mean it actually works better with no KeyCus installed?
I think this is just my PCB... I swapped back to original ROMs and right direction still doesn't work. I'm thinking cold joint on filter SMD as caius suggested. probably developed from handling the PCB so much as it definitely worked before.what's the link between right directions and the KeyCus?
swapping back to original ROMs settings work. so maybe EEPROM is initializing even if it doesn't need it?And settings?
The SMD Murata filters are a common issue on these boards, they lose contact from pads simply handling/flexing the PCB.I think this is just my PCB... I swapped back to original ROMs and right direction still doesn't work. I'm thinking cold joint on filter SMD as caius suggested. probably developed from handling the PCB so much as it definitely worked before.