Bad eproms that verify?

A place that you can discuss reproduction of classic titles or "licensed-for-reproduction" homebrew for personal use.

Moderators: B00daW, Moderators

Forum rules
1. NO BLATANT PIRACY. This includes reproducing homebrew less than 10 years old, with the exception of free software.
2. No advertising your reproductions, with the exception of free software.
3. Be nice. See RFC 1855 if you aren't sure what this means.
icemanxp300
Posts: 159
Joined: Thu May 14, 2015 6:17 pm

Re: Bad eproms that verify?

Post by icemanxp300 »

Ok what is going on here people. Look at the date I made this thread. It was exactly 1 year ago. I purchased a batch of chips in December and January they gave me problems.

Now the same exact thing happened. I purchased a batch of chips last month "December" and they program bad again just like the batch did a year ago.

However here is the kicker, Only on snes. I was trying to diagnose the problem and since I make genesis games as well now, I tried a genesis game and it worked. So Then I went back and tried snes again, multiple games and same thing, bad glitches on all.

So I grabbed the batch of chips I got over a year ago that would not program correctly and tried a genesis rom on them and it worked!!! Unreal. What is going on here. I'm glad I can use the chips now but what is going on here.

They are all 100F1
Ice Man
Posts: 547
Joined: Fri Jul 04, 2014 2:34 pm

Re: Bad eproms that verify?

Post by Ice Man »

Sounds like your SNES board is defective or your soldering is wrong. If ICs usually erase, blank check or verify they're 99% fine. I never had problems with EPROMs unless they didn't blank check or erase, those have been thrown in the trash.

How did you solder the 27c160 to a SNES board? Which SNES board did you use as a donor?
SHVC-1AXM
SHVC-1AXB
SHVC-1JXM
SHVC-1JXB
etc..


Genesis is simple so there's barely any error potential at all.
User avatar
thefox
Posts: 3134
Joined: Mon Jan 03, 2005 10:36 am
Location: 🇫🇮
Contact:

Re: Bad eproms that verify?

Post by thefox »

Maybe they are too slow for SNES. (Disclaimer: I have no idea how fast the Mega Drive ROMs have to be.)
Download STREEMERZ for NES from fauxgame.com! — Some other stuff I've done: fo.aspekt.fi
tepples
Posts: 22705
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Re: Bad eproms that verify?

Post by tepples »

The 65816 requires memory to return a value within a half cycle, which is 200 ns (slow ROM) or 120 ns (fast ROM). But the 68000 accesses memory only once every four CPU cycles. Because of this, a Genesis cartridge can use much slower memory if it isn't going to be DMAing from ROM.
icemanxp300
Posts: 159
Joined: Thu May 14, 2015 6:17 pm

Re: Bad eproms that verify?

Post by icemanxp300 »

Ok, what makes zero sense is I can order some m27c160 chips today and get them in and they can be identical and work fine.

Like I have programmed snes games all last year using these chips and the same adapter boards and same games. Here is a picture, the 2 chips on the left programmed fine, the two chips on the right will not.

If you look at the two chips in the middle they are 100% identical as far as the "I assume batch numbers" one programs fine, they other will not. It is only for snes though. All 4 of those chips will program perfectly genesis games but only the 2 on the left program correctly for snes.

So going over this speed thing, could it possible that some of these chips for some reason have some how "slowed down" and as such they are not fast enough to program snes properly now?

It is not a soldering problem or a wiring problem. I don't even solder until they go through my tester board which I have used to test 100's of snes games with. This problem is chip specific that is 100% guaranteed. As far as the boards I use, I use them all it doesn't matter as long as the donor has 36 holes instead of 32. so boards like 1aon-20 or 1a3m-11 anything if they are lo rom. Any hi rom works as well as long as they have 36 holes which I don't think I have come across a 32 dip hi rom donor yet.

So I am leaning to 1 of 3 problems.

1. The speed of the chips like thefox and tepples mentioned has slowed down.
2. The programmer/software is buggy
3. The adapter board is buggy

The only one that makes sense is 1. As I can and do program many of these chips perfectly fine.

Is there a way I can test the speed of these chips to see if some of them are not as fast as they should be?
100_8069.JPG
...
Post Reply