HDW No 12589162

[Fixed until broken]

Ok so on my last junkyard run I grabbed a GM PCM to try my hand at this again. I haven't played with one of these newer ones yet. my experience is with the old OBD1 stuff on GM TPI/TBI stuff.

It doesn't seem like anyone does it this way is but... is it possible to just pull the AM29F800BB off the board and dump/flash it? that way I don't have to deal with the OBD2 tools. I mean obviously the Flash can be pulled off the board and read/write it but is is formatted the same on there as the dumps pull out of the obd2 port. I would assume its the same I just figured It was worth asking. I figure its all stored on the flash since the dumps are 1mb and its a 1mb flash memory.

from what I am reading it looks like you can use Tunerpro now for these PCMs just need the right XDF files for it. Googling 12589162 xfd comes up with nothing. am I searching the wrong thing?

BTW first post here on so first I wanted to say thank you in advance.

[antus]

Yes you can pull the chip and flash. Because its a 16 bit format you generally need to swap the a/b bytes before you flash. Look at 0x6000 area for the vin to see if the file you have needs to be swapped or not. If you have the chip in a programmer do a read, and if it looks swapped, swap it again, do your editing, then swap it back before you flash. If it doesnt look swapped your programmer probably handled it differently and you dont need to do this.

You can also use a usbbdnnt to flash it through the BDM port after you connect up a couple of wires, or you can do calibration flashes with pcmhammer on the P59, and at some stage you should be able to do full os flashes if you need to change os too.

BDM: viewtopic.php?f=42&t=6215&start=50#p96378
PCMHammer: viewtopic.php?f=42&t=6080

Generally speaking you'd use the service number to ID the hardware (not the hardware ID ironically) and the OSID (operating system ID) to match up an xdf. People can flash different OS in to compatible machines, so whats on the sticker isnt necessarily on the pcm. But you would generally look to find an OSID bin file that is compatible with your hardware and your vehicle and which you have an xdf for. Then your ready to go. Also the PCM your talking about is known as a P59.

[Fixed until broken]

Ah makes sense on the OSID. That turns up a lot more results.

I was planning on using my TL866II since it listed as a supported device. I do need to pick up the SOP 44 adapter but they seem readily available.

I like using my TL866II to prove a point that cheap tools work for hobbyist I do a lot of odometer correction with it while people are dropping $500 on stand alone tools for it. I know they have some pretty cheap adapters for PCM Hammer and LSdroid I've been following PeteS on Youtube. speaking of youtube I am on there under same username as here. Unfortunately I don't own anything to test this PCM in after mess with it other than my bench top tester I use for instrument clusters( its just one of these ECUs in a box with some pots to stimulate the Fuel, Trans Temp, Coolant and oil pressure). later I will get one of the 512kb units that go in my truck and play with it. The owner of they yard gave me this one for free so I wasn't going to ask for a different one since it was free.

I am going to order my adapter SOP 44 and 3 weeks down the road once it gets here from china I will report back. Hopefully it doesn't come with coronavirus.

Edit: I wrote TSOP 48 but meant SOP 44 IDK why I was thinking it was TSOP or 48 pin...

[DavidBraley]

In my notes, the hardware # 12589162 is a drive by wire P59:

2005:
Service # 12589463, OSID # 12592618

2006:
Service # 12602802, OSID # 12605114 & 12606807
Service # 12589463, OSID # 12587811

2007:
Service # 12602802, OSID # 12597120

[Fixed until broken]

David yeah mine is service 12589463.

Ordered the tool just waiting now. Thanks for the info guys I will probably play with one of the bins from GitHub while I wait for the tool. Its going to take longer than I hoped since the seller is on holiday for Chinese New Year.

[Fixed until broken]

In my notes, the hardware # 12589162 is a drive by wire P59:

2005:
Service # 12589463, OSID # 12592618

2006:
Service # 12602802, OSID # 12605114 & 12606807
Service # 12589463, OSID # 12587811

2007:
Service # 12602802, OSID # 12597120

Do you have XDF/Bins for any of those? My package from china is delayed with the corona virus. Its still being held in china. Id really like mess with the bins in tunerpro while I wait. Thank you!

[DavidBraley]

Do you have XDF/Bins for any of those? My package from china is delayed with the corona virus. Its still being held in china. Id really like mess with the bins in tunerpro while I wait. Thank you!

I do not, but you will likely find some bin files in the links below. XDF for your OSID? Someone else will have to answer that one.

2005: http://www.gearhead-efi.com/Fuel-Inject ... -Bin-Files

2006: http://www.gearhead-efi.com/Fuel-Inject ... -Bin-Files

2007: http://www.gearhead-efi.com/Fuel-Inject ... -Bin-Files

[Fixed until broken]

I got in the adapter last week I just got time to test it out. it seems to work good. Could someone look at my bin and see if it is a good dump? I ended up with another PCM I did it to. Service number 1258963 HDW number 12589162. Where is the OSID in the bin?

[antus]

Its a good read, but you need to run a swap AB over it to reverse the byte order. If you were to edit it you would then swap them back after and write the swapped image back to the flash. Look at $504 and you'll see in hex 00C025EA which is the OSID in hex, which in decimal makes it 12592618. The OS Segment starts at $500. Its 2 bytes checksum, 2 bytes module number, 4 bytes ID, and because its the operating system its the OSID. Other segments are the same, but we would refer to them as the calibration segment IDs.

[Fixed until broken]

Yes you can pull the chip and flash. Because its a 16 bit format you generally need to swap the a/b bytes before you flash. Look at 0x6000 area for the vin to see if the file you have needs to be swapped or not. If you have the chip in a programmer do a read, and if it looks swapped, swap it again, do your editing, then swap it back before you flash. If it doesnt look swapped your programmer probably handled it differently and you dont need to do this.

looks like the A/B bytes need to be swapped is there an easy way to do that?