pcmhacking.net

Where is the OsID in the P04 binary ??

Bad thing about having lots of notes is finding the one you want ... I can't find it!

-Enjoy

There is no 'the' p04 binary. PeteS mentioned this. We're going to need a lookup list based on... OSID? Oh crap.... Best to use the data API and let the OS deal with it on the PCM, and/or look at universal patcher definitions and use that method.

Gampy wrote:Where is the OsID in the P04 binary ??

Bad thing about having lots of notes is finding the one you want ... I can't find it!

-Enjoy

In my '03 grand prix file, OS id is at 0007FFFA-D and is Hex to Decimal.
Mine is 00BFF535 and Decimal is 12580149
Here is the .bin file

Antus,

Are you saying the OsID is not in a uniform location across different OsID's ??

-Enjoy

It was in the same location in a .bin you posted...2005 buick century, I haven't looked at any others.

Yea punched myself in the face a couple times on that one ... I could have looked in mine and I didn't even think about it until you posted and made me think of it!

Duh! What a dumb ass I am ...

-Enjoy

Hiya Gampy,
No worries, I didn't think about looking for yours till your reply either. I went on the hunt and found one you posted, checked it and there it was

Gampy wrote:Antus,

Are you saying the OsID is not in a uniform location across different OsID's ??

-Enjoy

Im a little unsure. I have been told they are, but that might be between different v6 pcms. I also dont know what defines a p04 compared to similar v6 pcms. I would say we need to be careful until we know for sure between different hardware IDs. Would love for more information on the subject.

V6 Os is stored at 2 places and both can vary per bin. The easier one is almost always at the end of bin -6 bytes but sometimes it is -8 bytes.

The other place is near checksum location and it is also needed for checksum calculation.
Checksum is also stored at different address.
Either a lookup table for both of this is needed, or some logic from universal patcher can be implemented.
There are some search string that identify both of these locations flawless. There is also another string that can identify end of OS part, and can be used for custom crc32 to identify cross compatible OS numbers.

The structure is like this

start of bin- end of OS part. It doesn`t contain any identifiers as part number
start 0f calibration - end of bin. It does have cheksum p/n1 and p/n2

First part can be identical between different bins that have different p/ns in calibration part.

I will try to get some example soon.

Thank You,
I don't have my 2003 grand prix anymore. I think I have 1 blue/clear pcm somewhere to play with.