Procedure for changing to different year OS

[dropped2000]

I have a 2000 Silverado and would like to update it to a 2002 OS. It is a 5.3/4L60E 2wd. What files do I need and what is the correct procedure for doing this?

[Tordne]

Firstly, and most importantly you will need to have access to either the Commercial or Workshop version in order to perform a full-flash (operating system upgrade).

Then you need to decide if your are going to use an EFILive Custom Operating (http://www.efilive.com/downloads/downloads_customos.html). There is also a forum thread at that location which describes the required steps to use the Custom OS's. You will also need the stock GM operating system that matches the Custom OS you choose.

Otherwise you would just need to to get a tune from the appropriate vehicle (i.e. 2002 Silverado), and upload it.

I have a few tune files that you may be able to use either way on my Tune Repository (http://www.holdencrazy.com/EFILive/).

Then you start tuning...

Hope that helps some.

Regards,
Andrew

[dropped2000]

I do have the Commercial version already.

If I don't use a custom OS, all I have to do is a full flash with a 2002 .tun file?

What about the VIN? Do I just change the VIN in the 2002 .tun file to match my VIN?

[Dirk Diggler]

I do have the Commercial version already.

If I don't use a custom OS, all I have to do is a full flash with a 2002 .tun file?

What about the VIN? Do I just change the VIN in the 2002 .tun file to match my VIN?

Yup that is what i did for mine. Mkae sure you have the latest version of the software as it was added in 7.2.3 release 2

[Blacky]

I do have the Commercial version already.

If I don't use a custom OS, all I have to do is a full flash with a 2002 .tun file?

What about the VIN? Do I just change the VIN in the 2002 .tun file to match my VIN?

EFILive's full reflash procedure is "intelligent", unlike other packages on the market which destroy vehicle specific data. It will retain your VIN and other important data such as crank angle sensor error data.

Regards
Paul

[Steve Bryant]

Dropped 2000,
I first did a full flash of my 2000 OS to a Stock 2001 OS for a like vehicle from Rick's tune repository. Then a couple of weeks ago, I did another full flash to a custom OS and added my .tun file back in (via a regular calibration flash) and both times, it went without a hitch although I was nervous the first time.

One warning that has been mentioned elsewhere on the forum is that you should use a bench harness to do the full flash rather than your vehicle's ALDL connector. This isolates the PCM from other outside influences (data bus traffic) that could interrupt the full flash.

All my best,

Steve

[Scoota]

I do have the Commercial version already.

If I don't use a custom OS, all I have to do is a full flash with a 2002 .tun file?

What about the VIN? Do I just change the VIN in the 2002 .tun file to match my VIN?

EFILive's full reflash procedure is "intelligent", unlike other packages on the market which destroy vehicle specific data. It will retain your VIN and other important data such as crank angle sensor error data.

Regards
Paul
After you have loaded the CO's and tune file then (read the calibration from the PCM) by sucking up the PCM cal, the vehicle info will appear as paul has stated. You will then also be able to access the Custom Calibration window.

Cheers, Scotty.

[Till]

Dropped 2000,
One warning that has been mentioned elsewhere on the forum is that you should use a bench harness to do the full flash rather than your vehicle's ALDL connector. This isolates the PCM from other outside influences (data bus traffic) that could interrupt the full flash.

There is also an adapter for that, and I can't think of the name now.

On the passenger side, under the dash, there is the BCM module. To the left of the BCM are two connectors. In each, there is just a combe that connects all wires. You unplug those, and put in the adapter. Now you have a direct connection between the OBD-II port and the PCM.

Much less work than getting at the PCM itself. I am sure someone knwos the name of the adapter.

Till

[marcink]

There is also an adapter for that, and I can't think of the name now.

On the passenger side, under the dash, there is the BCM module. To the left of the BCM are two connectors. In each, there is just a combe that connects all wires. You unplug those, and put in the adapter. Now you have a direct connection between the OBD-II port and the PCM.

Much less work than getting at the PCM itself. I am sure someone knwos the name of the adapter.


Does anyone know the name or better part# for this adapter?

[AllCammedUp]

I do have the Commercial version already.

If I don't use a custom OS, all I have to do is a full flash with a 2002 .tun file?

What about the VIN? Do I just change the VIN in the 2002 .tun file to match my VIN?

Please (Paul or anyone else who has done the process) correct me if I'm wrong, but I thought the .TUN file was only the calibration portion of the PCM and not the operating system+calibrations. Hence, to upgrade to a newer OS I thought I would have to flash in a .BIN file (raw OS with the base GM calibration) and then download a new 'stock' TUN from the PCM once the BIN was flashed in, modify the 'new' TUN to have the same calibration settings from my 'old' TUN file (from the older OS) and then reflash the 'new' TUN back.

Is this not correct? From what it sounds like here, I can just grab any .TUN I want in any state of modification, flash it in with the full flash option, and it upgrades my PCM to whatever year that TUN is from and it brings with it whatever modifications are in the aforementioned TUN file.

[Blacky]

The *.tun files contain the entire 512K or 1Mb of PCm flash memory (i.e. calibrations AND operating systems) as well as a bunch of meta data, comments, history etc.

If you opt to do a calibration only relfash, then EFILive just picks out the 96Kb of calibration data from the *.tun file and flashes that into the PCM.

If you opt to do a full reflash, EFILive reflashes the entire 512K or 1Mb of calibrations AND operating system into the PCM.

The "special" case is the EFILive custom operating system base *.tun files. These *.tun files have deliberately had "labotomies". We zeroed out the entire 96Kb of calibration data and forced the calibration checksums to be invalid. That means after you have full-flashed one of EFILive's custom operating systems, the PCM will enter dead poll waiting for a valid calibration.

Then you need to perform a calibration only reflash from one of your own *.tun files that matches the new operating system. i.e. a *.tun file from the GM operating system from which the EFILive custom operating system was derived.

Ross has just finished writing a tutorial on how to upgrade to a new EFILive OS. It contains a list of all the GM<->EFILive operating system combinations. It should be available tomorrow.

Regards
Paul

[AllCammedUp]

Thanks for clearing that up Paul - I really do appreciate it. Not sure where my previous train of thought was from, but I was obviously wrong.

It's good to know the facts. Thanks!

[hpcubed]

The *.tun files contain the entire 512K or 1Mb of PCm flash memory (i.e. calibrations AND operating systems) as well as a bunch of meta data, comments, history etc.

If you opt to do a calibration only relfash, then EFILive just picks out the 96Kb of calibration data from the *.tun file and flashes that into the PCM.

If you opt to do a full reflash, EFILive reflashes the entire 512K or 1Mb of calibrations AND operating system into the PCM.

The "special" case is the EFILive custom operating system base *.tun files. These *.tun files have deliberately had "labotomies". We zeroed out the entire 96Kb of calibration data and forced the calibration checksums to be invalid. That means after you have full-flashed one of EFILive's custom operating systems, the PCM will enter dead poll waiting for a valid calibration.

Then you need to perform a calibration only reflash from one of your own *.tun files that matches the new operating system. i.e. a *.tun file from the GM operating system from which the EFILive custom operating system was derived.

Ross has just finished writing a tutorial on how to upgrade to a new EFILive OS. It contains a list of all the GM<->EFILive operating system combinations. It should be available tomorrow.

Regards
Paul

Is the tutorial available yet? If so, where is it located?

[Tordne]

Check out this thread (http://www.efilive.com/forum/viewtopic.php?t=1666).

I believe there will be a guide done for when the version 2 custom OS's get release, but this should cover you off for the time being.

Cheers,

[ToplessTexan]

There is also an adapter for that, and I can't think of the name now.

On the passenger side, under the dash, there is the BCM module. To the left of the BCM are two connectors. In each, there is just a combe that connects all wires. You unplug those, and put in the adapter. Now you have a direct connection between the OBD-II port and the PCM.

Much less work than getting at the PCM itself. I am sure someone knwos the name of the adapter.


Does anyone know the name or better part# for this adapter?

Serial Data Link Tester, J 42236-A.

http://www.efilive.com/forum/viewtopic.php?t=2005

[JR_VETTE]

Ok, I'm glad this thread came back 'up'. I have EFILive Commercial, and was all set to update my 99 OS to a 02 OS. I was doing great, copying the various tables from my 99 calibration over to the 02 calibration. When I got to copying the Spark tables, I got stumped on some of the differences. For example, the stock 02' calibration has some pretty significant values for the Fuel Mixture Spark Correction table, where my 99' calibration has all 0's. Optimal Timing was another area that stumped me. There were other areas that stumped me, but that's enough for now. I'm looking for someone that has done this. Better yet, a 01 or 02 BIN file with compatible stock 99/00 MN6 calibrations would be great :lol: . I have a few mods coming up (LT headers, intake manifold, and possibly a CAM), and I'd like to get ready for them as much as possible.

I thought this was a great idea at first, but really the only benefit I can see is losing the Backup VE table, and being 'ready' for a custom OS if I ever decide to go that route.

Feel free to PM or email me.

Oh, and this is all on my 99 C5 MN6 coupe.