pcmhacking.net

Edit 09/19/22: Cleaned up some spelling errors and added a few parameters.

Edit 08/15/22: Added a few more parameters.

Edit 07/13/22: Just a couple of little spelling and folder fixes.

I decided to kill some time and work on an XDF for the 2003 P59 12579405 OS. I built it based on the 7603 XDF so it should be pretty familiar. Of course please feel free to critique and offer suggestions on how to improve it.

You are aware this is a Intel only OS ??

IMO not one that should be done, people are going to be writing this OS to AMD units causing all sorts of headaches!

However it's kinda late now ... The cats out of the bag!

Should I pull it down? Or maybe add a warning?

It might be worth adding intel pcm only to the filename and/or title in the xdf, or else visible in there. If you flash an intel OS to an AMD pcm it wont brick it, but it wont be able to do things like save vin changes. you can flash it back to an amd os easily enough.

File and thread name edited to reflect Intel PCM only.

Phoenix wrote:File and thread name edited to reflect Intel PCM only.

So how do you know if the PCM has a Intel chip in it?
Is it the hardware number?

This OS is used on 2003 P59's with the following Hardware Numbers (not a comprehensive list),

12570558
12575502
12580786

They use the Intel 28F800B, 1mb flash chip.

Also you can use something like PcmHammer and do a 'Verify Entire PCM', or any other Read/Write operations that load the Kernel and it'll be in the log.

Not to bring up a dead thread but this OS I have flashed to AMD PCMs and worked just fine. My father-in-laws El Camino has this OS on it and it's an AMD pcm and drives perfect. So what's the issue with it? Currently reading a 405 OS that is on an AMD chip. Reading just fine. Anyone want to pipe in what the issue is?

If you look back a few posts, you'll see that Antus explains it (can't change vin etc)

That is the thing, I did change the vin. That is why I was a bit confused.
I wanted to double check the one I just did and it's a service# 12586242 and hdw# of 12583660. Opened it up as well and it was an AMD chip (AM29F800BB).

I guess when other have issues when does it arise? meaning lets say does it happen/brick when you go to write it after making a vin change?