94zcar

I am burning my first chip. I am using a willem eprom burner to burn AT29C256 flash chips. I need to offset? The chip to put all the info at the end of the chip is this correct? I can not figure out how to get it to do that. It always puts the info at the start of the chip. My bin file is 4K in size. Any help would be appreciated. -Rod-

Gladstoneiroc

iTrader: (1)

Hello, me last week (hopefully you don't fry the old ecm like I did). I found the easiest way to do it is to stack the bins in your tuning program then burn as a 64k bin. That would be 4k bin 4k block and 64k chip. Thanks Duronclocker.

jeepguy553

Start your burn at $7000 and end at $7FFF.

94zcar

Ok I am not sure how to stack the bins, how do I do this?
-
And I also do not know how to start the burn at the $7000 address. I was trying to figure that out but had no luck. The burning software has a move "A" to "B" function It has 3 area's to type in info.... "A" address Hex.... "B" Address hex... and size Hex.
Is this for moving your bin to the end? I tried typing in a different address but the bin did not move. I really don't know what to type in any of those boxes. I will try the addresses you suggest but don't know what size hex is for. -Rod-

94zcar

Ok I did a search in the achives for info on bin stacking. I just tried it out with tunerpro. I was able to stack my bin and output it as a new 32k bin. Thanks for the suggestion.
-
Now I'll just see if it'll run. I have a adapter and a ZIF socket on my ECM That I got installed by Craig Moates. What would happen if I put the chip in backwards? The notch goes toward the ZIF handle right? -Rod-
-

Mangus

http://www.moates.net/documentation....entation_id=20

94zcar

I tried typing that info into the swap A for B address But it did not work. I have a Willem Burner. I just can't figure it out. That is the only place to type in somthing. Thanks for the info though -Rod-

Siggy

To 94zcar

Have you solved this problem....?
I'm have the same results using the 29C256 and a Willem programer. The problem may be confined to the Willem, most info I've found relates to using other programers and software. The 29C256 appears to require 64 block or sector writing I'm just not sure how to setup the Willem to get a valid burn.
I've tried both the 27SF512 and the 29C256, the Atmel chip = no luck, the SST chip sometimes? But when using the old 27C256 eprom it works every time, I made a UV eraser using a tooth brush bacteria cleaner gadget...cheap. Whatever the solution I'm sure it's related to using the Willem correctly.
Also have you seen this Grumpy thread;
https://www.thirdgen.org/techbb2/sho...t=eprom+29c256

Gladstoneiroc

iTrader: (1)

With the Willem programmer and a 29c256 just stack your bin to fill 32k and then burn it onto a chip. Sometimes when I use willem i have to read, reset the buffer to 0X00, burn that then burn my bin.

Siggy

Thanks for the reply...I'm trying everything and will beat this thing.
I suspect that it may be a XP/CPU/Bios thing...I'm going to try using Win98 as I have heard that some users have had luck while others can use XP...could be a certain XP/CPU/Bios combination that is the problem.
My setup is..Willem 4 Enhanced, Asus P4PE MB, Intel P4 2.4G, XP SP2.
I'll post my results in any case.

Siggy

I have had some success using my Willem programmer (Honkong copy) to burn the 29C256 using the Willem mode and not the PC3 mode. You must put a jumper between pins 3-31 on the zif socket (Willem mode).
My 88 IROC is not available right now so I have no way to test the chip in my 7165 ecm until it is back home, but in Willem mode I can erase, burn, read and verify the chip no problem. Using the PC3 mode I can only burn a 27C128 eprom (UV eraseable) with good results. The PC3 mode will not correctly read the chip done in the Willem mode, so far. The PC3 mode refers to the A/B setting at startup...but as far as I can see this is only for stacking bin data?
I operate the Eprom3 program with my PC (XP) in diagnostic mode using msconfig and I also installed the Willem XP LPT polling fix found here.
http://www.willem.org/ZIP/xp_stop_polling.reg

I do not wish to offend about support for this Honkong burnner, I failed to realize the nature of the design...unfortunitly so have many others. On the other hand it would be a shame not to enjoy the 29C256 chip.

Siggy

I have been frustrated by a lack of info on this commercial copy of the Willem programer...warning cheap is not always best.
Be that as it may I did find a web link which may offer relief to those of us who have bitten. This link at least showed a photo of the item I have and much needed product manual support.

http://www.mcumall.com/comersus/stor...namicIndex.asp

I have modified my programer with a dip jumper to short pins 3 - 31 to enable the easy use of AT29Cxxx flash chip (Willem mode). The jumper is also needed to read the chip, I have tested in car...no problem. I also stack my bin file using TunerPro 4 rather then mess with the AB offset.
Now I will try to solve the SST 27SFxxx EEprom problems using this programer.
I wonder just how many out there are just as frustrated??

Siggy

I appoligize if it seems that I'm stealing this thread...I just felt that anyone doing a search would find related info quicker this way.
I have had problems using both the AT29C256 and SST27SF512 chips with the Willem Enhansed programer. There exists two models of the Willem Enhansed on Ebay, the Universal and the Dual powered. My info refers to the Universal model without the JP2 and JP3 jumpers. I found a form link which has solved the problem I was having burning and erasing the 27SF512 chip. I tested using a Pent 233 laptop running Me with ECP port & USB power. I did a single erase and then burned a TP stacked 64k bin....winner. Here is the form link for those who need it....I sure did!

http://www.mcumall.com/forum/topic.asp?TOPIC_ID=111

Gladstoneiroc

iTrader: (1)

It appears that the dual power ones are actually better though the design is older. They can do 2732's even though I don't use them, that's why I bought mine. I do have to change the buffer to 0x00 write and then write my data every time, but that's not a big deal.