Calibration Missing

[ScrmnEagle]

Requesting assistance. I was flashing the ecm to dial in the speedometer and the new tank capacity and ran into some problems. I get the error message that the "calibration is missing" and "flash can is not able to determine the license status of this ecm". Attached is the calibration details and a screenshot during a recent flash.

Calibration Details

VIN 1GCHK23D57F1944XX
Serial BKN07015PRHR
Hardware N/A
Operating System 25803708
Calibration 25818885
BCC 5321
Operating System 25803708
Engine Operation N/A
Engine Diagnostics N/A
Engine N/A
Fuel System N/A
System N/A
Speedometer N/A

Calibration Screen Shot

15:33:42.093: Scanning for EFILive FlashScan V2 USB
15:33:42.109: Autodetect interface ...
15:33:43.937: Interface not detected
15:33:44.609: Scanning for EFILive FlashScan V2 HAPI
15:33:44.625: Autodetect interface ...
15:33:44.828: Interface firmware version: 2.6.35
15:33:44.828: Connection to [FSV2] interface is OK
15:33:44.890: Interface firmware model: FSV2
15:33:44.906: Interface firmware version: 2.6.35
15:33:44.937: Interface firmware date: May 03, 2010
15:33:44.968: FlashScan serial number: 003742023957
15:33:44.984: FlashScan license number: 003742023957
15:33:45.031: Disconnecting ...
15:33:45.890: CAN-VPW Bridge Deactivated
15:33:45.906: Disconnected
15:33:46.578: Scanning for EFILive FlashScan V2 USB
15:33:46.593: Autodetect interface ...
15:33:48.406: Interface not detected
15:33:49.078: Scanning for EFILive FlashScan V2 HAPI
15:33:49.093: Autodetect interface ...
15:33:49.296: Interface firmware version: 2.6.35
15:33:49.296: Connection to [FSV2] interface is OK
15:33:49.328: CAN-VPW Bridge Activated
15:33:49.421: Current protocol set to: "ISO 15765 CAN"
15:33:49.421: Autodetect PCM...
15:33:51.453: PCM not detected.
15:33:51.453: Autodetect ECM...
15:33:52.609: ECM not detected.
15:33:52.609: Autodetect TCM...
15:33:52.640: Connection to TCM is OK
15:33:52.671: Current protocol: No Protocol
15:33:52.734: Interface firmware model: FSV2
15:33:52.765: Interface firmware version: 2.6.35
15:33:52.781: Interface firmware date: May 03, 2010
15:33:52.812: FlashScan serial number: 003742023957
15:33:52.843: FlashScan license number: 003742023957
15:33:53.984: Current protocol: "ISO 15765 CAN"
15:33:54.000: Getting status...
15:33:54.296: Status: Calibration missing.
15:34:04.262: Preparing ECM for reflash...
15:34:05.465: ECM seed is: $AE2D
15:34:05.465: Unlock attempt 1 of 1
15:34:05.637: Initializing ECM...
15:34:06.450: Request GM operating system...
15:34:06.512: GM operating system: 52606128
15:34:07.653: Request serial number...
15:34:09.356: Serial number: 86J701401310
15:34:14.589: ECM is in an unknown state.
15:34:16.714: Clear emisison related DTCs...
15:34:16.777: Clear DTCs for all modules...
15:34:17.933: Autodetect interface ...
15:34:18.027: Interface firmware version: 2.6.35
15:34:18.027: Connection to [FSV2] interface is OK
15:34:18.027: Autodetect ECM...
15:34:18.667: ECM not detected.
15:34:19.511: Disconnecting ...
15:34:20.339: CAN-VPW Bridge Deactivated
15:34:20.339: Disconnected
15:34:20.355: Data transfer was interrupted.
15:34:23.222: Done!

How could the OS and calibration change during a flash. I have no idea what vehicle supports OS 25803708 or Calibration 25818885.

No disconnects were noticed, perhaps a surge in vehicle battery? Anyways, I am skeptical in operating the truck under these conditions. Even a full flash has not resolved the issue. Look forward to your evaluation of the situation.

I have used the following trouble shooting to this point:

Disconnected the batteries for 15 minutes and tried flash again.
EFLive unit lights up when plugged into the OBD-2 connector only (no laptop)
No Blown Fuses

Currently using EFILive V7.5.6 Build 117
Flashscan V2 Firmware 2.06.35
Flashscan V2 Boot Block 2.06.03

Thanks

[ScarabEpic22]

Interesting, first try the latest release (it is currently under the red text in the following link) and upgrade your firmware (even though it is the same version number, the date is June 30 and it is different, beta testing is happening behind-the-scenes) using EFILive Explorer.

Download Link

Are you trying to flash the ECM or TCM? Its not detecting your ECM at all, just the TCM (for a speedo flash Id imagine this make sense). Are you trying to flash an LBZ or LMM? Have you been able to successfully flash this same truck previously?

[ScrmnEagle]

Interesting, first try the latest release (it is currently under the red text in the following link) and upgrade your firmware (even though it is the same version number, the date is June 30 and it is different, beta testing is happening behind-the-scenes) using EFILive Explorer.

All releases, including beta are installed after pulling these codes.

Download Link

Are you trying to flash the ECM or TCM? Its not detecting your ECM at all, just the TCM (for a speedo flash Id imagine this make sense). Are you trying to flash an LBZ or LMM? Have you been able to successfully flash this same truck previously?

Flashing the ECM. Detects ECM with a red X, after upgrade a green checkmark on a LBZ system. I have been able to flash successfully in the past with no issues, at least with no complications of this magnitude. I will update my signature to avoid vehicle stats questions in the future.

[Tordne]

Definitely do try the latest pre-release software/firmware version. With this installed the versions will be:
- 7.5.6 Build 125
- 8.1.2 Build 105
- V2 firmware 2.067.35 (30 June 2010)

[ScrmnEagle]

Definitely do try the latest pre-release software/firmware version. With this installed the versions will be:
- 7.5.6 Build 125
- 8.1.2 Build 105
- V2 firmware 2.067.35 (30 June 2010)

That is the same versions currently installed on the laptop and handheld as we speak. Currently performing a full flash now.

Log keeps retrying previous block, erasing ECM flash menmory, ecm flash memory erased OK, then retrying. This cycle has been going for over an hour. Does this seem strange to any one?

On another note, what does the last 3 digits on a time stamp represent?

[GMPX]

It's found the ECM at one point as it shows the OS 52606128 (DSP5), but initially it is finding the TCM (the 2xxxxxx type OS numbers are the TCM).
Does the truck start and run?

[ScrmnEagle]

It's found the ECM at one point as it shows the OS 52606128 (DSP5), but initially it is finding the TCM (the 2xxxxxx type OS numbers are the TCM).
Does the truck start and run?

Yes

[Tordne]

So if we're certain that everything is up to date (including the 30 June 2010 firmware) this is interesting; we've not seen any similar behavior to draw upon. Out of interest are you able to read the ECM? Can you also perhaps send the debug files to me (support@efilive.com) as described here (http://support.efilive.com/kb_articl...8254-QOGC-9586). Please do only send the specific files for the read/flash attempt.

In a previous question; the extra 3 digits on the times recorded in the logs are thousandths of seconds.

[ScrmnEagle]

So if we're certain that everything is up to date (including the 30 June 2010 firmware) this is interesting; we've not seen any similar behavior to draw upon. Out of interest are you able to read the ECM? Can you also perhaps send the debug files to me (support@efilive.com) as described here (http://support.efilive.com/kb_articl...8254-QOGC-9586). Please do only send the specific files for the read/flash attempt.

[COLOR="rgb(0, 0, 0)"]Yes I am able to read the ECM, Funny thing though every tune uploaded is void of a operating system and not recommended for flashing. Missing checksums. Unfortunately I am unable to send the requested data since the EFI program will not allow me to program the ECM with the operating system and calibrations any longer. [/COLOR]

In a previous question; the extra 3 digits on the times recorded in the logs are thousandths of seconds.

That was my 1st impression. I was hoping that it might refer to the sectors of the ECM drive. Files requested in e-mail.

[Tordne]

Is your file in .tun or .ctd format? You're not getting an error like in this thread (http://forum.efilive.com/showthread....-t-Load-a-File) are you? You should be able to email me the calibration (even if it is corrupt)?