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: 1788
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 021

Postby Gampy » Fri Jun 24, 2022 12:41 pm

As I already stated, recovery mode will not help ... The code path is the same.

I'm wondering if for some reason it's rejecting the 4096 (0x1000) byte request.
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!

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

Re: PCM Hammer Release 021

Postby antus » Fri Jun 24, 2022 1:30 pm

the boot sector code is a different code path inside the pcm - we have used this to fix a problem that looked identical to this on NSFW's pcm.
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

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

Re: PCM Hammer Release 021

Postby kur4o » Fri Jun 24, 2022 4:26 pm

Code: Select all
tst.b   (PCM_unlocked_1_byte_FFFF92CD).w
bne.s   loc_415C6
moveq   #$33,d0 ; '3'
bra.s   loc_415B2


I examined the error code $33 being send. It looks like the issue is between unlocking pcm and upload request. Pcm, somehow got reset and gets locked before mode 34 is send. I suspect a mode 20 is send at one point that resets unlocked state.

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

Re: PCM Hammer Release 021

Postby antus » Sat Jun 25, 2022 1:58 am

not by pcmhammer. maybe something else on the bus. does a bench flash with only the pcm work? also if testing, does 20 work everything else being equal?
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396

Posts: 46
Joined: Sat Nov 13, 2021 11:21 am

Re: PCM Hammer Release 021

Postby persingc » Sat Jun 25, 2022 11:41 am

Thank you for your continued support of your tool. Because of it I've learned so much.

Posts: 16
Joined: Wed Jun 01, 2022 8:02 am

Re: PCM Hammer Release 021

Postby MercRising » Sat Jun 25, 2022 2:05 pm

Unsure if it's user error or what, but unable to read though VCX Nano, but this is my first install and have never made a successful read. I can get details OK, so I know it's speaking to it, but fails after step that clears codes.

PCMH appears to read the PCM though my bench set up, which does read the PCMs and flash OK via HP Tuners. First go at VCX Nano and PCMH to make some clones on po1 and p59 GM stuff.

Here's the debug from latest attempt. Log looks like BillNobody's, and I have tried 3 pcms; a couple v6 p01 and this p59 in the log below. All fail to read.

[10:01:24:535] PCM Hammer 021
[10:01:24:541] Friday, June 24 2022 @10:01:24:54
[10:01:24:546] Initializing J2534 Device
[10:01:24:553] DLL already loaded, unloading before proceeding
[10:01:24:560] Existing DLL successfully unloaded.
[10:01:24:582] Loaded DLL
[10:01:24:749] Connected to the device.
[10:01:24:795] Battery Voltage is: 11.826
[10:01:25:815] Protocol Set
[10:01:25:862] Device initialization complete.
[10:01:59:035] TX: 6C 10 F0 3C 01
[10:01:59:084] RX: 6C F0 10 7C 01 00 33 47 4E 45 43
[10:01:59:095] TX: 6C 10 F0 3C 02
[10:01:59:162] RX: 6C F0 10 7C 02 31 33 54 39 33 47
[10:01:59:169] TX: 6C 10 F0 3C 03
[10:01:59:226] RX: 6C F0 10 7C 03 31 38 30 39 30 34
[10:01:59:235] VIN: 3GNEC13T93G180904
[10:01:59:251] TX: 6C 10 F0 3C 0A
[10:01:59:304] RX: 6C F0 10 7C 0A 00 BF F2 4D
[10:01:59:314] OS ID: 12579405
[10:01:59:329] Hardware Type: P01_P59
[10:01:59:349] TX: 6C 10 F0 3C 08
[10:01:59:416] RX: 6C F0 10 7C 08 00 BF F2 4C
[10:01:59:425] Calibration ID: 12579404
[10:01:59:440] TX: 6C 10 F0 3C 04
[10:01:59:509] RX: 6C F0 10 7C 04 00 BF CF BE
[10:01:59:519] Hardware ID: 12570558
[10:01:59:535] TX: 6C 10 F0 3C 05
[10:01:59:603] RX: 6C F0 10 7C 05 33 35 30 30
[10:01:59:613] TX: 6C 10 F0 3C 06
[10:01:59:681] RX: 6C F0 10 7C 06 30 39 30 32
[10:01:59:692] TX: 6C 10 F0 3C 07
[10:01:59:757] RX: 6C F0 10 7C 07 32 33 32 32
[10:01:59:768] Serial Number: 350009022322
[10:01:59:797] TX: 6C 10 F0 3C 14
[10:01:59:866] RX: 6C F0 10 7C 14 59 43 54 4B
[10:01:59:878] Broad Cast Code: YCTK
[10:01:59:895] TX: 6C 10 F0 3C A0
[10:01:59:944] RX: 6C F0 10 7C A0 00
[10:01:59:954] MEC: 0
[10:02:10:946] Will save to C:\Users\super\OneDrive\Desktop\Tuning\VX Diag\PCM Hammer Reads\1st read.bin
[10:02:12:720] Querying operating system of current PCM.
[10:02:12:755] TX: 6C 10 F0 3C 0A
[10:02:12:861] RX: 6C F0 10 7C 0A 00 BF F2 4D
[10:02:12:871] OSID: 12579405
[10:02:12:894] Suppressing VPW chatter.
[10:02:12:904] TX: 6C FE F0 28 00
[10:02:12:940] Sending 'test device present' notification.
[10:02:12:950] TX: 8C FE F0 3F
[10:02:12:988] RX: 6C F0 10 68 00
[10:02:13:010] Ignoring chatter: 6C F0 10 68 00
[10:02:13:060] Sending seed request.
[10:02:13:096] TX: 6C 10 F0 27 01
[10:02:13:207] RX: 6C F0 10 67 01 37
[10:02:13:218] PCM is already unlocked
[10:02:13:234] Unlock succeeded.
[10:02:13:273] Sending 'test device present' notification.
[10:02:13:305] TX: 8C FE F0 3F
[10:02:13:330] Attempting switch to VPW 4x
[10:02:13:349] TX: 6C FE F0 A0
[10:02:13:407] RX: 6C F0 10 E0 AA
[10:02:13:418] Parsing 6C F0 10 E0 AA
[10:02:13:430] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[10:02:13:455] Sending 'test device present' notification.
[10:02:13:473] TX: 8C FE F0 3F
[10:02:15:625] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:15:635] Sending 'test device present' notification.
[10:02:15:645] TX: 8C FE F0 3F
[10:02:15:688] TX: 6C FE F0 A1
[10:02:17:720] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:17:732] J2534 setting VPW 4X
[10:02:17:951] Sending 'test device present' notification.
[10:02:17:956] TX: 8C FE F0 3F
[10:02:17:966] Sending 'test device present' notification.
[10:02:17:971] TX: 8C FE F0 3F
[10:02:17:983] Loaded C:\Users\super\OneDrive\Desktop\Tuning\VX Diag\PcmHammer021\Kernel-P01.bin
[10:02:17:990] Sending upload request for kernel size 7890, loadaddress FF8000
[10:02:18:000] TX: 6C 10 F0 34 00 10 00 FF 80 00
[10:02:20:017] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:20:022] Sending 'test device present' notification.
[10:02:20:027] TX: 8C FE F0 3F
[10:02:22:058] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:22:066] Sending 'test device present' notification.
[10:02:22:080] TX: 8C FE F0 3F
[10:02:24:122] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:24:133] Sending 'test device present' notification.
[10:02:24:145] TX: 8C FE F0 3F
[10:02:26:176] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:26:193] Sending 'test device present' notification.
[10:02:26:215] TX: 8C FE F0 3F
[10:02:28:268] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:28:280] Receive timed out. Attempt #5, Timeout #5.
[10:02:28:291] TX: 6C 10 F0 34 00 10 00 FF 80 00
[10:02:30:322] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:30:335] Sending 'test device present' notification.
[10:02:30:357] TX: 8C FE F0 3F
[10:02:32:396] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:32:411] Sending 'test device present' notification.
[10:02:32:426] TX: 8C FE F0 3F
[10:02:34:460] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:34:472] Sending 'test device present' notification.
[10:02:34:485] TX: 8C FE F0 3F
[10:02:36:530] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:36:546] Sending 'test device present' notification.
[10:02:36:587] TX: 8C FE F0 3F
[10:02:38:636] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:02:38:644] Receive timed out. Attempt #5, Timeout #5.
[10:02:38:656] Permission to upload kernel was denied.
[10:02:38:670] If this persists, try cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[10:02:38:684] Failed to upload kernel to PCM
[10:02:38:705] Halting the kernel.
[10:02:38:723] TX: 6C 10 F0 20
[10:02:38:745] J2534 setting VPW 1X
[10:02:38:982] TX: 6C 10 F0 20
[10:02:39:012] Clearing trouble codes.
[10:02:39:280] TX: 68 6A F0 04
[10:02:39:559] TX: 68 6A F0 04
[10:02:39:857] TX: 8C FE F0 14
[10:02:40:124] TX: 8C FE F0 14
[10:02:40:141] Elapsed time 00:00:26.8682767
[10:02:40:157] Read failed, Error

Quite likely something I am missing, appreciate the help.

User avatar
Posts: 1788
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer Release 021

Postby Gampy » Sun Jun 26, 2022 12:50 am

Welcome MercRising,

I do not believe this to be the same issue ...

Does your bench harness follow this Bench Harness Schematic ??
Sorry, just had to ask ...

IMO the voltage,
[10:01:24:795] Battery Voltage is: 11.826
is low, please raise the voltage a couple of volts, over +12.6v is good.

If your using a Wal-Wart type power supply (Cell Phone Charger), get a better one, one with clean power, modern PWM type units don't work well!
Start digging through your tote of Wal-Warts and pick the heaviest +12v unit that supplies at least 1 Amp.

Here is the catch ... 1 Amp is fine for most basic users, however if you plan on adding a second VCI for bus activity logging, you'll want a power supply that supplies more then 1 Amp.

Also, it's reporting,
[10:02:13:218] PCM is already unlocked
That indicates multiple attempts without a complete reboot.

Please disconnect USB, disconnect OBDII, disconnect battery (remove all power), and turn off ignition switch for 1 minute or more (I like to reboot my PC as well, then everything is in a known state), then,
1. Connect Battery.
2. Connect OBDII
. . Wait for VCI to fully boot
4. Connect USB.
5. Start PcmHammer.
5.a. Select Device if needed.
6. Turn Ignition on.
7. Select 'Read Entire PCM' from the Tools menu.

Waiting 5 or 10 seconds between steps does not hurt!
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!

Posts: 16
Joined: Wed Jun 01, 2022 8:02 am

Re: PCM Hammer Release 021

Postby MercRising » Sun Jun 26, 2022 1:28 am

Will give those reboot steps shot, and think I have a few more power sources I can try. Cheers :punk:

Posts: 206
Joined: Fri Jul 30, 2021 5:49 pm

Re: PCM Hammer Release 021

Postby Cincinnatus » Sun Jun 26, 2022 10:37 am

So I tested my nano with v20 and v21 and both read (in vehicle) 2 p01s and 1 p59. I will say there is something weird that v20 and earlier would slow down (kb/s) during read in vehicle and have multiple retries, but v21 never slowed and had no retries. I did have weird problem that afterwards my 97 0411 swapped Vette won't run for more than 1 second after a read and I have to remove battery power (this happened the last time I did an in vehicle read also) before car will stay running. Vats is disabled by hptuning. I also had no power windows and also had reduced engine power on dic until battery power was removed and restored. My stock 2002 p01 van wouldn't run either (after an in vehicle read) for a few tries but after removing key it eventually did without removing battery power and it is stock. I had no issues on my stock p59 Silverado after an in vehicle read.

Posts: 206
Joined: Fri Jul 30, 2021 5:49 pm

Re: PCM Hammer Release 021

Postby Cincinnatus » Sun Jun 26, 2022 6:15 pm

After investigating this, the in vehicle read is causing other modules to error when they lose comm with the PCM and each other. I verified this by scanning with tech2win and had many u code errors in multiple modules. If you don't reset them by removing power or clearing the errors with scan tool, the car can become unresponsive. I've not had this issue with my hp software, so it's avoidable with code I assume.

PreviousNext

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: Google [Bot] and 5 guests