PCM Hammer P01 and P59 flash tool v015

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

Take the following with a grain of salt ... I'm pretty new to these GM PCMs.

I may very well be mistaken, however It looks to me like that PCM has had OS 12225074 improperly written to it ... The OSID was not changed!
You might try a XDF for OSID 12225074.

You may just need to change the OSID to 12225074 to clear it all up!

LIKE I SAID! I am new to these GM PCMs, allow someone else to confirm!

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
brandonwh64
Posts: 26
Joined: Mon Dec 31, 2018 9:17 pm
cars: building a 1965 F100 with a 5.3L LS

Re: PCM Hammer - new ls1 flash tool

Post by brandonwh64 »

Gampy wrote:Take the following with a grain of salt ... I'm pretty new to these GM PCMs.

I may very well be mistaken, however It looks to me like that PCM has had OS 12225074 improperly written to it ... The OSID was not changed!
You might try a XDF for OSID 12225074.

You may just need to change the OSID to 12225074 to clear it all up!

LIKE I SAID! I am new to these GM PCMs, allow someone else to confirm!

-Enjoy
The 12225074 you are seeing in my post was when I tried to compare that BIN with one that I read off the ecu. I will edit this post with an attached copy of what PCM hammer read of my ECUs
Attachments
stock2.bin
2000 chevy 1500 LM7 ECU2
(512 KiB) Downloaded 289 times
stock.bin
2000 chevy 1500 LM7
(512 KiB) Downloaded 299 times
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

What appears to me ... Is a 'Read Full Contents' with PcmHammer was done creating stock2.bin.
Then PcmHammer was used to do a 'Quick Comparison' between the PCM and the stock2.bin ... it failed.
Then PcmHammer was used to do a 'Quick Comparison' between the PCM and the 2001 Holden Commodore Sedan Automatic LS1 5.7 Litre - 12225074.bin ... it passed except for OSID mismatch.

What that says to me is:
1. PcmHammer failed creating stock2.bin
2. That PCM has had OSID 12225074 improperly flashed ... The OSID was not changed.

Like I said ... Let someone else confirm my thoughts.

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
brandonwh64
Posts: 26
Joined: Mon Dec 31, 2018 9:17 pm
cars: building a 1965 F100 with a 5.3L LS

Re: PCM Hammer - new ls1 flash tool

Post by brandonwh64 »

Gampy wrote:What appears to me ... Is a 'Read Full Contents' with PcmHammer was done creating stock2.bin.
Then PcmHammer was used to do a 'Quick Comparison' between the PCM and the stock2.bin ... it failed.
Then PcmHammer was used to do a 'Quick Comparison' between the PCM and the 2001 Holden Commodore Sedan Automatic LS1 5.7 Litre - 12225074.bin ... it passed except for OSID mismatch.

What that says to me is:
1. PcmHammer failed creating stock2.bin
2. That PCM has had OSID 12225074 improperly flashed ... The OSID was not changed.

Like I said ... Let someone else confirm my thoughts.

-Enjoy
Rgr that! Thanks gampy! Will await NSFW and antus to weight in
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

brandonwh64 wrote:
brandonwh64 wrote:First ECU read on the 4896 ECUs!!........
Ok so after the read, I loaded up tuner pro with the 512.dll and xdf 12202088 and the values are not right on anything. The ECU is from a 2000 Truck with LM7 (4896). Is their a special XDF I need? The 0411 XDF is supposed to work from what I read.

Here is a copy of the read properties

[12:11:33:041] VIN: 1GCEK19T1XE113519
[12:11:33:138] OS ID: 9373372
[12:11:33:233] Calibration ID: 9374401
[12:11:33:330] Hardware ID: 16220610
[12:11:33:585] Serial Number: 1DG02B438286
[12:11:33:680] Broad Cast Code: CWAF
[12:11:33:776] MEC: 0

What I also found weird was when I used quick comparison on the .bin it read then compared it to a stock 2001 LS1 0411. The bin it just read off the 4896 ECU shows bad but the 0411 shows good...

[01:41:48:061] C:\Users\XXX\Dropbox\Car\Tuning\Mytunes\Default\stock2.bin
[01:41:48:072] Validating 512k file.
[01:41:48:076] Start End Result File Actual Content
[01:41:48:080] 0 7FFFD Good 4D00 4D00 Operating system
[01:41:48:083] 8002 13FFF BAD 9E60 74B3 Engine calibration
[01:41:48:087] 14002 16DFF BAD AAAA 1216 Engine diagnostics.
[01:41:48:091] 16E02 1BDFF BAD 0000 B329 Transmission calibration
[01:41:48:096] 1BE02 1C7FF BAD 0000 0E16 Transmission diagnostics
[01:41:48:100] 1C802 1E51F BAD 004D 658F Fuel system
[01:41:48:105] 1E522 1EE9F BAD 4AFC 1DFC System
[01:41:48:110] 1EEA2 1EF9F BAD 4AFC CCFC Speedometer
[01:41:48:115] This file is corrupt. It would render your PCM unusable.
Thanks for trying this out on your PCM! I suspect that the read actually worked, but in order to view the bin file in Tuner Pro you'll need an XDF for the 9373372 operating system (as Gampy said). The fact that it produced a bin file at all is very encouraging. And the checksum for the whole file is valid - that's not proof that it worked, but it's darn close.

That last line of output above is misleading - it really should say "This file cannot be used on a 12200411 PCM." The checksums might actually be valid, but the app is trying to validate a 896 bin file using the rules of the 411 PCM. That says more about the app than it says about the bin file. :)

Also, note that the last couple "checksums" are 4AFC... that value is used to fill some empty space at the end of the 411's calibration segment, so the fact that the app found that value in the last two checksums is also pretty encouraging.

Does anyone know what flash chip is in the 9354896? If it's an Intel chip we might be able to write it pretty easily.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
brandonwh64
Posts: 26
Joined: Mon Dec 31, 2018 9:17 pm
cars: building a 1965 F100 with a 5.3L LS

Re: PCM Hammer - new ls1 flash tool

Post by brandonwh64 »

NSFW wrote:
Thanks for trying this out on your PCM! I suspect that the read actually worked, but in order to view the bin file in Tuner Pro you'll need an XDF for the 9373372 operating system (as Gampy said). The fact that it produced a bin file at all is very encouraging. And the checksum for the whole file is valid - that's not proof that it worked, but it's darn close.

That last line of output above is misleading - it really should say "This file cannot be used on a 12200411 PCM." The checksums might actually be valid, but the app is trying to validate a 896 bin file using the rules of the 411 PCM. That says more about the app than it says about the bin file. :)

Also, note that the last couple "checksums" are 4AFC... that value is used to fill some empty space at the end of the 411's calibration segment, so the fact that the app found that value in the last two checksums is also pretty encouraging.

Does anyone know what flash chip is in the 9354896? If it's an Intel chip we might be able to write it pretty easily.
How hard is it to take apart? I can tomorrow at work and take pictures for you. If it DOES have an intel, how hard would it be to OS flash it to a 0411? I have google searched my butt off today and couldn't find ANY xdf's for the 9373372 OS even though most Fbodys and trucks used this ECU from 98-00.
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

I think it's just a couple of torx-head screws but I'm not certain. Flashing to a 411 OS seems unlikely to work. Apparently the 411 CPU is a little bit faster, so I'd be surprised if the 411 OS didn't take advantage of that extra speed somehow.

That said, someone certainly thinks it should work: https://www.norotors.com/index.php?topic=4566.0

But if the 411 and 896 use pretty much the same wiring, then it might be better to install a 411. Or the later PCM with the 1mb chip, as that's supposed to be just a couple wires away from being compatible with the 411. PCM Hammer doesn't support the 1MB PCMs yet but I'm pretty sure it will before long.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

[edit]
Y'all have no idea the words I wanna use right now!

Obviously some of you have caught my mistake ... My apologies.
[edit]
brandonwh64 wrote: [01:46:47:575] C:\Users\XXX\Dropbox\Car\Tuning\12225074\2001 Holden Commodore Sedan Automatic LS1 5.7 Litre - 12225074.bin
[01:46:47:581] Validating 512k file.
[01:46:47:588] Start End Result File Actual Content
[01:46:47:595] 0 7FFFD Good 0BA1 0BA1 Operating system
[01:46:47:601] 8002 13FFF Good 608F 608F Engine calibration
[01:46:47:608] 14002 16DFF Good DCC3 DCC3 Engine diagnostics.
[01:46:47:616] 16E02 1BDFF Good E2C2 E2C2 Transmission calibration
[01:46:47:623] 1BE02 1C7FF Good DDB5 DDB5 Transmission diagnostics
[01:46:47:630] 1C802 1E51F Good E029 E029 Fuel system
[01:46:47:638] 1E522 1EE9F Good E2CC E2CC System
[01:46:47:646] 1EEA2 1EF9F Good 4AAE 4AAE Speedometer
[01:46:47:653] Requesting operating system ID...
[01:46:47:780] Operating system IDs do not match.
[01:46:47:787] PCM operating system ID: 9373372
[01:46:47:793] File operating system ID: 12225074
[01:46:47:801] Flashing this file could render your PCM unusable.
Ok, curiosity has me, how did this happen then?

-Enjoy
Last edited by Gampy on Sat Feb 09, 2019 3:43 am, edited 1 time in total.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

We should make the output clearer....

Mostly that's just saying that the checksums inside the bin file are all correct - the app wasn't talking to the PCM yet.

The last few lines compare the OS ID in the file to the OS ID in the PCM.

The next few lines would be about uploading the kernel to the PCM, and the lines after that would compare the contents of the file to the contents of the PCM's memory.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
Gampy
Posts: 2331
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

Thanks for trying to lighten it ... I feel absolutely ...ing dumb!

On the clearer output, I usually try to put the 'OK' (or whatever) at the beginning or end so it's easy to pick out.
Like the compare is ... Then you smart folks can make the same mistake and make me feel better ... :mrgreen:
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
Post Reply