Offsets when burning different EPROMS
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
So other than filling the eprom up, what the actual purpose of stacking?
Does the ECU not always read from 0x00 ? can't you just write the bin once at 0 offset and be done?
Does the ECU not always read from 0x00 ? can't you just write the bin once at 0 offset and be done?
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- VL400
- Posts: 4991
- Joined: Sun Mar 01, 2009 2:54 pm
- cars: VL Calais and Toyota Landcruiser. Plus some toys :)
- Location: Perth, WA
- Contact:
Re: Offsets when burning different EPROMS
For 64k or less bins, it must end at 0xFFFF. The last two bytes (0xFFFE and 0xFFFF) are the reset address for the processor to know where to begin running code from.
If your EPROM is larger than the bin, burning with 0 offset and no stacking will mean full limp home mode with no code running.
You need to stack the bin to make the resulting bin the same size as the EPROM and not worry about any math, or burn one bin with an offset so the bin ends at 0xFFFF - ie 16K $5D bin on a VR auto memcal with 27C512, offset would be 0xC000 (0x10000-0x4000 = 0xC000).
Either method does the same thing in terms of how it will work in the ECU, just that one method means you need to understand hex and the other simply stack until it makes a file that matches the EPROM size - which TP has a really simple way of doing as shown by holden202t earlier in this thread .. http://pcmhacking.net/forums/viewtopic. ... 343#p38348
If your EPROM is larger than the bin, burning with 0 offset and no stacking will mean full limp home mode with no code running.
You need to stack the bin to make the resulting bin the same size as the EPROM and not worry about any math, or burn one bin with an offset so the bin ends at 0xFFFF - ie 16K $5D bin on a VR auto memcal with 27C512, offset would be 0xC000 (0x10000-0x4000 = 0xC000).
Either method does the same thing in terms of how it will work in the ECU, just that one method means you need to understand hex and the other simply stack until it makes a file that matches the EPROM size - which TP has a really simple way of doing as shown by holden202t earlier in this thread .. http://pcmhacking.net/forums/viewtopic. ... 343#p38348
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
Ok that makes sense now. So its the end of the file at 0xFFFF thats important?
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- antus
- Site Admin
- Posts: 8237
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: Offsets when burning different EPROMS
Yep. Reset vector. It'll be a 16 bit (2 byte) address. And the computer will jump to that address and start executing at power on. All the internal addresses in the code assume the file will be loaded at the top of the address space (known as top justified, in tunerpro terms). Once its sitting in the right spot your good to go.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
Cool, thanks for the clarification.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
Trying to burn a tune to a STTSF27512 but the car wont run other than limp home.
So after looking at different tunes that worked fine I noticed my tune appears to be the cal only and OS part missing.
How do I get the file from TP to save the whole bin as well? Some files I open and save are complete, but my tunes for the VR and my VP are incomplete BINs
Yes, I have stacked it, the stock BIN files stack and work fine in the car.
Any ideas? This one I unloaded isn't stacked in case you are wondering.
So after looking at different tunes that worked fine I noticed my tune appears to be the cal only and OS part missing.
How do I get the file from TP to save the whole bin as well? Some files I open and save are complete, but my tunes for the VR and my VP are incomplete BINs
Yes, I have stacked it, the stock BIN files stack and work fine in the car.
Any ideas? This one I unloaded isn't stacked in case you are wondering.
- Attachments
-
- OSE $12P V112 BLCD V6 VP vacationer.bin
- (32 KiB) Downloaded 399 times
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- VL400
- Posts: 4991
- Joined: Sun Mar 01, 2009 2:54 pm
- cars: VL Calais and Toyota Landcruiser. Plus some toys :)
- Location: Perth, WA
- Contact:
Re: Offsets when burning different EPROMS
Use the flashtool and get bin.
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
haven't got any of the hardware on that car, using old school EEPROM and burner.
Anyway, I reckon I got it. I open the stock BLCD bin and loaded the tune in the bin compare. Used he difference tool to copy all the cal stuff over and left the OS part untouched. The difference tool indeed showed my tune had empty OS section. So I just burned it to the chip as it is with 0x8000 offset. Fingers crossed!
Anyway, I reckon I got it. I open the stock BLCD bin and loaded the tune in the bin compare. Used he difference tool to copy all the cal stuff over and left the OS part untouched. The difference tool indeed showed my tune had empty OS section. So I just burned it to the chip as it is with 0x8000 offset. Fingers crossed!
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
Good news, no more CEl and limp home but wont start, I reckon I have the VATS on as I did borrow the tune from the VR. Going to have a look now.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- vlad01
- Posts: 7780
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Offsets when burning different EPROMS
All good, working now. Geez this tune is considerably better than the old one.
Solved my long issue of low power at mid to high revs, it was what suspected, false knock. Plus I have a more accurate VE table and other parameters to suit the engine.
Will add the tune to my built thread. Suits stock VN s2 and VP engines with pacemakers, no bell mouth and better intake, 65mm TB, stock injectors.
Solved my long issue of low power at mid to high revs, it was what suspected, false knock. Plus I have a more accurate VE table and other parameters to suit the engine.
Will add the tune to my built thread. Suits stock VN s2 and VP engines with pacemakers, no bell mouth and better intake, 65mm TB, stock injectors.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.