Flashhack - New LT1 flash tool

[yoheer]

Can you add file converter?
I've found some tuned files, but they are .LT1
Dunno how to convert em into .bin

[steveo]

how about tools > ee bin converter

select current format
load file
select desired format
save file

[yoheer]

oh great. already done! thanx

[toyinhawaii]

hi all,
After the long process of learning the tuner pro, eehack, flashhack (still new on this)i did some editing to my bin with help from you all here, especially Lemarky Dissod. Then i had Moe (Moe horsepower)(Thanks Moe!) fine tune my bin file for the Cam, headers, tires ,gear ratio and shift kit. Looks like i'm now ready to rock and roll. i noticed i am the first to reply back to this thread since September? didnt notice if there was another thread somewhere. i am ready to flash my bin to the PCM and just wanted to confirm the process. Sorry if it is here somewhere in the 20 pages of this thread. i did look at the FLASHHACK download page and saw the "what not to do's". i havent ventured this far, so from what i can read on the Flashhack it does seem pretty straight forward...... but,i dont trust myself lol!. just wanted to confirm the process like take my tuned bin file, upload it to the "load bin" then use the "write calibration" to flash it to the ECM. at what point do i turn the key on(obviously before the process), etc. Just wanted to know if there was more to this step by step process. thanks so much for the help!

[steveo]

- key on
- open flashhack
- load bin
- press write calibration
- make sure it finishes (it will tell you)

if it does not finish do not turn your key off, just press write again until it works. if that does not work, you can close and re-open flashhack, load a different bin, or try a different computer or cable.

[toyinhawaii]

Thanks Steveo! As soon as i completed the upload and cranked it over it sounded a whole lot better, idle went from a 550-ish RPM to a 750-ish RPM, seems like the perfect idle now. took it out on the main street and man O' man what a difference..like night and day ,awesome feeling after it sitting for 15 yrs. Although the 4L60E w/shift kit, shifting seems a little strange...IDK...a lot of torque? maybe the 3:08 gears??? i heard that it probably needs to be more of a 3:42... but man what a feeling

[1gcrazy]

i have reports back that the P66 V6 flash has successfully written without bricking but does need more testing. i wonder if anyone can help me find some V6 people that are brave? i haven't seen robertisaar around in a million years, and i don't really know any others.

Back from the dead but if you still need someone let me know. I have hundreds of ECU's at my disposal for flashing. Not necessarily anything in particular but many old GM units.

[spfautsch]

Hey steveo couple questions when you have a moment. Absolutely nothing urgent. First, what version of QT are you currently building with on winders? Also, have you heard anything from any of the other linux zealots?

I reported back that I was able to compile on Ubuntu quite a while ago, but I don't think I ever tested because frankly, eehack has worked flawlessly for reads and flashing (actually, everything I've asked it to do).

I recently acquired a problem ecu that would freeze during reads and the t-side wouldn't reset. So I grabbed the latest flashhack source and built it on QT 5.15.2.

On the bench I found eehack would read and flash without issue. Haven't tried it in the car yet - about to go do that. But flashhack was giving me this on the bench:

MFR: FTDI
SER# A104VFGG
VENDOR: 403
PRODUCT: 6001
27.887: Reconnecting to ALDL bus, please wait....
27.887: DEBUG::Listening for ALDL heartbeat to determine current bus master...
28.212: DEBUG::Got heartbeat frame for current master f1
28.213: DEBUG::Silencing bus master device f1
29.202: DEBUG::Found heartbeat, sending mode 8 request with predelay 2
29.204: COMM::Sent message: F15608B1
29.519: COMM::Attained bus silence, stable connection is now likely.
29.543: Successfully connected to the ALDL bus.
29.543: COMM::Sent message: F45605B1
29.569: COMM::Recieved reply: F4580D023372
29.570: DEBUG::Unlocking TSIDE
29.575: COMM::Sent message: F4570D01A7
29.601: COMM::Recieved reply: F4590D011E0384
29.607: COMM::Sent message: F4590D02E1FCC7
29.633: COMM::Recieved reply: F4580D02AAFB
29.639: COMM::Sent message: F45605B1
29.665: COMM::Recieved reply: F45705AA06
29.665: Uploading kernel to TSIDE
29.666: ERROR! Cannot upload code: program TSIDE_KERNEL is not loaded.
29.667: ERROR! Failed to upload program TSIDE_KERNEL to TSIDE
29.667: ERROR! Failed to load kernel for TSIDE
29.668: ERROR! Could not connect or load the kernel.
32.480: COMM::Sent message: F056F0CA
35.277: COMM::Sent message: F056F0CA
35.283: COMM::Reply was not as expected: f056f0ca vs 5600B9F0
35.539: Reconnecting to ALDL bus, please wait....

This ecu looked like it spent the majority of it's life sitting in a car sans hood (out in the elements). I initially assumed the problem was water infiltration because it looked like it had been in a flood. Three of the six screws holding the clamshells together broke on removal, and had to be drilled out. I also had to give it a pretty good whack because the corner that sits lowest in the y-body was corroded together on the alignment dowel. It appeared to be clean inside, but I was afraid it was going to be a basket case.

Anyway, there were several hundred warnings during compile so I may try going back to a really old QT and see what happens. If memory serves lots of references to deprecated or soon-to-be deprecated libraries.

PS - I ran across the picture of your bench rig researching how to connect mine up. Extra love if you used drywall screws on the PCBs. :-)

[kur4o]

Looks like the kernel program are missing or cant be loaded. They should be in the 68k folder.

Upon startup of flashhack press debug and post what is in the log.

It did compile fine with 5.6.0.0

The official release uses much newer qt.

[spfautsch]

Yeah, it occurred to me this morning that I was running the executable from the build folder. Thanks, works now.

Now to figure out what's up with the ecu. In car it still won't read though I haven't tried with flashhack yet. Starts, runs and logs ok with eehack albeit with numerous disconnects.

I guess I need to open it back up and compare the boards to one of my 1333s. I did notice it has a 16188309 knock module in it.

[steveo]

just for fun, if it's a really stubborn car but datalogging works you should be able to retrieve your bin with the universal read tool (tools -> select tool if you've already picked EE)

it's much more likely to plow through and get your data as it doesn't have to load the kernel or do anything crazy to work, it just uses the regular datastream. you need to configure it to read device F4 for the tside and E4 for the eside.

in its current state this would give you two 64k bins you'd have to stack to make a traditional bin, also verify the checksums.

fortunately flashhack has you covered there too, the ee bin converter tool (tools menu) will both verify and stack those bins for you once you have them both. just load them each with eside and tside then change the mode to standard and hit save. don't use 'raw' that's for bins read/written directly from the chip with scrambled address lines

as far as build environment yes it has lots of warnings with newer QT versions, but it builds and runs fine. QT is a real pain with 'depreciating' old features so they give you years of notice via these 'warnings'. eventually if the feature truly disappears we can go rewrite that part easily. maybe if i have time i'll go give it a tuneup.

[spfautsch]

just for fun, if it's a really stubborn car but datalogging works you should be able to retrieve your bin with the universal read tool (tools -> select tool if you've already picked EE)

That doesn't sound like fun to me. Maybe if I get the urge to try and hack the climate control will I glut for such punishment - if it's on the ALDL.

And it wasn't necessary anyway, flashhack was able to reconnect and read the entire bin. Really cool stuff steveo!

Four times throughout the process I saw this:

COMM::Sent message: F45C060200200BBD8040
COMM::Reply was not as expected: f45c060200200bbd8040 vs F45C060600200BBD8040
DEBUG::Trying to reconnect to bus...
Reconnecting to ALDL bus, please wait....
DEBUG::Listening for ALDL heartbeat to determine current bus master...
The bus is silent.

I only have the one car, but this appears to be a different ecu - guessing an 8051. As I mentioned there was no part # sticker on it when I acquired it. There are two un-populated pads for ICs on the t-side that are present on the 1333. Upper left by the interconnect ribbons.



Edit: these ICs in the 1333 t-side are the same PN as the other two 20 pin four-sided smt chips in this area: 014 034987

Edit 2: also noticed another un-populated 28 pin IC directly adjacent to the flash chip on the upper right side. Also a missing smt diode and through-hole ceramic capacitor. curious if anyone with an 8051 can confirm these part differences.

Whatever the difference is, this ecu doesn't talk on the ALDL as cleanly in my Y body. I've read and flashed both of my 1333 ecus in this car with eehack numerous times without so much as a hiccup.

Edit 3: here's what the 16181333 t-side outer plane looks like for comparison

[NomakeWan]

That doesn't sound like fun to me. Maybe if I get the urge to try and hack the climate control will I glut for such punishment - if it's on the ALDL.

It is not on the ALDL. The Entertainment and Comfort Bus which handle the radio and climate control are their own separate "network," and the HVAC system has to be patched into the ALDL connector manually. This is done by jumping pin 4 of the HVAC control head to pin 14 of the ALDL. Note that this still does not put it on the CCM's serial bus; all it does is connect the full E&C bus to a separate pin on the ALDL so that a Tech 1A/Tech 2 can be used for diagnostics.

Dumping using a read command reminds me of my Subaru SVX days. That was how we dumped the ECU and TCU on those cars. Lots of fun.

[spfautsch]

Thanks, that tells me it's barely worth the effort just to dump the program to fix the one tiny annoyance. Having watched the batee videos on these I don't recall seeing any eeproms on either boards anyway so it's probably a futile effort to begin with.

Still hoping to find confirmation of the ecu models in the pics above. It seems likely the less populated board is an 8051 and not an older revision of a 1333. Still curious what causes the difference with ALDL errors. Next rainy day I'll spend some time looking for the datasheet for the big IC that's missing.

[JimCT_9C1]

Still hoping to find confirmation of the ecu models in the pics above. It seems likely the less populated board is an 8051

So in the name of science I opened up my spare PCM from a 95 F-body - looks just like the image posted by spfautsch above with the three unpopulated pads.
Mine appears to be a reman - it has a new case (no sticker), but labeled inside as 8051.

Jim