PCM Hammer P12 development

They go by many names, P01, P10, P12, P59, E38, VPW, '0411 etc.
User avatar
antus
Site Admin
Posts: 10111
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: PCM Hammer P12 development

Post by antus »

The black box issues with the obdlink were recently fixed. The latest development version should be able to recover them. Need a github account then download from https://github.com/PcmHammer/PcmHammer/ ... 9077872207

What will definitely work is moving settings across you need and updating the calibration on the new ones keeping the OS that is has. Worth the effort? Not sure, up to you.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
SmichaelR22
Posts: 12
Joined: Mon Feb 16, 2026 11:14 pm
cars: LS chassis swaps of 47-54 chevy trucks, 50s international trucks, jeeps, rock crawlers, too many to list.

Re: PCM Hammer P12 development

Post by SmichaelR22 »

grabbed another cobalt 2.0 LSJ 2005 stock read, and then removed vats and any evap DTCs, for reference.
both files attached.
successful write.


2005_cobalt_ss 2_0_SC_stock read_P12_12601774_.bin
[11:27:24.810] VIN: 1G1AP14P157631831
[11:27:24.906] OSID: 12601774
[11:27:24.934] Description: P12 1Mb (Atlas I4/I5/I6)
[11:27:25.000] Calibration ID: 0
[11:27:25.212] Serial Number: 5105KG05SB
[11:27:25.278] Broad Cast Code: YLJX
You do not have the required permissions to view the files attached to this post.
2.2L ebay turbo ecotec transaxle rear steer rock crawler on 42 reds
User avatar
SmichaelR22
Posts: 12
Joined: Mon Feb 16, 2026 11:14 pm
cars: LS chassis swaps of 47-54 chevy trucks, 50s international trucks, jeeps, rock crawlers, too many to list.

Re: PCM Hammer P12 development

Post by SmichaelR22 »

antus wrote: Thu Oct 22, 2026 12:54 am read one of the p12 or p12b you picked up from the junk yard and save it away so you know which one it is and can put it back to stock if you need to. Then try and write your bin to it. This will cost you nothing and you'll see if you can get that far. Then you can put it in your car and see if electronic throttle works. Even if it doesnt you can use it as a test pcm for the flash process and once you've written it successfully with changes a couple of times and are confident you can do it again you can write the calibration back to your original PCM.

got around to this before i cut the car up and took to scrap today (2007 cobalt LNF). kept the cars PCM as is (read file and saved.) 2nd test then tried in car a yard PCM P12 1mb from a colorado loaded with the first cobalt 2.0 SC tune / DTCs removed, VATS removed. Car starts and runs, but shows "reduced power" on dash, and only revs to 3k rpm. good flash test, but sounds like i did not get lucky with a matching slave OSID . good test though. finally the 3rd PCM from another friends cobalt 2.0 SC read, modified its bin without vats, flashed, and it works great.
2.2L ebay turbo ecotec transaxle rear steer rock crawler on 42 reds
LSxHunter
Posts: 7
Joined: Sun Sep 20, 2026 7:32 pm
cars: 2006 Hummer H3, 2016 Escalade, 1991 Z28

Re: PCM Hammer P12 development

Post by LSxHunter »

For anyone using the P12 TableSeek files: those were built from v3.13 of the 12627884 XDF. v3.19 is out now with 2800 items (v3.13 had about 1900), so there's a lot more to pattern match if anyone wants to regenerate them. Same link: https://lsxhunter.com/p12/

@SmichaelR22: that XDF is for OS 12627884 only. The addresses differ on other OSIDs, which is what the TableSeek files are for.

On the slave question: from the main CPU side on 12627884, the main CPU talks to the slave over QSPI, and the slave reads posted here (spyder09's) are a 68332 image that loads at 0x40000 with its cal at 0x50100. I haven't found anything on the main side that reads the slave back, so that matches what antus said. Happy to share addresses if it helps anyone.

Also thanks to everyone who posted reads in here. The extra P12 bins have been a big help for cross-checking.
LSxHunter
Posts: 7
Joined: Sun Sep 20, 2026 7:32 pm
cars: 2006 Hummer H3, 2016 Escalade, 1991 Z28

Re: PCM Hammer P12 development

Post by LSxHunter »

Quick update on the P12 work. The H3 XDF (OS 12627884) is at v3.21 with 3,947 items, about 88 % of the calibration.

We’ve started carrying it to other P12 operating systems. An item goes into another OS’s XDF only when the code that reads it is the same as on the H3 (or proven to behave the same in an emulator), its table header matches, and its values check out. Anything we can’t prove there is left out. These are “located and checked in that OS’s code, not confirmed on a vehicle”, so edit in small steps and log.

Current catalog:

2006 Colorado / Canyon 3.5 L52 (12606375): about 84 %
Colorado / Canyon 2.8 LK5 (12627883): about 83 %
2006 TrailBlazer / Envoy 4.2 LL8 (12627882, 12606400): about 75 %
2005 to 2007 Cobalt SS / Ion Red Line LSJ and 2006 Cobalt (12601774, 12601904, 12597978, 12598275, 12605261, 12610624): about 49 to 64 %
older Canyon 3.5 OS (12589586): about 47 %

The Ecotec ones are lower because that engine shares less code with the H3; we’re tracing their own tables next. Every XDF loads and exports identically in TunerPro 5 and 6. None of them defines a checksum, so correct the P12 segment checksums before you flash.

Downloads: lsxhunter.com/p12/

If you have a P12 with an OS that isn’t listed, a stock (unmodified) read with the year, model, engine and transmission helps a lot. Reads are used for mapping only and never shared. Thanks to everyone who has posted reads and tools in these threads.