PCM Hammer P04 Support Project

Post by **Gampy** » Thu Mar 16, 2023 4:18 am

Awe, I must have my notes fouled up, that version was supposedly used elsewhere.
Not a big deal ... However, you really should delete it and use a release version.

Properties are the 'Read Properties' button on PcmHammer's main tab.

So you can read a P04 and get the bin off it ??

-Enjoy

Cincinnatus · Post by **Cincinnatus** » Thu Mar 16, 2023 4:22 am

I am using the newest version. That attempt was 2 years ago (date is at start of log). I'm just here as a willing beta tester with a nano.

Post by **Gampy** » Thu Mar 16, 2023 4:35 am

Please don't misunderstand, not pissed off or anything like that ... Just clarifying for accuracy.
You've done nothing wrong!

PCM Hammer - TEST BUILD 018-824-9.1 (8/5/2021, 3:52 AM)

The date stamp is the date that version was built, not when the log was created!
That date stamp also signifies it's not an official release.

New versions of PcmHammer now have the log date as well.

-Enjoy

Cincinnatus · Post by **Cincinnatus** » Thu Mar 16, 2023 5:14 am

Got it. I pulled that log from here

viewtopic.php?f=42&t=7515

darkman5001 · Post by **darkman5001** » Thu Mar 16, 2023 7:57 am

Cincinnatus, you have a PM. Unzip my version into its own directory and run. Select the device and also select 4x High Speed. Read the properties first then do a full read. Once complete send both the debug and user log as well as the bin that was saved.

Post by **antus** » Thu Mar 16, 2023 8:02 am

"most ScanTool (STN) VCI's will do at least 2048 bytes"

This is unfortunately not true any more. Scantool keep changing their products internally and if a product isnt tested and specifically added to pcmhammer it'll fall back to 512bytes as the most compatible setting. People have not been sending us updates with the new IDs, and personally I got a bit sick of updating the code for scantool. Most new scantools will now only run at 512byte packets and wont work for this. People who know what they're doing can send us details or better a pull request for pcmhammer and it can be updated, but really since scantool are selling so many interfaces for use with pcmhammer itd be better if they were sending us pull requests to update the app as they keep changing their lineup.

Regarding P04 changes, the loader in 68k is the main thing. PCMHammer has had most of the required flags added already, we might need one more to flag split kernel and It wont be much of a code change to use the loader. Once it can load larger kernels I think that's the biggest hurdle overcome, still more kernel work to go, though, but if we're lucky the existing kernel code might mostly work. I agree with gampy a pure asm kernel would be ideal.

Cincinnatus · Post by **Cincinnatus** » Thu Mar 16, 2023 12:20 pm

here is the failed attempt. i noticed it's a different OS than my previous attempt. I'll try to find the other pcm and try it too.

[07:24:38:925] PCM Hammer (3/15/2023, 5:46 PM)
[07:24:38:925] Wednesday, March 15 2023 @07:24:38:92
[07:24:38:940] Initializing J2534 Device
[07:24:38:972] Loaded DLL
[07:24:43:721] Connected to the device.
[07:24:43:752] Battery Voltage is: 0.957
[07:24:45:065] Protocol Set
[07:24:45:112] Device initialization complete.
[07:25:11:645] TX: 6C 10 F0 3C 01
[07:25:11:723] RX: 6C F0 10 7C 01 00 31 47 34 48 50
[07:25:11:723] TX: 6C 10 F0 3C 02
[07:25:11:785] RX: 6C F0 10 7C 02 35 32 4B 33 58 48
[07:25:11:785] TX: 6C 10 F0 3C 03
[07:25:11:848] RX: 6C F0 10 7C 03 34 30 32 39 30 35
[07:25:11:848] VIN: 1G4HP52K3XH402905
[07:25:11:863] TX: 6C 10 F0 3C 0A
[07:25:11:926] RX: 6C F0 10 7C 0A 00 BA 60 6A
[07:25:11:926] OS ID: 12214378
[07:25:11:926] Hardware Type: P01_P59
[07:25:11:942] TX: 6C 10 F0 3C 08
[07:25:11:988] RX: 6C F0 10 7C 08 00 BA 60 66
[07:25:11:988] Calibration ID: 12214374
[07:25:11:988] TX: 6C 10 F0 3C 04
[07:25:12:051] RX: 6C F0 10 7C 04 00 8E C8 80
[07:25:12:051] Hardware ID: 9357440
[07:25:12:051] TX: 6C 10 F0 3C 05
[07:25:12:098] RX: 6C F0 10 7C 05 31 44 34 30
[07:25:12:098] TX: 6C 10 F0 3C 06
[07:25:12:160] RX: 6C F0 10 7C 06 54 52 38 32
[07:25:12:160] TX: 6C 10 F0 3C 07
[07:25:12:223] RX: 6C F0 10 7C 07 31 38 FC EE
[07:25:12:238] Serial Number: 1D40TR8218
[07:25:12:254] TX: 6C 10 F0 3C 14
[07:25:12:317] RX: 6C F0 10 7F 3C 14 31
[07:25:12:317] Received an unexpected response. Attempt #1, status UnexpectedResponse.
[07:25:14:332] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:14:332] Sending 'test device present' notification.
[07:25:14:332] TX: 8C FE F0 3F
[07:25:16:364] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:16:364] Sending 'test device present' notification.
[07:25:16:364] TX: 8C FE F0 3F
[07:25:18:395] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:18:395] Sending 'test device present' notification.
[07:25:18:395] TX: 8C FE F0 3F
[07:25:20:427] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:20:427] Sending 'test device present' notification.
[07:25:20:427] TX: 8C FE F0 3F
[07:25:22:458] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:22:458] Receive timed out. Attempt #6, Timeout #5.
[07:25:22:458] TX: 6C 10 F0 3C 14
[07:25:22:505] RX: 6C F0 10 7F 3C 14 31
[07:25:22:505] Received an unexpected response. Attempt #1, status UnexpectedResponse.
[07:25:24:514] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:24:514] Sending 'test device present' notification.
[07:25:24:514] TX: 8C FE F0 3F
[07:25:26:529] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:26:529] Sending 'test device present' notification.
[07:25:26:529] TX: 8C FE F0 3F
[07:25:28:561] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:28:561] Sending 'test device present' notification.
[07:25:28:561] TX: 8C FE F0 3F
[07:25:30:592] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:30:592] Sending 'test device present' notification.
[07:25:30:592] TX: 8C FE F0 3F
[07:25:32:608] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:25:32:608] Receive timed out. Attempt #6, Timeout #5.
[07:25:32:608] BCC query failed: Error
[07:25:32:608] TX: 6C 10 F0 3C A0
[07:25:32:670] RX: 6C F0 10 7C A0 00
[07:25:32:670] MEC: 0
[07:26:28:431] Will save to C:\Users\Cincinnatus\Desktop\bin files\p04 test.bin
[07:26:34:188] Querying operating system of current PCM.
[07:26:34:219] TX: 6C 10 F0 3C 0A
[07:26:34:313] RX: 6C F0 10 7C 0A 00 BA 60 6A
[07:26:34:313] OSID: 12214378
[07:26:34:329] Suppressing VPW chatter.
[07:26:34:344] TX: 6C FE F0 28 00
[07:26:34:375] Sending 'test device present' notification.
[07:26:34:375] TX: 8C FE F0 3F
[07:26:34:407] RX: 6C F0 10 68 00
[07:26:34:422] Ignoring chatter: 6C F0 10 68 00
[07:26:34:422] Sending seed request.
[07:26:34:438] TX: 6C 10 F0 27 01
[07:26:34:500] RX: 6C F0 10 67 01 2E 48
[07:26:34:500] Parsing seed value.
[07:26:34:532] Sending unlock request (2E48, 4B1F)
[07:26:34:532] TX: 6C 10 F0 27 02 4B 1F
[07:26:34:610] RX: 6C F0 10 67 02 35
[07:26:34:610] The PCM didn't accept the unlock key value
[07:26:36:634] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:26:36:634] No response to unlock request. Attempt #2
[07:26:38:649] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[07:26:38:649] No response to unlock request. Attempt #3
[07:26:39:524] RX: 6C F0 10 60
[07:26:39:524] Unlock response truncated, expected 6 bytes, got 4 bytes.
[07:26:39:540] Unable to process unlock response.
[07:26:39:540] Unlock was not successful.

Cincinnatus · Post by **Cincinnatus** » Thu Mar 16, 2023 1:20 pm

Success!

p04 test2.bin: (512 KiB) Downloaded 45 times

[11:10:30:306] PCM Hammer (3/15/2023, 11:00 PM)
[11:10:30:321] Wednesday, March 15 2023 @11:10:30:32
[11:10:30:337] Initializing J2534 Device
[11:10:30:399] Loaded DLL
[11:10:35:509] Connected to the device.
[11:10:35:556] Battery Voltage is: 12.363
[11:10:44:338] VIN: 1G4HP52K3XH402905
[11:10:44:463] OS ID: 12214378
[11:10:44:463] Hardware Type: P04_Intel
[11:10:44:478] **********************************************
[11:10:44:478] WARNING: P04_Intel Read is EXPERIMENTAL ONLY.
[11:10:44:494] It may or may not read your P04_Intel correctly. The read will be VERY SLOW.
[11:10:44:494] If you have the skills please help us improve this code and send us a pull request on github.
[11:10:44:509] P04_Intel Write is not yet under development, please do not ask when it is ready. P04_Intel read must work well first.
[11:10:44:509] **********************************************
[11:10:44:588] Calibration ID: 12214374
[11:10:44:666] Hardware ID: 9357440
[11:10:44:838] Serial Number: 1D40TR8218
[11:10:44:916] MEC: 0
[11:11:21:183] Will save to C:\Users\Cincinnatus\Documents\p04 test2.bin
[11:11:27:793] Querying operating system of current PCM.
[11:11:27:887] OSID: 12214378
[11:11:27:887] WARNING: P04_Intel Read is EXPERIMENTAL ONLY.
[11:11:27:903] It may or may not read your P04_Intel correctly. The read will be VERY SLOW.
[11:11:30:856] Unlock succeeded.
[11:11:30:887] Attempting switch to VPW 4x
[11:11:30:950] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[11:11:35:903] Kernel upload 100% complete.
[11:11:35:919] kernel uploaded to PCM succesfully. Requesting data...
[11:14:36:132] Read complete.
[11:14:36:148] Read-request messages had to be re-sent once.
[11:14:36:148] We're not sure how much retrying is normal for a read operation on a 512kb PCM.
[11:14:36:163] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[11:14:36:445] Clearing trouble codes.
[11:14:38:179] Clearing trouble codes.
[11:14:39:304] Elapsed time 00:03:08.4482016
[11:14:39:304] Saving contents to C:\Users\Cincinnatus\Documents\p04 test2.bin

Cincinnatus · Post by **Cincinnatus** » Thu Mar 16, 2023 1:27 pm

debug log

test2 debug.txt: (1.59 MiB) Downloaded 48 times

darkman5001 · Post by **darkman5001** » Thu Mar 16, 2023 1:29 pm

Awesome. Another success. About how long did that read take?

PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project

Re: PCM Hammer P04 Support Project