PCM Hammer Release 021

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
User avatar
Posts: 671
Joined: Fri Feb 02, 2018 3:13 pm

PCM Hammer Release 021

Postby NSFW » Sun May 15, 2022 5:01 am

The big news for this release is that PCM Hammer now supports reading and writing P10 and P12 PCMs.

Kudos to Gampy and Antus and everyone who helped with investigating, troubleshooting, and testing.

Since P10 and P12 support is so new, you should consider yourself a beta tester if you're working with those PCMs. There's a difference between "it has worked" and "it always works," and we need your help to find out exactly where we're at. There may be some issues to address before P10 and P12 PCMs can be flashed as reliably as P01 and P59 PCMs.

Please post in this thread about what works for you, and what doesn't.

Also note that the community will need volunteers to:
* contribute bin files for P10 and P12 PCMs
* document variations of P10 and P12 PCMs
* document which makes / models / years used which PCMs and which variants
* figure out which operating systems can support the widest variety of vehicles
* create XDFs for the highest-value operating systems

And we'll need one or more volunteers to create and maintain a collection of P10 and P12 bin files and XDF files.

Documentation for PCM Hammer can be found here:
https://github.com/LegacyNsfw/PcmHacks/wiki

Version 021.2 adds support for P12 OS ID 12601904.
Attachments
PcmHammer021.2.zip
(2.13 MiB) Downloaded 226 times
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!

Site Admin
User avatar
Posts: 7248
Joined: Sat Feb 28, 2009 8:34 pm

Re: PCM Hammer Release 021

Postby antus » Sun May 15, 2022 9:40 am

Please note that the P12 support does includes support for the 2Mb P12b PCMs.

For P10/P12/P12b we are looking for reports of success or failure from in vehicle testing when changing the OS to another type. PCM Hammer updates the main flash chip but it does not update the small amount of flash in the slave CPU. We think there is a good chance this data is fine shared between different OSIDs but we need to confirm this. As always make sure you save a bin as the first thing you do, and test proper vehicle operation in a safe environment. If you have changed the OSID and tested in a car let us know what OSID you changed from and to, and the results. Thanks!
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Posts: 137
Joined: Sat Dec 18, 2021 8:15 am
Location: New Jersey, USA

Re: PCM Hammer Release 021

Postby darkman5001 » Sun May 15, 2022 11:12 pm

I can't remember where we were with this, but only very minor issue I see is with the P10. When selecting "Read Properties" there is about a 20 second delay and then it comes back with "Hardware ID Query Failed". Again very minor issue, as all other functions work including writing.
Attachments
PcmHammer_userLog_20220515@090519.txt
(592 Bytes) Downloaded 53 times
PcmHammer_debugLog_20220515@090535.txt
(3.33 KiB) Downloaded 52 times

Posts: 5
Joined: Sun May 15, 2022 7:10 pm

Re: PCM Hammer Release 021

Postby hashtagfacts » Sun May 15, 2022 11:43 pm

I'm new to the whole scene, thank you for having me! however it reads my P12 PCM fine, the only thing is, there's no such thing as an XDF for me. I have a 2004 GMC Canyon 3.5L L52 and I would like some assistance figuring it out as there is literally nothing anywhere about it online. This is not my only vehicle this is just something that I'm going to play with, for learning purposes of course.

Posts: 540
Joined: Sun Apr 10, 2016 9:20 pm

Re: PCM Hammer Release 021

Postby kur4o » Mon May 16, 2022 4:11 am

hashtagfacts wrote:I'm new to the whole scene, thank you for having me! however it reads my P12 PCM fine, the only thing is, there's no such thing as an XDF for me. I have a 2004 GMC Canyon 3.5L L52 and I would like some assistance figuring it out as there is literally nothing anywhere about it online. This is not my only vehicle this is just something that I'm going to play with, for learning purposes of course.


You can definitely help by posting stock files. Any and all stock files are needed and welcomed.

Posts: 11
Joined: Sun Jul 03, 2016 5:11 pm

Re: PCM Hammer Release 021

Postby Asylumwarp » Mon May 16, 2022 7:12 am

here is a read attempt from the p12

[01:31:44:419] PCM Hammer 021
[01:31:44:424] Sunday, May 15 2022 @01:31:44:42
[01:31:44:428] Initializing AVT (838/842/852) on COM3
[01:31:44:464] Sending 'reset' message.
[01:31:44:468] AVT 852 Reset OK
[01:31:44:469] Looking for Firmware message
[01:31:44:470] AVT Firmware 2.6
[01:31:44:486] Set VPW Mode
[01:31:44:489] Disable AVT Acks
[01:31:44:497] AVT Acks disabled
[01:31:44:497] Configure AVT filter
[01:31:44:499] AVT filter configured
[01:31:44:541] Loaded credits.html from network.
[01:31:44:541] Loaded start.txt from network.
[01:31:44:541] Loaded help.html from network.
[01:31:44:542] Thanks for using PCM Hammer.
[01:31:57:168] Will save to C:\Users\Family\Dropbox\P12\test.bin
[01:31:58:670] Querying operating system of current PCM.
[01:31:58:741] TX: 6C 10 F0 3C 0A
[01:31:58:776] RX: 6C F0 10 7C 0A 00 C0 4A 30 41 41
[01:31:58:780] OSID: 12601904
[01:31:58:786] Suppressing VPW chatter.
[01:31:58:789] TX: 6C FE F0 28 00
[01:31:58:794] Sending 'test device present' notification.
[01:31:58:798] TX: 8C FE F0 3F
[01:31:58:822] RX: 6C F0 10 68 00
[01:31:58:825] Ignoring chatter: 6C F0 10 68 00
[01:31:58:890] Sending seed request.
[01:31:58:893] TX: 6C 10 F0 27 01
[01:31:58:922] RX: 6C F0 10 67 01 05 50
[01:31:58:926] Parsing seed value.
[01:31:58:934] Sending unlock request (0550, 4348)
[01:31:58:937] TX: 6C 10 F0 27 02 43 48
[01:31:58:972] RX: 6C F0 10 67 02 36
[01:31:58:978] The PCM did not accept the key - too many attempts
[01:31:59:985] Waited 2seconds.. no data present
[01:31:59:989] AVT: no message waiting.
[01:31:59:996] No response to unlock request. Attempt #2
[01:32:01:000] Waited 2seconds.. no data present
[01:32:01:003] AVT: no message waiting.
[01:32:01:006] No response to unlock request. Attempt #3
[01:32:02:008] Waited 2seconds.. no data present
[01:32:02:012] AVT: no message waiting.
[01:32:02:015] No response to unlock request. Attempt #4
[01:32:02:018] Unable to process unlock response.
[01:32:02:021] Unlock was not successful.

p12 using avt
using VPW line

Posts: 540
Joined: Sun Apr 10, 2016 9:20 pm

Re: PCM Hammer Release 021

Postby kur4o » Mon May 16, 2022 7:54 am

This OS is from saturn, so it is possible the unlock algo differs.

Can you run this script with this program. It will test if pcm uses standard algo.

https://pcmhacking.net/forums/viewtopic.php?f=42&t=7753

post results here.
Attachments
$10_brute_unlock_var_algo.txt
(417 Bytes) Downloaded 52 times

Posts: 11
Joined: Sun Jul 03, 2016 5:11 pm

Re: PCM Hammer Release 021

Postby Asylumwarp » Mon May 16, 2022 7:57 am

antus wrote:Please note that the P12 support does includes support for the 2Mb P12b PCMs.

For P10/P12/P12b we are looking for reports of success or failure from in vehicle testing when changing the OS to another type. PCM Hammer updates the main flash chip but it does not update the small amount of flash in the slave CPU. We think there is a good chance this data is fine shared between different OSIDs but we need to confirm this. As always make sure you save a bin as the first thing you do, and test proper vehicle operation in a safe environment. If you have changed the OSID and tested in a car let us know what OSID you changed from and to, and the results. Thanks!



Antus, some OS's share the same slave however changing from year to year becomes a problem on the slave. There is a link between the main flash OS and the slave OS and when they mismatch it creates a brick. We got to figure out how to atleast identify the slave OS for matching the correct main flash before write attempt or it will create a mess of broken pcms.

Posts: 540
Joined: Sun Apr 10, 2016 9:20 pm

Re: PCM Hammer Release 021

Postby kur4o » Mon May 16, 2022 8:15 am

With sps you can update main OS + slave. If there is different service number pcms, that can be used as identifier. Of course some test can be done with sps updating 2003 pcm with 2007 OS and slave, to test hardware compatibility.
Is it possible to unbrick by loading correct slave after main OS is updated.

Posts: 11
Joined: Sun Jul 03, 2016 5:11 pm

Re: PCM Hammer Release 021

Postby Asylumwarp » Mon May 16, 2022 8:25 am

kur4o wrote:This OS is from saturn, so it is possible the unlock algo differs.

Can you run this script with this program. It will test if pcm uses standard algo.

https://pcmhacking.net/forums/viewtopic.php?f=42&t=7753

post results here.



Here are the results
p12_brute_algo_results.txt
(20.04 KiB) Downloaded 55 times

Next

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: Scott68B and 1 guest