This relates to a chip I supplied to a customer in thread here: https://honda-tech.com/zerothread/1692801

anyways, i bought another batch of 10 SST 27sf512 chips from moates.net.

I have a standard process I follow for burning chips, so here's what I do for all burns. For the SST chips, I erase the chip, and set the start of device to 08000. (FYI, I'm using the Xtronic Pocket Programmer 2). Then I program the device. After that I move the device to buffer and save the buffer as a new file. Then depending on what application the chip is burned in (hondata/crome/etc) I attempt to open the file.

Well here's the strange part. I burn one of the new SST chips for the above person, burns just fine. I go to open the file I created to see if it works and boom, opens right up. So I say, thsi is a good chip and mail it out. He gets solid CEL, which alot of times I just attribute to crappy ecu socketing, etc, it doesn't happen often but **** happens. Anyways, fast forward to last night, I'm feeling bad for him, so I go to burn a new chip and send it out. Chip burns, just fine, the created file i made, opens up perfectly. So i decide to go one step further and tose the chip into my car to ensure the CEL goes out...low and behold it does not.

I go back and retransfer the file off the chip and it opens up in Crome...so....WTF is going on? I put a riser on the chip, just thinking maybe it wasn't making a good contact with the ZIF socket and no change.

Now, i'm reburning all the chips I have, and testing and none seem to really work. I think, maybe i'm burning it wrong, so I swap between 'start of buffer' and 'start of device' setting them to 08000 back and forth to see if anything works..nothing. then i notice when i erase the chip, sometimes its fully erasing and other times its leaving some left over code. Do the SST chips have a limit on how often they can be erased? or is my Programmer just taking a **** on me?

Between the romulator issues i'm having and now programmer issues, this is becomign a bit expensive if ever 2 years I'm going to have to rebuy all this ****.

 

sounds like the burner is corrupting the BIN files- even tho they sometimes open doesnt mean all is ok. It is possible to open a corrupt file.

 

any reason it will work 100% fine on atmel 29c256 chips?

 

actually, I wonder about since the burn is only burning part of the chip, does what's left on the chip matter? kind of like if its not 00s, or FFs would it matter.

I've burned alot of SST chips before without any problems, its just this latest batch.

 

did you try starting the buffer at 8000. Also is the chip furthest away from the lever with notch facing arm

 

yea, chip is in the bottom 28 pins, i atfirst though maybe i had it 1 tooth out of line, but it was the correct are and yep, the indention is pointing towards the lever.

I feel stupid, as I've probably burned a few hundred chips over the past 3 years and now all of a sudden i feel like a retard with these SST chips.

 

Yeah, here's what I've figured out since I've had the exact same issues with Crome and the SST chips.

Do not use Crome to burn your .bin's!

I have a Moates.net Burn1 and APU1. For everything to work flawlessly I have to...

1. Create a new .bin in Crome (your old .bin with the solid CEL occuring is fucked, do not copy and paste the old values into the new .bin either).
2. Save file.
3. Use another program (such as TunerPro RT) to erase the chip, upload the file to buffer, load buffer to chip, verify.
4. Do step 3 every time you need to burn a .bin. Do not use Crome.

Those steps have worked flawlessly for me with pretty much the same issues, just different burner.

 

hrmmm.. think maybe i just forgot to remove checksome or something stupid like that?

i use the Xtronic PP2 software to burn all chips, I never use anything else. that could be why I can verify the burn and the map opens via laptop but then car says F-you.

but I will say, last night after all the issues, I even stopped messing with crome files and start to just reburn my current hondata rom to a SST chip to get it to work and it didn't work either. it was around midnight by the time i started that, so i stopped and decided to start over today when i get home to see what's up.

regardless i managed to get an extra amtel chip to burn for the guy, but that was my last atmel chip and since they are pretty much gone forever, i need to learn and adapt.

 

i've seen weird stuff with sst's too. I wish atmels were still being made

 

i know

 

is this your first time using sst's.i been using them awhile. heres my settings for pp2

buffer start 08000
device start 08000
device end 0ffff

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by seen4ever &raquo;</TD></TR><TR><TD CLASS="quote">actually, I wonder about since the burn is only burning part of the chip, does what's left on the chip matter? kind of like if its not 00s, or FFs would it matter.</TD></TR></TABLE>i dont believe so. the 512 chips have 2 "pages" not necessarily just more space on the chip. you have to either add or remove a ground to the chip to access the second page. if you are burning it like you would a 256 chip, thats basically what you are going to end up with, since you are not using the second page.

thats what the Moates 2timer does, just adds/removes a ground. hence the one wire in this pic (at least thats the info ive read on this topic )

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by IMPORTJEDI &raquo;</TD></TR><TR><TD CLASS="quote">is this your first time using sst's.i been using them awhile. heres my settings for pp2

buffer start 08000
device start 08000
device end 0ffff
</TD></TR></TABLE>

that's the thing, its not my first time, i've burned probably 10-50 chips of them, all of a sudden its a problem.

i think i tend to use buffer start 00000
device start 08000
and device end 0ffff
with the checksum =00000

either way, i'll go out and screw with it again tonight to see if i can figure out what the hell i was doing last night.

 

kind of silly but are you selecting the right chip?

 

only one option for 27SF512 which is a 12.5v chip

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by backpurge &raquo;</TD></TR><TR><TD CLASS="quote">Do not use Crome to burn your .bin's!
</TD></TR></TABLE>

That funny...EVERY chip I burn for OBD1 ECUs comes straight out of Crome and into my BURN1 PERRRRRRFECTLY.

You must be doing something wrong or using a version with issues...

To the original poster, when I use SST512 chips and my Pocket Programmer, here is what the screen looks like...




<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by seen4ever &raquo;</TD></TR><TR><TD CLASS="quote">regardless i managed to get an extra amtel chip to burn for the guy, but that was my last atmel chip and since they are pretty much gone forever, i need to learn and adapt.</TD></TR></TABLE>

They arent gone completely...maybe getting pretty hard to find and more expensive but I just found a few hundred more for a good price

Keeping them in stock for as long as I can

http://www.xenocron.com

 

^^ Same, I use Crome to burn all my SST chips, after the burn I verify and then upload the .bin from the chip to make sure all is ok. I have yet to have a issue, and I lost count to the number of chips I have burned like this. in the high 100's

BTW im using the Burn1 as well.

one more thing. I have had a few issues with bad burners, they work great for the longest time and then wham!! errors or problems arise.. dont blame it on yourself just yet brother G/L

 

yep, my settings were that exactly, as I said, i've done this before and had no issues, I did notice my damn checksum number was changing yesterday, maybe that was it. hell maybe i just need to uninstall and re-install the PP software. could just be my laptop hating me.

eitehr way, thanks for the help, i didn't attempt any tonight, as for some reason my garage is hotter than outside and its 95 degrees outside.

 

I have not had any problems thus far. They are actually great chips and very afforadable. I use a ALL-11 burner

Works fine all the time.

 

Whats REALLY weird is that at one point in the past...I had the same situation. I had been burning SST chips for the longest and then my PP starting shitting the bed on me. I thought the burner went bad and put it away.

I got it out at a later date and tried it again and it worked flawlessly...not sure quite why to this day.

install any new software lately?

If you burn that many chips...it might be a good idea to look at the BURN1...such a simple and effective little bugger. You will question why you carried around that parrell port thingy with the long and bulky power supply for all these years

I just keep it around to burn the wacky variety of chips that EVERY once in a while I still have to entertain

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by seen4ever &raquo;</TD></TR><TR><TD CLASS="quote">yep, my settings were that exactly, as I said, i've done this before and had no issues, I did notice my damn checksum number was changing yesterday, maybe that was it. hell maybe i just need to uninstall and re-install the PP software. could just be my laptop hating me.

eitehr way, thanks for the help, i didn't attempt any tonight, as for some reason my garage is hotter than outside and its 95 degrees outside.</TD></TR></TABLE>

 

I had a lot of problems with my PP2. Only with 12v program chips tho (27SF, 27C, etc.) not 5v program (29C, etc.)

You also might wanna try "doubling" the program in a hex editor (i.e. 0000-7FFF and 8000-15FFF same program) or writing to the 512 chips twice, once at 0000 offset and once at 8000 offset.

 

I remember i had a problem with burning sst512 chips but I use a batronix burner
I was having the exact same problem with solid cels

It turned out it was the updated software I downloaded from batronix. Every time i would set the offset to 8000h it would never do it.

I found the software that orginally came with the burner loaded it back up and it worked.

 

Just to add my 2 cents, that pocket programmer is a piece of ****. I've probably burned 10,000 eproms in my time, and the few times I used that programmer, I had nothing but problems.. I own 4 different programmers, and my favorite by far is the Batronix, and although its not the cheapest one out there, it is far from the most expensive in my collection..

On the other hand, my Xtronics Emulator served me well for many, many years, and now it sits around as a backup to my 3 Ostrich units..

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by xenocron &raquo;</TD></TR><TR><TD CLASS="quote">Whats REALLY weird is that at one point in the past...I had the same situation. I had been burning SST chips for the longest and then my PP starting shitting the bed on me. I thought the burner went bad and put it away.

I got it out at a later date and tried it again and it worked flawlessly...not sure quite why to this day.

install any new software lately?

If you burn that many chips...it might be a good idea to look at the BURN1...such a simple and effective little bugger. You will question why you carried around that parrell port thingy with the long and bulky power supply for all these years

I just keep it around to burn the wacky variety of chips that EVERY once in a while I still have to entertain </TD></TR></TABLE>
Burn1 has most always done the job for me

 

i also have had an issue with the SSR chips in the 27 series.

i just said screw fingding the reason and ordered some more atmels from xenocron, i dont care how much it costs, im just stickin to the atmels