4827(128G) EPROM Substitute? Can't seem to program them with the GQ-4X Burner

TSB

Well-known member
Joined
Jan 14, 2016
Messages
2,541
Reaction score
916
Location
Alaska
4827(128G) EPROM Substitute? Can't seem to program them with the GQ-4X Burner

I've tried using the 482764 chip setting (both have the same specs), writing at the slowest speed, with the supplemental power supply attached.

Maybe it's just not possible. Is there an acceptable substitute for this EPROM?
 
Last edited:
Can you clarify what you have and what you're doing?

Are you saying you have a HN4827128G chip, and you're trying to burn it with the HN482764 device setting? If so, that won't work... the HN482764 is a 64kbit chip... the HN4827128G is a 128kbit chip.

I'd try using the "27128(21V VPP)" device.

DogP
 
Thanks! I'll give that a try.

Can you clarify what you have and what you're doing?

Are you saying you have a HN4827128G chip, and you're trying to burn it with the HN482764 device setting? If so, that won't work... the HN482764 is a 64kbit chip... the HN4827128G is a 128kbit chip.

I'd try using the "27128(21V VPP)" device.

DogP
 
I'm beginning to think that it's not the programmer OR the eprom.

I programmed it using the "27128(21V VPP)" setting, but it still gives me garbage(different garbage, but garbage nonetheless).
I read back the file, though, and it saved as a 16Kb filesize.

The weird thing, is that the eprom has Verified every time.

Have I got the wrong file?


EDIT: It read back as a 16KB file...
 

Attachments

  • IMG_8545.JPG
    IMG_8545.JPG
    129.5 KB · Views: 9
Last edited:
If the EPROM verified, then it probably worked... 16K Bytes (128K bits) is correct for a 27128 EPROM.

Why do you think the problem is the EPROM? There are quite a few other reasons for a board to show garbage than a bad EPROM.

DogP
 
I put these eproms on a working boardset. This was the only one that kept it from booting.

If the EPROM verified, then it probably worked... 16K Bytes (128K bits) is correct for a 27128 EPROM.

Why do you think the problem is the EPROM? There are quite a few other reasons for a board to show garbage than a bad EPROM.

DogP
 
It really is weird. It "blank-checks" fine, and verifies afterwards. I can only guess that I've got the wrong/corrupted cpu_pg5.11d file.
 
Last edited:
On some games there can be different rom sets. You can burn the whole set or try to find the one you need.
On the other hand, Ive had one of my files get corrupted. It programmed and verified but was spitting out the wrong checksum. I think it happened when I moved my rom files to my external drive.
 
It really is weird. It "blank-checks" fine, and verifies afterwards. I can only guess that I've got the wrong/corrupted cpu_pg5.11d file.

You are correct. Spy Hunter cpu_pg5.11d in mame is bad.
I started to attach the correct version here, but not sure if that'd be ok or not.
If you'll send me a pm with your email address, i'll email you the correct cpu_pg5.11d.

I wouldn't mind attaching a zip of the file here, if its ok with the powers that be.
 
PM inbound! I'm glad to find out that I'm not crazy... 😜


You are correct. Spy Hunter cpu_pg5.11d in mame is bad.
I started to attach the correct version here, but not sure if that'd be ok or not.
If you'll send me a pm with your email address, i'll email you the correct cpu_pg5.11d.

I wouldn't mind attaching a zip of the file here, if its ok with the powers that be.
 
Back
Top Bottom