OS Swapping - How tusually o Please!

[trlrider]

Morning all!
I apologize if I have chosen the wrong thread category.

Have acquired a couple of ECU/PCM's to experiment/learn with on the bench. (price was right: free) Oddly enough both are out of 2000 GMT800's and show to have the 9381344 operating system. The OS searches in the forums has found very little .xdf support and suggestions are usually made to switch to a more supported OS. GM TIS shows the 9381344 was replaced with the 12205612 OS at some point.


Having searched with multiple criteria, have yet to find out a explanation how to do such a OS swap. Probably using the wrong search criteria knowing my countyline brain.

I have a operational bench harness, as well as TunerPro, TunerProRT, and PCMHammer on the laptop. Used LSDroid to do the initial read with a OBDLink MX+

One of these may eventually end up in a 5.3 swap into a early '80's square body.

Thanks all, have learned allot on the forum and have a long way to go.

[Neukam]

To swap the OS with PCM Hammer, go to Tools-Write Full Flash (Clone) and load a bin with the OS and calibration that you want to use

[B52Bombardier1]

If it is a stock unmolested original GM OS BIN, there's a big list of things you will need to do with that BIN in Tuner Pro before it'll support your 5.3 liter motor. I use variations of the following OS BINS because they have XDF files that are richly developed:

12208322

12212156

12202088

12587603 - only for the 1 megabyte PCM devices

I also keep a long list of things to defeat in the OS prior to writing the BIN to my lab rat and in use PCM devices.

Rick

[trlrider]

PC Hammer - check
.bin - check
OS System - there in lies the question.

Does having the correct .xdf and .bin constitute the complete operating system, or is there something else that is needed, such as cloning from a functional PcM.

Sorry, but I have not found what constitutes the complete operating system to do this.

Thank You for your time and putting up with us newbies

[trlrider]

Bear with me, as I am digesting allot of information lately.
Both these came PCM's came from 2000 5.3/4L60E GMT800 vehicles, one a Tahoe the other a 1500
The 5.3 that will probably go in this unit was a 2002 and I will be using a non-computer controlled transmission so the .bin would be for a manual.

As far as I know, the PCM's were unmolested.

Thank You for the .bin suggestions.

If it is a stock unmolested original GM OS BIN, there's a big list of things you will need to do with that BIN in Tuner Pro before it'll support your 5.3 liter motor. I use variations of the following OS BINS because they have XDF files that are richly developed:

12208322

12212156

12202088

12587603 - only for the 1 megabyte PCM devices

I also keep a long list of things to defeat in the OS prior to writing the BIN to my lab rat and in use PCM devices.

Rick

[B52Bombardier1]

The XDF file is ONLY used to interpret and edit the BIN file and DOES NOT get written to the PCM. It DOES NOT become part of the OS. The XDF and the BIN MUST MATCH each other by OS name. For example, you will wind up with an unusable BIN if you attempt to edit a 12212156 OS BIN with an XDF for 12202088.

The BIN is the complete operating system. P01 PCM devices (red/blue connectors) all use OS files that are 512k bytes in size. The P59 PCM devices (green/blue connectors) all use OS files that are 1 megabyte in size.

Furthermore, you will be completely overwriting whatever BIN / OS is currently on your experimental junk yard PCM devices though for grins, I'd probably save a copy of the original OS. But really, its likely just taking up space on your hard drive and I've never found a useful reason to keep any BIN that I cannot find a matched XDF for.

Rick

[trlrider]

Rick, Thank You! That is the answer I was looking for, and makes total sense now.

Yes, I have the existing .bin saved in a file. Time to play ( I mean experiment) now!

My 2004 has the P59 PCM and already exploring what may make my life easier on that one and has the more common operating system.

Thanks again,

Louis

The XDF file is ONLY used to interpret and edit the BIN file and DOES NOT get written to the PCM. It DOES NOT become part of the OS. The XDF and the BIN MUST MATCH each other by OS name. For example, you will wind up with an unusable BIN if you attempt to edit a 12212156 OS BIN with an XDF for 12202088.

The BIN is the complete operating system. P01 PCM devices (red/blue connectors) all use OS files that are 512k bytes in size. The P59 PCM devices (green/blue connectors) all use OS files that are 1 megabyte in size.

Furthermore, you will be completely overwriting whatever BIN / OS is currently on your experimental junk yard PCM devices though for grins, I'd probably save a copy of the original OS. But really, its likely just taking up space on your hard drive and I've never found a useful reason to keep any BIN that I cannot find a matched XDF for.

Rick