hex offsets for williem

[trevor425]

i have been searching and trying different things to burn a new eprom chip. i have all the hex in place. when i burn the chips however, i seam to be using incorrect offsets for the hex. i have tried both the 16k and 32k maps, and im using tuner pro to alter them.


also i have tried just making a stock map and i still cant get them to work. am i missing something in my programing process? how do i get the map to appear as an image on the eprom? how do i burn the image on the last half of the chip?

anyone who is familiar with the willem eprom programmer willing to lend a hand?

 

[donniekak]

If you have the correct bin size, and offset in your tuner pro .xdf, or whatever you use, you just need to have the right chip selected in the burner software.

 

[trevor425]

tuner pro only burns directly with the moates burn 2 i believe. im using tuner pro only to mod bins.
my problem isnt with tuner pro itself, but with the programmers software, or my inability to operate it properly.

i keep getting this "error at 0x00003E chip = 0xbd buffer 0xff" inside my willem program. i load the bin from my computer directly into the willem software. i have no idea how the offset needs to be set, in order for the ecu to recognize the code. im completely stumped, thanks for the help so far.

 

[donniekak]

What chip are you using, and what positions are the dip switches on the burner.

 

[trevor425]

sst27sf512's and i set the dip switches to what the program tells me for those switches so 1 2 4 6 10 11 12 down and 3 5 7 8 9 up.



i found this just now, and think i may have the info i was looking for.

http://tech.mirage-performance.com/ECU/EPROM-info.html -link

""Posted by: "Steve Piette" Fri Jun 27, 2008 on the Yahoo Group "DSM-ECU"

-----------------------------------------------------------------------

There is no difference between the 16k and 32k EPROM images when it comes to the actual software. The difference is that the 32k image has 16k of padding in front the code or two copies of the image depending on the size of the original EPROM and how the image was made.

The sooner we get people to start working in memory address mode rather than EPROM offset addresses the less confusing it will be. The real code lives in the address space starting at 0xc000 (c000h) to 0xffff.

The 16k images are 0x4000 (0x0000 to 0x3fff) long and need 0xc000 added to each location to get the memory address. The 32k images are 0x8000 (0x0000 to 0x7fff) long and need 0x8000 added to each location to get the memory address.

So for example the rev limiter parameter in the E931 code is at 0xf27a, which is 0x727a bytes from the beginning of a 32k image or 0x327a bytes from the beginning of a 16k image.

0xf27a - 0xc000 = 0x327a
0xf27a - 0x8000 = 0x727a

You'll also hear 0xc000 and 0x8000 referred to as the EPROM offset.""




i cant seam to get my willem software to load the code on the second half of the chip. this is whats bugging me. im about to just buy the ostrich and hopefully ill be able to operate that,

 

[trevor425]

If you have the correct bin size, and offset in your tuner pro .xdf, or whatever you use, you just need to have the right chip selected in the burner software.

what offset am i supposed to use for the tuner pro xdf?
shouldnt i be able to burn a stock image without using tuner pro at all?

 

[steve]

Your binary file doesn't go into the beginning of the flash chip. It needs to be offset so that the end of the binary file is at the end of the chip.

Since the Flash chip can hold 0x0000 to 0xffff and your images are either 0x0000 to 03fff (16k) or 0x0000 to 0x7fff (32k). So you need to have the burner start programming the beginning of the image at either 0xc000 for a 16k binary or 0x8000 for a 32k binary image. Those are the offsets we talk about.

What this should do is program the first byte (0x0000) of the image to byte 0x8000 in the chip, byte 0x0001 of the image to byte 0x8001 of the chip all the way until byte 0x7fff of the image is in byte 0xffff of the chip for a 32k image.

I don't have a willem pcb50 or it's manual so I can't tell you what you have to do to make it work correctly.

 

[donniekak]

The 512 chips are 4x larger than the image for a 1g. Burning it as a 32k image with the first 16k all f's puts the data in the 2nd 4th of the chip, It needs to be at the end. You need to buffer the image to get the data at the end of the chip.

 

[steve]

Padding the beginning of the image isn't elegant but it does work

 

[trevor425]

thanks steve and don, i understand what you are saying. ive been trying to set the image to 008000 to 00ffff chip start to end, but the willems software isnt the easiest to operate.

i found this write up yesterday, if you scroll down to the programing steps at post #9 on the last page, you can see his bins load to address 008000 automaticlly in the buffer. mine however load to 005000 and i cant seam to get it to the proper address.

How to Program the SST 27SF512 using an Advanced Dual Powered Willem EPROM Programmer - Nissan Forums: Nissan Enthusiast Forum

its not a dsm, but the guy is using the same programmer, chips as well as 32k bins.
he is burning two chips for a daughter board.

im so frustrated with this willem board, i am seriously about to shell out the money for an ostrich, but am concerned about the ds-map's lack of support due to the site being shut down atm. i might just grab one of the moates burn 2 so i can burn through tuner pro completely. but id rather just spend a bit more on the ostrich and tune on the fly.


after reading a bit more, i think my programmer is damaged. it fails to verify the chips after programing everytime. no matter what i set the offset to, it no longer will burn chips! oh well, i dont need all the feature this hobby programmer has anyways. i appreciate the help guys.

 

[steve]

i am seriously about to shell out the money for an ostrich, but am concerned about the ds-map's lack of support due to the site being shut down atm. i might just grab one of the moates burn 2 so i can burn through tuner pro completely. but id rather just spend a bit more on the ostrich and tune on the fly.

You'll have to explain what "ds-map's lack of support due to the site being shut down atm means". The issue with the DS-MAP site only has to do with long term support of the Jackal package from Curtis.

The Ostrich is a EPROM Emulator. TunerPro supports it and there is also a generic tool for loading code into it. I have a couple Ostrich and one I use all the time in non-automotive applications.

 

[trevor425]

i meant jackal on the whole ds-map comment, i recalled skimming the recent support thread here on tuners, and a growing concern for new and future users of the avaliablity of software and support.
i realize now, that the ostrich doesn't burn chips, i was thinking of the auto prom"s features. so really that doesnt solve my current issue anyways.

burn2 is in the shopping cart for now. i feel i should have gone with it from the start, but was distracted by all the bells and whistles of this willem, and the 40$ price tag.

im interested in the non automotive applications of the ostrich, care to elaborate?

 

[steve]

im interested in the non automotive applications of the ostrich, care to elaborate?

TunerPro and TunerPro RT - Professions Automobile Tuning Software

With that you can load any random file into the Ostrich and use it like a USB flash drive if you wanted. The 2700 family of ROM, and EPROMS were very popular devices. So I can plug the Ostrich into some of my older computer hardware and upload the contents rather than burning a chip for every change.

 

[polarmoment]

Does the newer Willem not have the offset box? Mine is getting on 10 years old now (EPR097g, i think) but there's just a box to type in the offset where you want it to start writing. For the SST chips, I just plug 8000 in and hit 'write.'

You must be logged in to view this image or video.

I do occasionally get validation errors if my laptop has gone into and come out of standby before trying to write a chip. It somehow fails to communicate with the port under that circumstance, but restarting always fixes it.

Another thing I've had prevent the burner from working is if the exe file is moved from the folder it was originally extracted into, or if the folder is moved at all for some reason.

Which version of the willem software are you using?

 

[trevor425]

yea, that looks identical to mine, i have tried the 8000 offset but i keep getting error codes during validation as you mentioned (unrelated to offsets i realize). im using the 97ja software recommended bye other willem users, perhaps ill try the 97g.
thanks for the tips, ill give them a shot after lunch cause i left the burner at home.