Page 13 of 14

Re: P04 R&W Testing

Posted: Mon May 29, 2023 7:44 am
by MtnPwnd
Gampy wrote:I know for a fact it is a P08, the Hardware Number (16268310) is P08, it is not going to work as a P04 ... PERIOD!

Give me a few minutes and I'll PM you a test build that will no doubt read that PCM!

-Enjoy
I was able to read the PCM just fine. I haven't tried to write to it yet but attached you will find the results and debug log with my test here for the PCM I have here.

Re: P04 R&W Testing

Posted: Mon May 29, 2023 8:31 am
by Gampy
Awesome ... Glad it worked, remember the P08 is currently READ ONLY, you cannot write to it with PCM Hammer yet!

It's coming soon I hope!

-Enjoy

Re: P04 R&W Testing

Posted: Mon May 29, 2023 9:20 am
by antus
The OSID is one of these couple of 'unknown' where we were told they are P04 but its not. The other couple may be P08 as well? Its probably a good time to put P08 in there properly at which point it'll be cleaned up.

https://github.com/LegacyNsfw/PcmHacks/ ... o.cs#L2089

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 1:18 am
by ejs262
What do we need to gain P04 write support? anything a lesser member like myself can provide to aid in getting us there?

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 6:49 am
by Gampy
ATM, patience is required!

Kernel code is super super close ... I'm not going to be rushed though!
I do work on it as diligently as health allows.

Then we need to work on the Application side (PcmHammer itself), which really shouldn't be a big deal and should go really quick ...

What we really need is an ACCURATE list of just P04 Os ID's and just P08 Os ID's.
Might as well throw P05 in there as well, as I'm hoping P05 will join the supported list shortly after we are caught up with the current whirlwind of activities.

And not all combined together and shuffled without a PCM identifier ... We must know what PCM the OsID belongs to accurately!

-Enjoy

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 6:57 am
by ejs262
Gampy wrote:ATM, patience is required!

Kernel code is super super close ... I'm not going to be rushed though!
I do work on it as diligently as health allows.

Then we need to work on the Application side (PcmHammer itself), which really shouldn't be a big deal and should go really quick ...

What we really need is an ACCURATE list of just P04 Os ID's and just P08 Os ID's.
Might as well throw P05 in there as well, as I'm hoping P05 will join the supported list shortly after we are caught up with the current whirlwind of activities.

And not all combined together and shuffled without a PCM identifier ... We must know what PCM the OsID belongs to accurately!

-Enjoy
10-4, I'll wait patiently then! if there's anything I might be able to do, I'm more than happy to do so!

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 7:13 am
by Gatecrasher
Gampy wrote:
What we really need is an ACCURATE list of just P04 Os ID's and just P08 Os ID's.
Might as well throw P05 in there as well, as I'm hoping P05 will join the supported list shortly after we are caught up with the current whirlwind of activities.

And not all combined together and shuffled without a PCM identifier ... We must know what PCM the OsID belongs to accurately!

-Enjoy
I gave you one. You told me it was wrong, and then refused to provide even a single example out of 1720 entries, to illustrate why.

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 8:01 am
by Gampy
Gatecrasher wrote:
Gampy wrote:
What we really need is an ACCURATE list of just P04 Os ID's and just P08 Os ID's.
Might as well throw P05 in there as well, as I'm hoping P05 will join the supported list shortly after we are caught up with the current whirlwind of activities.

And not all combined together and shuffled without a PCM identifier ... We must know what PCM the OsID belongs to accurately!

-Enjoy
I gave you one. You told me it was wrong, and then refused to provide even a single example out of 1720 entries, to illustrate why.
That is because it is erroneous, I can't help that ... I'm just stating fact!

I told you what is wrong, there are OsID's marked as P04, that are not P04 OsID's ... That says your source is flawed!

As for giving up my control sample's, how do I know your source is accurate if I give up my control samples.

You seem to have taken it personally ... It isn't, have a good day.

-Enjoy

Re: P04 R&W Testing

Posted: Fri Jun 02, 2023 9:23 am
by Gatecrasher
No worries. I'm sure you'll get there. Good luck. :thumbup:

Re: P04 R&W Testing

Posted: Sun Jun 04, 2023 8:01 am
by rjdrew1986
Gampy,

Should version 021 permit me to read the full Read the entire PCM? (PCM = 12583827). I've tried power cycling & unlocking + 10 seconds.

Here are the results:

[05:55:32:533] PCM Hammer 021
[05:55:32:546] Saturday, June 03 2023 @05:55:32:54
[05:55:32:550] Initializing J2534 Device
[05:55:32:563] Loaded DLL
[05:55:34:942] Connected to the device.
[05:55:34:950] Battery Voltage is: 12.038
[05:55:35:707] Thanks for using PCM Hammer.
[05:56:14:612] Will save to C:\Users\My Computer\Documents\Automotive\ECM\2005 Lesabre\12583827 Full Read.bin
[05:56:19:177] Querying operating system of current PCM.
[05:56:19:242] OSID: 12598603
[05:56:19:338] PCM is already unlocked
[05:56:19:343] Unlock succeeded.
[05:56:19:370] Attempting switch to VPW 4x
[05:56:19:413] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[05:56:43:761] Permission to upload kernel was denied.
[05:56:43:770] If this persists, try cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[05:56:43:781] Failed to upload kernel to PCM
[05:56:43:871] Clearing trouble codes.
[05:56:44:897] Elapsed time 00:00:25.5467566
[05:56:44:903] Read failed, Error

Here is the Debug Log:

[05:55:32:533] PCM Hammer 021
[05:55:32:546] Saturday, June 03 2023 @05:55:32:54
[05:55:32:550] Initializing J2534 Device
[05:55:32:563] Loaded DLL
[05:55:34:942] Connected to the device.
[05:55:34:950] Battery Voltage is: 12.038
[05:55:32:615] Loaded start.txt from network.
[05:55:32:615] Loaded help.html from network.
[05:55:32:617] Loaded credits.html from network.
[05:55:35:703] Protocol Set
[05:55:35:724] Device initialization complete.
[05:55:35:707] Thanks for using PCM Hammer.
[05:56:14:612] Will save to C:\Users\My Computer\Documents\Automotive\ECM\2005 Lesabre\12583827 Full Read.bin
[05:56:19:177] Querying operating system of current PCM.
[05:56:19:201] TX: 6C 10 F0 3C 0A
[05:56:19:238] RX: 6C F0 10 7C 0A 00 C0 3D 4B
[05:56:19:242] OSID: 12598603
[05:56:19:254] Suppressing VPW chatter.
[05:56:19:257] TX: 6C FE F0 28 00
[05:56:19:264] Sending 'test device present' notification.
[05:56:19:267] TX: 8C FE F0 3F
[05:56:19:285] RX: 6C F0 10 68 00
[05:56:19:288] Ignoring chatter: 6C F0 10 68 00
[05:56:19:302] Sending seed request.
[05:56:19:304] TX: 6C 10 F0 27 01
[05:56:19:335] RX: 6C F0 10 67 01 37
[05:56:19:338] PCM is already unlocked
[05:56:19:343] Unlock succeeded.
[05:56:19:360] Sending 'test device present' notification.
[05:56:19:361] TX: 8C FE F0 3F
[05:56:19:370] Attempting switch to VPW 4x
[05:56:19:384] TX: 6C FE F0 A0
[05:56:19:409] RX: 6C F0 10 E0 AA
[05:56:19:410] Parsing 6C F0 10 E0 AA
[05:56:19:413] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[05:56:19:421] Sending 'test device present' notification.
[05:56:19:423] TX: 8C FE F0 3F
[05:56:21:539] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:21:541] Sending 'test device present' notification.
[05:56:21:541] TX: 8C FE F0 3F
[05:56:21:546] TX: 6C FE F0 A1
[05:56:23:551] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:23:556] J2534 setting VPW 4X
[05:56:23:620] Sending 'test device present' notification.
[05:56:23:621] TX: 8C FE F0 3F
[05:56:23:628] Sending 'test device present' notification.
[05:56:23:630] TX: 8C FE F0 3F
[05:56:23:639] Loaded C:\Users\My Computer\Documents\Automotive\ECM\PcmHammer021\Kernel-P01.bin
[05:56:23:649] Sending upload request for kernel size 7890, loadaddress FF8000
[05:56:23:660] TX: 6C 10 F0 34 00 10 00 FF 80 00
[05:56:23:683] RX: 6C F0 10 7F 34 00 10 00 FF 80 33
[05:56:23:687] Received an unexpected response. Attempt #1, status Refused.
[05:56:25:690] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:25:690] Sending 'test device present' notification.
[05:56:25:691] TX: 8C FE F0 3F
[05:56:27:695] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:27:697] Sending 'test device present' notification.
[05:56:27:699] TX: 8C FE F0 3F
[05:56:29:705] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:29:705] Sending 'test device present' notification.
[05:56:29:706] TX: 8C FE F0 3F
[05:56:31:711] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:31:711] Sending 'test device present' notification.
[05:56:31:712] TX: 8C FE F0 3F
[05:56:33:715] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:33:716] Receive timed out. Attempt #6, Timeout #5.
[05:56:33:718] TX: 6C 10 F0 34 00 10 00 FF 80 00
[05:56:33:733] RX: 6C F0 10 7F 34 00 10 00 FF 80 33
[05:56:33:735] Received an unexpected response. Attempt #1, status Refused.
[05:56:35:738] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:35:738] Sending 'test device present' notification.
[05:56:35:739] TX: 8C FE F0 3F
[05:56:37:742] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:37:742] Sending 'test device present' notification.
[05:56:37:743] TX: 8C FE F0 3F
[05:56:39:748] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:39:748] Sending 'test device present' notification.
[05:56:39:749] TX: 8C FE F0 3F
[05:56:41:753] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:41:754] Sending 'test device present' notification.
[05:56:41:755] TX: 8C FE F0 3F
[05:56:43:759] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:56:43:760] Receive timed out. Attempt #6, Timeout #5.
[05:56:43:761] Permission to upload kernel was denied.
[05:56:43:770] If this persists, try cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[05:56:43:781] Failed to upload kernel to PCM
[05:56:43:791] Halting the kernel.
[05:56:43:796] TX: 6C 10 F0 20
[05:56:43:799] J2534 setting VPW 1X
[05:56:43:862] TX: 6C 10 F0 20
[05:56:43:871] Clearing trouble codes.
[05:56:44:131] TX: 68 6A F0 04
[05:56:44:385] TX: 68 6A F0 04
[05:56:44:640] TX: 8C FE F0 14
[05:56:44:894] TX: 8C FE F0 14
[05:56:44:897] Elapsed time 00:00:25.5467566
[05:56:44:903] Read failed, Error