93 V6 flash

[dbuster]

I haven't had a chance to do any more data logging so I am practicing with what I have.

Down loaded bin from bench unit and loaded into tuner pro, opened data logs in trimalyzer and followed instructions to modify bin in tuner pro and loaded new bin in eehack.

Loaded new bin and old bin in eehack flash tool, ran program stability test, passed. Clicked upload bin file to ecm, accepted the warning that i may make a brick and got -eehack error must select either T side or E side to flash- On flash tool select E side or T side are not highlighted, I cannot select them.

[kur4o]

Download flashhack from steveo site. It now supports v6 pcm. First do some test reads, and use only the files you have read with flashhack to avoid any file format difference.

eehack uses full binary files which are 128kb. flashhack uses partial binaries which are cut from the unneeded blank regions and the files size is 64kb.

Only 64kb files are compatible with tunerpro xdf.

For flashing v6s I only recommend flashhack from now on. The file format it uses is the same for the tunerpro xdf and there is no need to do any file conversions.

[dbuster]

ok, thanks I will give it try.

[dbuster]

Down loaded flashhach, selected v6. Assuming that "Read calibration" is how I down load bin I get an error message.


DEBUG::flashhack Version BETA 0.5.8
DEBUG::Building read region map for TSIDE
DEBUG::Building read region map for ESIDE
Entering programming mode on ESIDE
DEBUG::SERIAL: Opened port COM3
DEBUG::SERIAL: Port info: USB Serial Port
MFR: FTDI
SER# FT0DOCB5A
VENDOR: 403
PRODUCT: 6001
Reconnecting to ALDL bus, please wait....
DEBUG::Listening for ALDL heartbeat to determine current bus master...
DEBUG::Got heartbeat frame for current master e4
DEBUG::Silencing bus master device e4
DEBUG::Found heartbeat, sending mode 8 request with predelay 2
Successfully connected to the ALDL bus.
DEBUG::Unlocking ESIDE
Uploading kernel to ESIDE
DEBUG::Executing prepared program ESIDE_KERNEL on ESIDE
DEBUG::Executed ESIDE_KERNEL on ESIDE
Entering programming mode on TSIDE
DEBUG::Unlocking TSIDE
Uploading kernel to TSIDE
DEBUG::Executing prepared program TSIDE_KERNEL on TSIDE
DEBUG::Executed TSIDE_KERNEL on TSIDE
Kernels loaded, ECM executing from RAM.
ERROR! Cannot upload code: program TSIDE_READ is not loaded.
ERROR! Failed to upload program TSIDE_READ to TSIDE
ERROR! Flash read sub-routine upload failure.
ERROR! Read procedure failed. Review the log.
DEBUG::Rebooting TSIDE
DEBUG::Executing prepared program REBOOT on TSIDE
DEBUG::Executed REBOOT on TSIDE
Rebooted TSIDE
DEBUG::Rebooting ESIDE
DEBUG::Executing prepared program REBOOT on ESIDE
DEBUG::Executed REBOOT on ESIDE
Rebooted ESIDE
DEBUG::Giving back ALDL bus master to E4

[kur4o]

The read routine is missing. Extract these in the P66V6 folder and give it a try.

[dbuster]

"Windows cannot open the folder"- The compressed folder(P66V6_read.rar.zip) is invalid

[NomakeWan]

"Windows cannot open the folder"- The compressed folder(P66V6_read.rar.zip) is invalid

It's a .rar file, which the forum doesn't allow you to upload, so he added .zip to the end to get around that. Remove the .zip and it will open.

[steveo]

i'll be uploading a new version tonight that'll fix that.

[steveo]

new version is up there.

[dbuster]

Down loaded new version, will try shortly.
Thanks

[dbuster]

Ok, I believe that works! I was able to pull the bin run it through tuner pro and flash it back onto the ecm and read it again with flashhack. I will play with it some more tonight.
thank you, thank you!

[steveo]

that's good news, thanks for trying it out

[dbuster]

Finally had time to get back to this, did a few different flashes on my test unit and one on my car. It worked, successfully flashed a modified bin and my car still runs! Still have a lot to learn. Thanks stevo and kur4o for all your help and guidance. I will be back with more questions.

[kur4o]

Glad to hear it is working as expected.
You are welcomed for any questions and suggestion.

[dbuster]

Looking over some logs I see that the spark advance never goes higher than 1, last log attached.