Help burning a rom please?

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
I need to burn a rom, the rom I wish to replace on a faulty board is a:- B8706 NMC27C256Q 250

I found what I thought was a replacement and erased it all ok (checked with Galep32)

I went onto maws and compared the CRC until I found the exact rom I need.

Downloaded the mame rom and extracted the piece I need,

I can load it into Galep32 so I can see the data, (chose a NMC27C256 as no Q on the end in the Galep National eprom model section)

I then click prog and it says error program failed??

Looking at the chip I'm trying to program it says:-

B8724 (and then the rest is the same) NMC27C256Q 250

What does the "B" number refer to? Am I trying to burn to the wrong type of eprom?

Sorry never programmed a rom before (Eprom eraser only arrived today)

My Galep4 reads fine, verifys fine, even checks blanks ok, just not able to write to it.

I can tell you all the details of the rom I'm trying to burn, or can anyone send me a rom to try (which you know will be ok on that chip) and tell me the settings just so I can make sure my Galep is ok?

I'm sure it is...as it passes all tests, both when it loads up and in the test menu part.

I need to understand how to prog roms to get any further, I'm happy once I've done one that i'll be ok in the future just wanna get the first one under my belt.

Ta

Paul.
 
G

Guests

Guest
its prolly the batch run of the chip, pay it no attention.

does it say anything in teh galep log when it gets the error?
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
As AnDyC says, that bit is most likely irrelevant. The key part is the manufacturer code "NM" in this case and the IC ID "27c256Q". The Q is used to indicate a variant, and I'm sure if you googled NM27c256 you'd get the datasheet which explains what the Q variant was.
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
AnDyC said:
its prolly the batch run of the chip, pay it no attention.

does it say anything in teh galep log when it gets the error?

smiley9.gif
Where's the log?
smiley36.gif


Does it create a notepad text file in the folder, or is there a part of the program with it in?

Ta

It's probably something really simple, just a box to tick as I'm such a rom burning noob, all you guys know you have to pick 8 bit for example and then prog it!

smiley9.gif
Don't miss out the obvious!
smiley36.gif

paulcan692010-08-12 21:00:06
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Well ok, seems I was doing it right, I got a MSL2732 from my zig zag (galaxian hardware) (LAX)

then downloaded the correct rom from looking at MAWS and that programmed ok, so I'm guessing the NMC***** chip was bad??

Weird!
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
How long was it between clicking the Go button on programming the 256 and getting the error? Did it give any indication how much of the buffer it had written out to the chip or did it fail immediately? I assume from your first post that you initially did a blank check?

I've not used a Galep but do you know if it's got the ability to check that each pin has good contact? Probably the most common fault I have when blowing EPROMs is a bad pin connection error which is reported by my progger. Normally fixable by rubbing the leg with a fibre glass pencil, but other times it's irretrievable and I guess some internal wiring has melted or some other fault.
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Yes did a blank check before all OK, because I'd never seen one burn I didn't know what to expect but looking back I understand now.

The second I hit the go button it was stopping and saying error, but after seeing a blank and a good ROM programme I can tell that it failed three quarters of the way though the first line of data.

i.e everything was all FF's apart from the first line if that makes sense.

Sorry
smiley9.gif
this is so new to me.

I'm a hands on person I have to do things first to learn, then I read and don't get bored.

I can't read 300 pages then have a go, I'm the back wards man the back wards man!

(Freddy got fingered quote, we watched it today at lunch at work)

Do first then read otherwise I switch off.

Thanks y'all my confidence has stepped up a notch.

Lesson to self, don't use hot air gun on scrap boards again, although quick I'm gonna buy a desolder gun.

Aoyue 474 anyone?? (see wanted section)

smiley17.gif
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
Hi dude,

How can you tell it failed 3/4 of the way through the first line of data? Any chance of taking a screen shot of the failure and posting it up? If you click the programming tool window, then hold Alt and press the PrtScr button this will paste a copy of the window onto the clipboard. Then just start mspaint.exe and Edit -> Paste to save the image. Sorry if that's teaching you to suck eggs ;)

Based on what it shows (I don't know the Galep software) it should be possible to ID whether it's a faulty EPROM or a wider issue.

And the hot air gun on scrap boards - what happened? As long as you don't try to remove everything in one go it's normally a pretty good method of bulk extraction. Some PCB substrates don't like it - often bootlegs as they have really cheapo laminates. And some early Atari stuff - the grey boards can bubble up too but I can't think of many Atari games that you'd resort to heat gunning
smiley36.gif


cheers
tim
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
blank18.08.10.JPG
Well

Don't know what I was doing but somehow this is how it looked before (blank)

Then this is what I was trying to burn....

burn18.08.10.JPG


However don't know what I did before but somehow I had a screen as the top pic with a load of FFF's (blank) apart from the very top line which was half filled with data like the lower pic, but now I can't seem to re-emulate that???

smiley9.gif


Anyhoo please see this pic below, sorry this is all so new to me...

Do I need an adapter to prog this kind of chip, the part circled in red now makes me think that this is my problem? Any ideas???

Thanks,

adapter18.08.10.JPG

paulcan692010-08-18 20:37:24
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
Heh. Well that certainly is blank, but not the kind of blank I think you were expecting. It looks like you didn't insert the image correctly.

cheers
tim

ps Don't worry about anybody thinking you're not up for learning or don't appreciate the help given. Work always has to come before hobbies, otherwise there'd be no $$$ for the hobby :)
 

paulcan69

Can reburn OTP EPROMs! Fear my power!
Feedback
11 (100%)
Credits
943CR
Do you think this needs an adapter Tim?

I did exactly the above with another chip which was a MSL2732K (and a different rom image) and that worked perfectly, I now think that I can't program this without an adapter.

What's a DIL?
smiley9.gif


And what's a PLCC32?
smiley9.gif


I'm guessing I want the second one
smiley36.gif


P.S Black Tiger is next to me, just having a look now!
 

tb2000

Active member
Feedback
4 (100%)
Credits
3,575CR
DIL is "Dual In-Line" or "Dual In-Line package", it refers to the two parallel rows of legs/pins on a standard eprom or whatever.
PLCC32 is a "Plastic Leaded Chip Carrier", and either goes into a socket or is surface mounted - and yes, you'll need an adapter to program one.
smiley1.gif


Edit: This might do the trick, although i'm not sure if the adapter has to be programmer-specific.
tb20002010-08-18 21:08:22
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
Hi dude,

It doesn't need an adaptor. What the software is showing in that window is that the EPROM comes in a variety of form factors:

DIL - Dual in-line. These are all of the chips you see; dual rows of pins in-line.

PLCC32 - Plastic Leaded Chip Carrier 32 pins - Wiki link

You definitely want DIL but it shouldn't make any difference. The software is just telling you that you can use an adaptor to program the PLCC version - perhaps some pins are swapped on the adaptor so it uses whether you select DIL or PLCC to route data to specific pins on the progger. Don't worry about any of this stuff - just select DIL.

When an EPROM is wiped by exposure to UV light it actually works by using the energy in the UV photons of light (UV light is high energy, which is why it's used) to excite electrons causing them to fill holes in the chip substrate.

Each single bit (bit as in 8 bits make a byte) of storage in the EPROM is made up from a number of holes. When the holes for a cell are full, that cell reads out as a binary 1. Given that each storage unit of the EPROM is an 8-bit byte, and all the bits are set to 1, this will read out as 0xFF in hex or 1111 1111 in binary (The 0x notation indicates the following value is in hex. I leave a space between each 4 bits when writing binary representation as it's easier to count that way if you have a long string of bits).

So when you read the blank EPROM, or conduct a blank check the progger reads the chip and expects to find 0xFF in every cell. If it doesn't find this then the check fails.

The reason it needs to have every cell set to 0xFF is because the progger can't push electrons into the holes, it can only drain them away. So what the progger is doing on an electron level as it burns the EPROM is looking in its buffer to see what value you want to write, figuring how this differs from 0xFF (or 1111 1111 in binary) and then deciding which cells it needs to drain so that they read as a binary 0.

So if you're writing 0xAA to a cell, the progger basically sees that you want to write 1010 1010 in binary to a cell which currently has 1111 1111. So it knows to drain the first, third, fifth & seventh holes - in this instance we start reading the binary from right to left, where the right-most bit is known as the Least Significant Bit (LSB) as it represents the value of 1, whereas the 8th bit - Most Significant Bit or MSB - represents the value 128.

Anyway, this is diverging slightly but I figured it might help you to understand what is going on.

Back to the problem - the IC has passed a blank check, so you know that all the cells have been bumped up to 0xFF so it's ready for programming. What I would do now is to read in the chip and then look at the buffer to see how much data has been changed. I suspect this is what you did before when you said you saw the data displayed.

Report back on the buffer contents and we can figure out what's going on. I suspect you just have a duff EPROM (maybe an internal short or broken column/row decoder) but this is a useful exercise to learn how this stuff works and also pickup some other useful titbits. Depending on what data you get back from the read attempt we may be able to determine the actual fault (as a clue, think what would happen if one of the data or address pins wasn't connected internally - we'll see patterns which I'll explain when you post back with a shot of the buffer after reading the dodgy EPROM).

cheers
tim

ps Any pedantic types who want to challenge my explanation of how an EPROM works - go ahead, but bear in mind I'm aiming for a useful explanation, not a quantum mechanics level of accuracy ;)

EDIT: Had left a line of random text at the bottom.trmatthe2010-08-18 21:23:30
 

trm

Who loves you, and who do you love?
Feedback
2 (100%)
Credits
2,877CR
tb2000 said:
Edit: This might do the trick, although i'm not sure if the adapter has to be programmer-specific.

Paul is trying to program a normal DIP-28 27256 so no adaptor is needed. The PLCC is just the Galep software throwing in another variable to add to the confusion :)
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Nice link though - ta.

There's multiples listed so no need to bid against me if anyone does want it
smiley1.gif


Quite why there's not BIN I don't know!
 
Top