I'm stuck at burning my first chip. I've got the Autoprom with TunerProRT, and a 27sf512 chip. I found the AKWA bin and 4F.xdf mask for a '8747. Improper chip placement seems to be a common problem, but I have the notch facing the lever and moved so the extra pinholes are between the lever and the chip. I erased the chip, blank checked the chip, and loaded the file to buffer, so far so good. I then programmed the chip, but when I verify the chip, it fails. BMmonteSS wrote in the Come in for a FREE tune!!!! thread, that the 4K file should start at F000 on the 27sf512 chip. I tried that with no success. TunerProRT by default wants to start it at 00F000. I tried that with no success. I'm not sure how to clear the buffer between burn attempts, so I've been closing the burn window and reopening it, in case I have more than one bin in there. Well, do you think the chip addressing might be my problem? Or is there something else i need to look at closer? Thanks for the help guys Bob

Hi Bob -

Indeed, if you're burning a 4KB bin to a 27SF512 chip (which is 64KB), you need to start at 0xF000 (which is the same as 0x00F000). In the burn utility, set the chip start to 0xF000, chip end to 0xFFFF, buffer start to 0, and buffer end to 0x0FFF. Erase the chip first, load your bin to the buffer, then burn the buffer to the chip. Verify. If the verification fails, it could be a bad chip, among other things.

Note that you MUST erase the 27SF512 before every burn.

Give it another go and let us know how you fare.

Thanks Mangus
The burn utility actually states that the file size in bytes
[interger/hex]: 4096/0x1000

I put the new addresses in, including the x
I erased the chip again
then I blank checked the chip, chip is blank message rec.
loaded file to buffer
programed chip
PROM I/O suceeded
verifying device against buffer....and...................................................................
FAILURE: Verification Failed [not matched]

So did I do it correctly. 4096 is 4KB, right?

Can tunerpro detect a bad chip, or verify that the chip is good in any way?

I'll see if I can find another chip tomorrow.
Any place besides frys electronics that might carry them?
If I cant find any locally, I'm sure I can get them online, but I hate to wait.

What are the other things you mention it could be?

Thanks for your help
Bob

The "0x" or "$" before the values indicate it is a Hex value.
Do not enter the "x" in the box.
0xFFFF should just be FFFF

The 0x shouldn't make a difference.

I'm not sure where locally you could buy them. Moates can get some out to you pretty quickly.

From what you describe, you're doing everything correctly. I'm going to go with a bad chip. How old is the chip and how much has it been used?

There are several mail-order outlets that can get you new chips.

You might try Digikey, Arrow Electronics, and Mouser Electronics.
Also, Jameco and JDR Microelectronics also carry them.....

I am with Mangus here, it sounds like a bad IC.
If you REALLY want to find out, try this test.
With a programming ASCII editor (UltraEdit, Vedit, VE, etc) make a two 4K files, one with with all locations filled with $55s, and another with $AAs. (Inverted bit patterns of 01010101 and 10101010)

Burn these to the chip and then read back and do a binary file compare.
This should tell you which bit(s) of which byte(s) are corrupt.

Thanks Mangus

The chip came new with the autoprom, but since a new chip is cheap, it's worth a try in case this one's a fluke. Or in case I did something wrong, and damaged it some how.

And since Moates is a Thirdgen member, I want to send him more of my business. The only problem is, I can't log on to his website. I've sent emails to his website, and to his email on here, and i know he logged on today, but I haven't got a reply. Can anyone else get a hold of him?

Thanks s24a

But I'm just a geekwannabe, and dont have a clue on how to due what you suggested. Hell, I tried looking for a chip at those places you suggested, but got lost and confused looking around on their website for it.

Thanks for help
Bob

www.moates.net seems to be up and running for me.

craig at moates dot net should also work. If he gets the mail, he'll respond. It might take him a day or two, though (seems he's beginning to get in over his head with regard to his inbox).

-M

Hi Bob,

Sorry for any trouble you might be having. I've sent you my personal number via IM. If you'd like to call me anytime, I can step you through all of the specifics. If it's a bad chip, we can send you some new ones. If there's something wrong with the programming device, we can get to the bottom of that as well and get you a new one if needed.

Either way, I'd be glad to walk you through everything to make sure nothing is being missed. Don't be shy, I don't mind answering.

Hope this helps,
-Craig
----------
Also, sorry about the emails. We've been having trouble with both incoming and outgoing mailings.

We're due for an email server migration next weekend, and hopefully we will appear more responsive thereafter.