t-side (so literally 0x3CB3 in the combined bin)
it's just an extra byte in the 'flashing string' section that i use to store my version byte. i wonder if it's not stored, or if it's not reading it, or what
hah you know what's super funny?
it doesn't write at all.
no wonder it was so bloody fast
the beta i posted is compiled to dummy write so i can test data ordering in the flash routine.
lets try this again!
here, rebuilt...sorry bout that.
even more changes in this version too, working more on the wideband stuff.
ok here goes. flash worked with optimize and the patch is registering in eehack v0.1 ...i think read flash is not working by that i mean that eehack will pull the bin but not to prompt to save it, it just goes back to the main eehack app. in scan9495 error 51 eeprom programming dtc shows up. when comparing before and after flashes 0x3848 Shift Time (sec) Vs. %TPS Vs. Shift, Normal Mode, High Alt. table has 3858 as FF instead of what was originally there. 0x3cb3 was 00 now 01
Attachment 9947
97z28 A4 obd1 swap(16188051)
Tunerpro Newbie
ah, is that an automatic transmission bin? it shouldn't have done that. i'll look into it.in scan9495 error 51 eeprom programming dtc shows up. when comparing before and after flashes 0x3848 Shift Time (sec) Vs. %TPS Vs. Shift, Normal Mode, High Alt. table has 3858 as FF instead of what was originally there.
i guess i screwed the checksum up.in scan9495 error 51 eeprom programming dtc shows up.
thanks i'll look into that tooi think read flash is not working by that i mean that eehack will pull the bin but not to prompt to save it
appreciate the testing!
i would recommend against using the optimizer for the time being...obviously needs some work.
would be curious if the patch works though
actually i bet read bin didn't save 'cause the checksum is screwed up. it will refuse to write to disk and print a warning message in that event.
Bookmarks