EEPROM error on Dragon Blaze

[jessiewonka]

I bought a Dragon Blaze that played fine other than giving an eeprom error on startup. Then it started resetting. After seeing a thread with a similar issue (http://shmups.system11.org/viewtopic.ph ... =45866&sid), I replaced the eeprom chip. But now it boots with a "security ng!" error and won't boot further.



I can't seem to find this error online anywhere.

[system11]

There are a couple of little used inputs defined in JAMMA:

Service
Tilt
Test (well, fairly common)

Try turning it on with each of those held down in turn, I asked Haze and there's something to do with security and an input port.

[jessiewonka]

There are a couple of little used inputs defined in JAMMA:

Service
Tilt
Test (well, fairly common)

Try turning it on with each of those held down in turn, I asked Haze and there's something to do with security and an input port.

I'd tried turning it on with a variety of player buttons, test and service with no success. Tilt though, how would I activate that? It does coin up fine!

It does seem like it just needs reset in some way.

[jessiewonka]

Interestingly you can get it into this endless "security ng!" loop in mame as well if you flip the "debug" dip switch. Turning it on seems to reset it. But the board has no dips. There is an area marked reset with four pads.

[dingsbums]

You can reset (erase) all data saved on a Dragon Blaze - I think it's worth a try - use the "erase all data code".
Edit: Since you replaced the EEPROM I think it's best to try it with the original one (if you still have it).

http://www.world-of-arcades.net/1945/Dr ... ecrets.htm

[jessiewonka]

You can reset (erase) all data saved on a Dragon Blaze - I think it's worth a try - use the "erase all data code".

http://www.world-of-arcades.net/1945/Dr ... ecrets.htm

I can't get in far enough to enter any codes.

[dingsbums]

With the original EEPROM also ?

[jessiewonka]

With the original EEPROM also ?

The original eeprom isn't going back on, it was hard enough to get the replacement situated.

[dingsbums]

Since you stated in your first post that your PCB is resetting with the original EEPROM I would try to:

1. Insert the original EEPROM
2. Fire up the PCB
3. Enter the Test Mode
4. Enter the Erase Code
5. Hope that it clears the EEPROM and starts the game correctly .

And since I don't know how long it takes before your PCB resets - do it all quickly .
But seriously - Since it's not working at the moment I think it's worth a try.

[jessiewonka]

Since you stated in your first post that your PCB is resetting with the original EEPROM I would try to:

1. Insert the original EEPROM
2. Fire up the PCB
3. Enter the Test Mode
4. Enter the Erase Code
5. Hope that it clears the EEPROM and starts the game correctly .

And since I don't know how long it takes before your PCB resets - do it all quickly .
But seriously - Since it's not working at the moment I think it's worth a try.

Already did this before replacing the eeprom.

[dingsbums]

Then it's going to be a tough one
What's happening when you have the "Security NG" message on the screen and you hit the test button ? Can you enter the test mode ?

[jessiewonka]

Then it's going to be a tough one
What's happening when you have the "Security NG" message on the screen and you hit the test button ? Can you enter the test mode ?

It boots to that message and stays put. It can be coined up, the counter increases and a sound triggers. I've tried several variations of test and service buttons. Read above.

[system11]

Well tilt is on another JAMMA pin near service and test. The reason I suggest it is Haze pointed out that debug input port and it's close to the service input, which means there's a chance it's coming through the same chips and potentially one of those edge inputs. Could just as easily go to a jumper though. In fact you could try working it out by tracing the logic from the service button.

Of course you could also remove the eeprom and program it with the stub default data stored in the MAME ROM set, then refit it. You'll probably have to find someone who already has a relevant adapter though.

[jessiewonka]

It looks like tilt (pin 15 on solder side) goes nowhere.

In fact you could try working it out by tracing the logic from the service button.

Do you mean trace the logic from the service pin?

Of course you could also remove the eeprom and program it with the stub default data stored in the MAME ROM set, then refit it. You'll probably have to find someone who already has a relevant adapter though.

Yeah I'd need someone. : )

[Dave_K.]

Following on system11's suggestions, you could check the PCB pins with a multimeter continuity test to ensure the test, service and tilt pins are not being held to ground. You could also do the same with your cabinet's jamma connector (without the game plugged in).

I don't know enough about these psikyo eeproms to know if putting in a blank is causing the freeze at boot, or if your random freezing simply got worse and is re-corrupting the eeprom data every time. But I like the suggestion to try and put the old eeprom back or reprogramming the new one with default/mame data.

On a side note, I had recently put Dragon Blaze in one of my cabs, and happened to notice the same eeprom ng! red error msg at boot, but it ran fine. I recall then making a change in the settings to freeplay, and checked again just now and see the eeprom is saying ok!

[jessiewonka]

Update on this one: Fox1 was able to repair the board for me. I'd scratched a trace under the EEPROM, and as suggested here the chip was missing the data.