P08 Support Information

[antus]

Yeah since we are also looking at P08s the P04 sum code was detecting P08 bins as P04 and saying the valid P08 files were corrupt. So I added just the definition of P08 since we need it anyway and cleaned up the P04 checksums so they don't get tangled anymore. Gampy is on the P08 kernel, I plan to look at P08 file checksums. At some stage we'll get on to the write functionality in the asm kernel and that should get write open on several new PCMs. Cant give a time though, its when we get there. I just saw blackbox mentioned in another thread... and now that we are getting familiar with this whole family it might not be too much to put that on the list too. But we better not get too far ahead of ourselves.

[zack4200]

Gampy, I read my p08 with the build you PM'd me. BIN and logs attached

I read it in vehicle and ended up with the security light on and the truck not starting. kind of weird imo because this truck doesn't have a chipped key

anyway, disconnecting the battery for a minute or two fixed it. Is this normal with an in vehicle flash or did I mess something up somewhere?

[Gampy]

Wow, Sorry ... It sounds like the Kernel did not die and allow the OS to have control back, I'll have a look at the logs and see what they show.

The only 'write' thing it does is clear all codes when PCMHammer tells the Kernel to die, there is a requirement for that, don't remember why, however there is no way it can do permanent damage.

Looks like the same PCM I have, 98 S10 with OsID 9364970.

Right now we only have two OsID's for the P08, 9364970 and 12206029.

Thank you for testing and sharing.

-Enjoy

[Cincinnatus]

I've had some in vehicle reads cause problems. It seems the other modules lose communication with pcm and each other and set a bunch of codes. This wasn't with a p08, it was a p01. I don't remember ever having a no start, but I did have lots of lights on the cluster and dic.

[antus]

Thats because the bus is silenced and lot of errors trigger until the 'clear dtcs' step at the end. It happens on all of them and is normal for an in-vehicle read with any software.

[Gampy]

That should not create a battery disconnect situation ...

However, looking at the debug log I see the OBDX Pro VT has some ugly impatience ... It is supposed to be waiting longer then it is, it's set to 3000ms.
I do not know what it's max wait time is ... but it ain't long enough.

[04:10:32:936] Range File CRC PCM CRC Verdict Purpose
[04:10:32:945] XPro: 20 01 00 DE
[04:10:32:945] TX: 6C 10 F0 3D 02 02 00 00 06 00 00
[04:10:33:445] Timeout.. no data present A
[04:10:33:446] CRC read failed, re-trying 00060000 / 00020000
[04:10:33:946] Timeout.. no data present A
[04:10:33:947] CRC read failed, re-trying 00060000 / 00020000
[04:10:34:447] Timeout.. no data present A
[04:10:34:447] CRC read failed, re-trying 00060000 / 00020000
[04:10:34:947] Timeout.. no data present A
[04:10:34:947] CRC read failed, re-trying 00060000 / 00020000
[04:10:35:447] Timeout.. no data present A
[04:10:35:448] CRC read failed, re-trying 00060000 / 00020000
[04:10:35:855] Network RX: 6C F0 10 7D 02 02 00 00 06 00 00 E4 D3 83 D8
[04:10:35:855] 060000-07FFFF E4D383D8 E4D383D8 Same OperatingSystem

-Enjoy

[Cincinnatus]

Antus, the codes did not automatically clear at the end, and I had problems that required manually clearing the codes to restore vehicle back to original state. The codes were in modules other than the pcm. A battery disconnect would accomplish this too. This has occurred on multiple vehicles I have read in the past. I haven't tried with the more recent release. I just remove pcm if I'm going to read or write so I don't have to worry about problems.

[MudDuck514]

Wow, Sorry ... It sounds like the Kernel did not die and allow the OS to have control back, I'll have a look at the logs and see what they show.

The only 'write' thing it does is clear all codes when PCMHammer tells the Kernel to die, there is a requirement for that, don't remember why, however there is no way it can do permanent damage.

Looks like the same PCM I have, 98 S10 with OsID 9364970.

Right now we only have two OsID's for the P08, 9364970 and 12206029.

Thank you for testing and sharing.

-Enjoy

Hi all,

Gampy, here is the OSID from my 2001 Pontiac Grand AM with the 2.4l I4:
12208773
If you want to, add it to the mix.

Mike

p.s. once the weather clears up I'll drop the PCM out from under the dash to get the info off of it.

[Gampy]

Thank you Cincinnatus, we don't clear other modules, maybe we should look into that, having a no start after a flash doesn't look good and is bad manners IMO!
I think it's doable if we save a list (array) of modules that respond to the 4x shift, they are the ones that need to be reset I believe.

MudDuck514,
Thank you, I'll add it to the currently very short list, that's #3 ...
A test would be awesome!

I'll add it now, then post the latest P08 artifact (test build).

We do need P04, P08, E54 read testing ... There are recent updates (early this AM US time).
There are still some things to cover, we're getting there, slowly but surly.

Thanks y'all!

-Enjoy

[Gampy]

The latest artifact (test build).

Test em up please, P04, P08 and E54.

Read Entire PCM
Read Properties
Verify Entire PCM works on the P04, more work to be done for the P08 and E54, coming soon.

Post em up, debug logs and bins from PCMHammer reads.

Thanks y'all!
-Enjoy

PCMHacks_fb75d9516d83c0263d936c923540d01675cef98b.zip
CheckBuild #50
(2.18 MiB) Downloaded 5 times

Browse to where you saved it during download, drag n drop it where you want to unzip it on the fly, adjust destination directory name accordingly in the Select Destination Dialog, when done, browse to Destination directory, find PCMHammer.exe and double click on it.