T43 reflash fault solved

[Blacky]

EDIT: This problem has not been solved with the latest update, please don't attempt to program any 2010 model 6 speed TCM's until we announce a fix.

After many hours of testing and lots of late nights, pizza and caffiene I believe the T43 reflash fault has been fixed.:fluffy:
The fault was only in the FlashScan/AutoCal firmware so to fix it all you need to do is to update your FlashScan firmware with the firmware (V2.06.17) attached to this thread.
The AutoCal firmware has not been updated yet, but will be shortly. Once it is updated it will be added to this thread.

If you encounter any problems with this new firmware please post in this thread.

Instructions:


Save the attached file into the folder: \Program Files\EFILive\V8\Firmware.
Connect FlashScan to your computer via the USB cable.
Then start EFILive_Explorer, that will automatically start the EFILive Control Panel program (i.e. EFILive_Hapi) which will detect the new firmware file and display a balloon tip indicating that updated firmware is now available.
Click on that balloon tip (or on the FlashScan icon in the system tray if no balloon tip appears). That will cause the EFILive Control Panel to be displayed.
Select the Firmware screen and click on the [Update] button.


Regards
Paul

[gmh308]

:rockon: And I thought it was just me when I had the write failures...:)

[Blacky]

Update:

With this V2.06.17 firmware, you may get error $517 when using BBR to read a controller. The error occurs at the end of the read, when FlashScan attempts to verify the contents of the *.ctd file. The *.ctd file will be corrupt and will not be usable.

It is being fixed and an update will be available asap.

Regards
Paul

[mr.prick]

Does this FW fix the mysterious connection dropping issue w/passthru?

[Blacky]

Does this FW fix the mysterious connection dropping issue w/passthru?

Given that I can't reproduce the drop out during logging, I can't say for sure. However, the changes that were made to fix the T43 issues only apply to CAN based controllers.

So if you were getting drop outs on a VPW based vehicle then it probably won't help.

However, I'll be interested to know if it still drops out with this new firmware. Maybe other changes/optimizations have fixed the problem.

Regards
Paul

[ScarabEpic22]

Any update to the BBR read error this fw supposedly causes?

[Blacky]

Its being tested this weekend. Hopefully it will be available early next week.
Paul

[ScarabEpic22]

Thanks, hasnt been an issue for me yet but my 4 year old Optima RedTop bit the dust 2 days ago so I havent been driving anywhere let alone reflashing!

[joecar]

Bummer about your Optima (which model was it...?), what happened to it...?

[ScarabEpic22]

Its a RedTop, cant remember what model it is but Ill be pulling it soon enough. Probably going to have to wait until late morning tomorrow after my next final is over so I can get a new battery. I want to get a YellowTop and then swap the stock Delco from my SS into my 02 as I will be putting a system in my SS but Ive heard Optima's quality has really gone downhill in the last few years.

Any suggestions?

[Highlander]

WIll let you know if it drops out. I think i had also a bad cable which I am fixing. Hopefully with this update everything goes north again.

[proflash]

I keep having a problem with the t43 on a new e2 maloo ute and keep getting the same error

I have the latest boot block and firmware update but all i get is a message that the checksum is invalid.



12:36:53.265: Scanning for EFILive FlashScan V2 USB
12:36:53.281: Autodetect interface ...
12:36:55.078: Interface not detected
12:36:55.703: Scanning for EFILive FlashScan V2 HAPI
12:36:55.718: Autodetect interface ...
12:36:55.781: Interface firmware version: 2.6.17
12:36:55.781: Connection to [FSV2] interface is OK
12:36:55.812: Interface firmware model: FSV2
12:36:55.843: Interface firmware version: 2.6.17
12:36:55.859: Interface firmware date: Dec 04, 2009
12:36:55.875: FlashScan serial number: 003616934237
12:36:55.890: FlashScan license number: 003616934237
12:36:55.921: Disconnecting ...
12:36:56.671: CAN-VPW Bridge Deactivated
12:36:56.671: Disconnected
12:36:57.296: Scanning for EFILive FlashScan V2 USB
12:36:57.312: Autodetect interface ...
12:36:59.093: Interface not detected
12:36:59.718: Scanning for EFILive FlashScan V2 HAPI
12:36:59.734: Autodetect interface ...
12:36:59.796: Interface firmware version: 2.6.17
12:36:59.796: Connection to [FSV2] interface is OK
12:36:59.828: CAN-VPW Bridge Activated
12:36:59.890: Current protocol set to: "ISO 15765 CAN"
12:36:59.890: Autodetect PCM...
12:37:01.921: PCM not detected.
12:37:01.921: Autodetect ECM...
12:37:01.953: Connection to ECM is OK
12:37:01.953: Autodetect TCM...
12:37:01.984: Connection to TCM is OK
12:37:02.000: Current protocol: "ISO 15765 CAN"
12:37:02.031: Interface firmware model: FSV2
12:37:02.062: Interface firmware version: 2.6.17
12:37:02.078: Interface firmware date: Dec 04, 2009
12:37:02.093: FlashScan serial number: 003616934237
12:37:02.109: FlashScan license number: 003616934237
12:37:04.171: Autodetect interface ...
12:37:04.250: Interface firmware version: 2.6.17
12:37:04.250: Connection to [FSV2] interface is OK
12:37:04.250: Autodetect TCM...
12:37:05.296: TCM not detected.
12:37:06.343: Getting status...
12:37:06.359: Status: Calibration missing.
12:37:37.796: Bootloader version: T43a_v1.2C (09E2-1B00)
12:37:37.796: Preparing TCM for reflash...
12:37:37.828: TCM reports "Not secured!"
12:37:37.828: Initializing TCM...
12:37:39.078: Initializing TCM, step 1 of 4
12:37:39.078: Initializing TCM, step 2 of 4
12:37:40.343: Initializing TCM, step 3 of 4
12:37:42.843: Initializing TCM, step 4 of 4
12:37:43.265: Initializing bootloader...
12:37:43.609: Initializing bootloader, step 1 of 5
12:37:43.953: Initializing bootloader, step 2 of 5
12:37:44.312: Initializing bootloader, step 3 of 5
12:37:44.656: Initializing bootloader, step 4 of 5
12:37:45.000: Initializing bootloader, step 5 of 5
12:37:46.031: TCM ready for reflashing.
12:37:46.125: Request GM operating system...
12:37:46.140: GM operating system: 24254909
12:37:47.312: Request serial number...
12:37:47.375: Serial number: DV1952020109
12:37:48.312: Erasing TCM flash memory... (please wait up to 120 seconds)
12:37:51.156: TCM flash memory erased OK
12:37:51.406: Reflashing TCM's memory...
12:38:48.140: Total time: 00:56
12:38:48.140: Data compression achieved: 8.8%
12:38:48.453: Checksum of flash failed after write completed. Please reflash the controller.
12:38:48.453: TCM is in an unknown state.
12:38:50.578: Clear emisison related DTCs...
12:38:52.625: Autodetect interface ...
12:38:52.703: Interface firmware version: 2.6.17
12:38:52.703: Connection to [FSV2] interface is OK
12:38:52.703: Autodetect TCM...
12:38:52.718: Connection to TCM is OK
12:38:53.734: Clear DTCs for all modules...
12:38:55.796: Autodetect interface ...
12:38:55.875: Interface firmware version: 2.6.17
12:38:55.875: Connection to [FSV2] interface is OK
12:38:55.875: Autodetect TCM...
12:38:55.890: Connection to TCM is OK
12:38:57.203: Disconnecting ...
12:38:57.953: CAN-VPW Bridge Deactivated
12:38:57.953: Disconnected
12:38:57.953: Reflash failed.
12:39:00.390: Done!

[GMPX]

Can you please try the firmware attached to this post instead and let us know if those solves your problem.
From Paul's original post:

Instructions:


Save the attached file into the folder: \Program Files\EFILive\V8\Firmware.
Connect FlashScan to your computer via the USB cable.
Then start EFILive_Explorer, that will automatically start the EFILive Control Panel program (i.e. EFILive_Hapi) which will detect the new firmware file and display a balloon tip indicating that updated firmware is now available.
Click on that balloon tip (or on the FlashScan icon in the system tray if no balloon tip appears). That will cause the EFILive Control Panel to be displayed.
Select the Firmware screen and click on the [Update] button.

Thanks,
Ross

[proflash]

still same issue and checksum fail

[GMPX]

Thanks for trying, sorry it's still not working. I don't have an immediate fix, can you please keep trying to flash it, you might get lucky and it will take on one of the attempts. We'll keep working on it now.

[proflash]

I'll keep on trying, pity its a brand new car and the owners getiing nervous!!!

[GMPX]

We all are!!

[proflash]

I appreciate the work you guys do so much more now

[joecar]

proflash, welcome to the forum...:cheers:

[proflash]

proflash, welcome to the forum...:cheers:

thanks

I been here a few times but tend to just read and observe, I think I;ll start to contribute a little more now.

[GMPX]

Please refer back to the first post in this thread, there is still a problem programming 2010 model TCM's.

[Chuck CoW]

EDIT: This problem has not been solved with the latest update, please don't attempt to program any 2010 model 6 speed TCM's until we announce a fix.

After many hours of testing and lots of late nights, pizza and caffiene I believe the T43 reflash fault has been fixed.:fluffy:
The fault was only in the FlashScan/AutoCal firmware so to fix it all you need to do is to update your FlashScan firmware with the firmware (V2.06.17) attached to this thread.
The AutoCal firmware has not been updated yet, but will be shortly. Once it is updated it will be added to this thread.

If you encounter any problems with this new firmware please post in this thread.

Instructions:


Save the attached file into the folder: \Program Files\EFILive\V8\Firmware.
Connect FlashScan to your computer via the USB cable.
Then start EFILive_Explorer, that will automatically start the EFILive Control Panel program (i.e. EFILive_Hapi) which will detect the new firmware file and display a balloon tip indicating that updated firmware is now available.
Click on that balloon tip (or on the FlashScan icon in the system tray if no balloon tip appears). That will cause the EFILive Control Panel to be displayed.
Select the Firmware screen and click on the [Update] button.


Regards
Paul


That's strange Paul...The EFI LIVE software on my primary tuning laptop is over a year old and I've tuned quite a few 2010 Camaros with T43s....

I did actually have trouble reading one or two and switched to a different vintage V2 cable, but writing them was never a problem.....

What's the fault?

Chuck CoW

[Blacky]

I did actually have trouble reading one or two and switched to a different vintage V2 cable, but writing them was never a problem.....

What's the fault?

Chuck CoW

The fault is at the end of the re-flash the check-sums are wrong causing the TCM to reject the newly programmed data and refuse to function until a clean flash is made.

Regards
Paul

[GMPX]

That's strange Paul...The EFI LIVE software on my primary tuning laptop is over a year old and I've tuned quite a few 2010 Camaros with T43s....That is because the 2010 Camaro is actually using a 2009 TCM and 2009 OS. 2010 Vette and CTS-V are real 2010 TCM's, these will give you trouble.

Cheers,
Ross

[gmh308]

That is because the 2010 Camaro is actually using a 2009 TCM and 2009 OS. 2010 Vette and CTS-V are real 2010 TCM's, these will give you trouble.

Cheers,
Ross

The T43 hardware is finally changed for 2010? Or is it purely the OS change?

[GMPX]

Don't know Ian, all I know is that we can't flash them at this stage

[LSXTurbo]

I have been stuck on the dyno with 2 late model VE Holdens.

Got the latest software and the lates V2 firmware.

thanks

[Chuck CoW]

That is because the 2010 Camaro is actually using a 2009 TCM and 2009 OS. 2010 Vette and CTS-V are real 2010 TCM's, these will give you trouble.

Cheers,
Ross

Finally happened..... I got another 2010 L99 Camaro the other day.... I can write T43 files all day long with my V2 and old software....

But, Reading fails half way through with my current V2 (and old software) but when I switch to a V2 with more current firmware, it reads the files good.

Chuck CoW

[HTMtrSprt]

I just had this happen on a '07 'Vette w/ OS 24239353. Tried programming with both the old firmware (2.04.xx) and now the newest (2.06.28) in the V2. Keeps saying the same thing..... checksum failed, did not program.

What next?

[GMPX]

The problem you are having is probably not exactly the same as the issues with the 2010 models. The 2010 models had a change in the TCM that caused us problems.

Although you updated the firmware did you update the software as well?

[HTMtrSprt]

Problem solved..... I think someone had been in the car and 'molested' the file, screwing up the checksum. I downloaded a stock cal from HoldenCrazy and it loaded just fine.