P08 Support Information

[Gampy]

Hi all,

Looking for a valid P08 Seed/Key pair, any one have a set or two ??
Or where they are stored in a binary ...

Thanks
-Enjoy

[kur4o]

You can brute force the algo for 30 minutes, or give me an OS number or a VIN, and I will try to find the algo.

If that is the 4cylinder pcm, try algo $0D
a valid pair from a bin not sure which year it is,
seed 60 36 , key 59 42

[Gampy]

Thank you sir!

I would be interested in knowing the 30 minute brute force technique.

-Enjoy

[kur4o]

You can test each algo, in brute force style. It will be realtively fast. useful for modules that don`t have known algo and it is hard to guess.

[Gampy]

Thank you sir!

If anyone happens to know the DLC registers, for the two year groups that would be greatly appreciated.

Code: Select all

#define DLC_CONFIGURATION           (*(unsigned char *)0x????????)
#define DLC_INTERRUPTCONFIGURATION  (*(unsigned char *)0x????????)
#define DLC_TRANSMIT_COMMAND        (*(unsigned char *)0x????????)
#define DLC_TRANSMIT_FIFO           (*(unsigned char *)0x????????)
#define DLC_STATUS                  (*(unsigned char *)0x????????)
#define DLC_RECEIVE_FIFO            (*(unsigned char *)0x????????)

I believe pre 98.5,

COP1 is: 0xFFFFFA27
COP2 is: 0xFFFFC006

and 98.5 and up,

COP1 is: 0xFFFA27
COP2 is: 0x800806

Have been looking, unfortunately my disassembly skills suck at best, I am also looking at two different sources, I believe one is pre 98.5 the other is 98.5 up.

Thanks!

-Enjoy

[antus]

The pre 98.5 seems to have all the same registers as the P04. At least that's the bin I have on hand. With these earlier ones with fewer registers it's harder to see what's what from a disassembly but the same couple of DLC registers come up in the as does the COP, so I think it's worth just setting the kernel build to use P04|P08 and start test. I havn't seen a post 98.5 bin yet. I expect my post 98.5 (service number 9356249, HDW 16268310) to arrive in about a week, then I'll be keen to test or develop.

[Gampy]

I am using the ones posted here: viewtopic.php?f=42&t=8138&p=120755#p120754

Maybe outta move them posts here or something ...

-Enjoy

[zack4200]

I tried reading a p08 from my 98 s10 (build date is 08/98, so I'm not sure if it's considered pre or post 98.5) with the test build Gampy linked to here but it didn't work. The first thing I noticed is that it identifies the pcm as a p01/p59. it also failed to unlock the pcm. I've included my logs

Code: Select all

[10:42:52:535]  PCM Hammer (4/18/2023, 2:54 AM)
[10:42:52:536]  Friday, April 21 2023 @10:42:52:53
[10:42:53:401]  Device Found: OBDX Pro VT
[10:42:53:592]  Voltage is: 13.55V
[10:42:53:598]  Device Successfully Initialized and Ready
[10:42:58:073]  VIN: 1GCCS1942W8234430
[10:42:58:102]  OS ID: 9364970
[10:42:58:111]  Hardware Type: P01_P59
[10:42:58:133]  Calibration ID: 9365003
[10:42:58:156]  Hardware ID: 16204850
[10:42:58:214]  Serial Number: ATNQLW8231
[10:43:03:303]  BCC query failed: Error
[10:43:08:366]  MEC query failed: Error
[10:44:25:053]  Will save to D:\Car Stuff\pcmhammer test bins\98 s10 2.2 LN2.bin
[10:44:35:092]  Querying operating system of current PCM.
[10:44:40:164]  Operating system query failed, will retry: Error
[10:44:45:245]  Operating system query failed: Error
[10:44:45:248]  Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[10:45:11:473]  Using OsID: 9364970
[10:45:13:222]  Unlock was not successful.
[10:46:57:613]  Halting kernel.
[10:46:57:630]  Clearing trouble codes.

[Gampy]

zack4200,

Thank you, unfortunately the P08 is not yet supported, the first reads were done just yesterday, so we are about to add read only support after we figure out one minor issue, in fact I'm working on it now (when I'm not replying here), hopefully within the next day or so we should have a test build available.

I will add that OsID though ...

Would you like to try a custom test build now, I'm happy to build you one ??

Thank you!
-Enjoy

[zack4200]

ah okay, I saw a few p08 related commits on github and obviously this thread so I thought maybe stuff had been added already.

If you feel like building a custom test build for me I'll definitely try it out! otherwise I'm fine with waiting for the one issue to be sorted out.