P01 Write Parameters failure

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

P01 Write Parameters failure

Post by Gampy »

Hi all,

Help!

Did a "Write Parameters" on a P01, it failed ... Retried immediately and it still failed, thought to myself, no big deal it's just a parameter block, recovery should fix that, rebooted, short pinned it ... No success!
I believe the failure message was 'Unable to erase flash memory. Code: ', I forget the code, I'm pissed at myself for not saving the log!

So, after rebooting, I tried a typical normal "Write Parameters",
[09:56:18:492] PCM Hammer (11/29/2020, 4:08 PM)
[09:56:19:534] Voltage: 13.5V
[09:56:19:550] Elm ID: ELM327 v1.3a
[09:56:19:582] ScanTool device ID: STN1110 v4.2.1
[09:56:33:347] T:\Automotive\GM_ECU\PcmData\Mine\BDM\12208322_SvN12200411.bin
[09:56:33:369] Validating 512k file.
[09:56:33:372] Start End Stored Needed Verdict Segment Name
[09:56:33:391] 00000 7FFFD 7F53 7F53 Good Operating system
[09:56:33:395] 08002 13FFF 375F 375F Good Engine calibration
[09:56:33:400] 14002 16DFF 0DC8 0DC8 Good Engine diagnostics.
[09:56:33:405] 16E02 1BDFF 01FF 01FF Good Transmission calibration
[09:56:33:411] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[09:56:33:420] 1C802 1E51F 1D08 1D08 Good Fuel system
[09:56:33:428] 1E522 1EE9F 06AE 06AE Good System
[09:56:33:438] 1EEA2 1EF9F 3BEC 3BEC Good Speedometer
[09:56:33:448] Requesting operating system ID...
[09:56:33:629] PCM and file are both operating system 12208322
[09:56:33:775] PCM Unlock not required
[09:56:33:785] Unlock succeeded.
[09:56:33:858] This interface does not support VPW 4x
[09:56:33:889] Requesting permission to upload kernel.
[09:56:34:056] Requesting permission to upload kernel.
[09:56:34:217] Requesting permission to upload kernel.
[09:56:34:370] Requesting permission to upload kernel.
[09:56:34:529] Requesting permission to upload kernel.
[09:56:34:698] Permission to upload kernel was denied.
[09:56:34:708] If this persists, try cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[09:56:34:719] Failed to upload kernel to PCM
[09:56:34:731] Elapsed time 00:00:00.9355468
Debug log,
PcmHammer_debugLog_20201130@095638.txt
(4.65 KiB) Downloaded 137 times
Still responds to OsID, that's good!

Then tried the Short-trick,
[09:57:39:991] PCM Hammer (11/29/2020, 4:08 PM)
[09:57:41:043] Voltage: 13.7V
[09:57:41:059] Elm ID: ELM327 v1.3a
[09:57:41:091] ScanTool device ID: STN1110 v4.2.1
[09:58:04:664] T:\Automotive\GM_ECU\PcmData\Mine\BDM\12208322_SvN12200411.bin
[09:58:04:689] Validating 512k file.
[09:58:04:693] Start End Stored Needed Verdict Segment Name
[09:58:04:709] 00000 7FFFD 7F53 7F53 Good Operating system
[09:58:04:714] 08002 13FFF 375F 375F Good Engine calibration
[09:58:04:718] 14002 16DFF 0DC8 0DC8 Good Engine diagnostics.
[09:58:04:724] 16E02 1BDFF 01FF 01FF Good Transmission calibration
[09:58:04:730] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[09:58:04:739] 1C802 1E51F 1D08 1D08 Good Fuel system
[09:58:04:748] 1E522 1EE9F 06AE 06AE Good System
[09:58:04:757] 1EEA2 1EF9F 3BEC 3BEC Good Speedometer
[09:58:04:768] Requesting operating system ID...
[09:58:15:616] Operating system request failed, checking for a live kernel...
[09:58:21:481] Checking for recovery mode...
[09:58:30:125] PCM is not responding to OSID, kernel version, or recovery mode checks.
[09:58:30:135] Unlock may not work, but we'll try...
[09:58:30:255] PCM Unlock not required
[09:58:30:265] Unlock succeeded.
[09:58:30:336] This interface does not support VPW 4x
[09:58:30:348] Something went wrong. Object reference not set to an instance of an object.
[09:58:30:358] Do not power off the PCM! Do not exit this program!
[09:58:30:368] Try flashing again. If errors continue, seek help online.
[09:58:30:379] viewtopic.php?f=42&t=6080
[09:58:30:392]
[09:58:30:440] System.NullReferenceException: Object reference not set to an instance of an object.
at PcmHacking.CKernelWriter.<Write>d__6.MoveNext()
[09:58:30:451] Elapsed time 00:00:00.1757812
Debug log,
PcmHammer_debugLog_20201130@095851.txt
(8.29 KiB) Downloaded 129 times
I do have BDM, however I would like to get PcmHammer to recover this if possible, obviously the Os is responding, at least it's responding to the OsID query,
[09:56:33:505] TX: STPX H:6C10F0, R:1, D:3C0A
[09:56:33:617] RX: 6C F0 10 7C 0A 00 BA 48 C2
I will be attempting to track down the Null Reference Exception, it's not the cause, it's the results of, but needs to be trapped.

Suggestions ??
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
Gampy
Posts: 2333
Joined: Sat Dec 15, 2018 7:38 am

Re: P01 Write Parameters failure

Post by Gampy »

So, I hooked up the BDM and read the PCM, the resulting binary, And the original binary,
12208322_SvN12200411.bin
(512 KiB) Downloaded 130 times
While I had the BDM hooked up I wrote the above binary.

Tested it, all was good, PCM Hammer successfully "Verify Entire PCM".

Then did a "Write Parameters", it failed, followed that immediately with a "Write Full Flash (Clone)", it failed.

I did save the logs this time ...
[06:39:38:607] PCM Hammer (11/30/2020, 5:24 PM)
[06:39:39:740] Voltage: 12.6V
[06:39:39:756] Elm ID: ELM327 v1.3a
[06:39:39:788] ScanTool device ID: STN1110 v4.2.1
[06:40:13:357] T:\Automotive\GM_ECU\PcmData\Mine\BDM\12208322_SvN12200411.bin
[06:40:13:378] Validating 512k file.
[06:40:13:380] Start End Stored Needed Verdict Segment Name
[06:40:13:385] 00000 7FFFD 7F53 7F53 Good Operating system
[06:40:13:390] 08002 13FFF 375F 375F Good Engine calibration
[06:40:13:394] 14002 16DFF 0DC8 0DC8 Good Engine diagnostics.
[06:40:13:400] 16E02 1BDFF 01FF 01FF Good Transmission calibration
[06:40:13:406] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[06:40:13:412] 1C802 1E51F 1D08 1D08 Good Fuel system
[06:40:13:420] 1E522 1EE9F 06AE 06AE Good System
[06:40:13:429] 1EEA2 1EF9F 3BEC 3BEC Good Speedometer
[06:40:13:439] Requesting operating system ID...
[06:40:13:559] PCM and file are both operating system 12208322
[06:40:13:719] Unlock succeeded.
[06:40:13:767] This interface does not support VPW 4x
[06:40:13:784] Requesting permission to upload kernel.
[06:40:13:831] Upload permission granted.
[06:40:14:696] Kernel upload 9% complete.
[06:40:15:815] Kernel upload 22% complete.
[06:40:16:918] Kernel upload 35% complete.
[06:40:18:071] Kernel upload 48% complete.
[06:40:19:191] Kernel upload 61% complete.
[06:40:20:343] Kernel upload 74% complete.
[06:40:21:446] Kernel upload 87% complete.
[06:40:22:582] Kernel upload 100% complete.
[06:40:23:990] Kernel Version: 010301BB
[06:40:24:000] Kernel uploaded to PCM succesfully.
[06:40:24:102] PCM and image file are both operating system 12208322
[06:40:24:230] Flash chip: Intel 28F400B, 512kb
[06:40:24:292] Calculating CRCs from file...
[06:40:24:308] Requesting CRCs from PCM...
[06:40:35:091] Range File CRC PCM CRC Verdict Purpose
[06:40:35:103] 060000-07FFFF not needed not needed n/a OperatingSystem
[06:40:35:117] 040000-05FFFF not needed not needed n/a OperatingSystem
[06:40:35:133] 020000-03FFFF not needed not needed n/a OperatingSystem
[06:40:35:150] 008000-01FFFF not needed not needed n/a Calibration
[06:40:36:804] 006000-007FFF 85B5BB36 AAC258F8 Different Parameter
[06:40:38:467] 004000-005FFF 390F1E5F 85B5BB36 Different Parameter
[06:40:38:487] 000000-003FFF not needed not needed n/a Boot
[06:40:38:546] Processing range 006000-007FFF
[06:40:38:569] Erasing.
[06:40:38:628] Unable to erase flash memory. Code: A8
[06:40:38:646] Select the debug tab, click anywhere in the text,
[06:40:38:661] press Ctrl+A to select the text, and Ctrl+C to
[06:40:38:677] copy the text. Press Ctrl+V to paste that content
[06:40:38:692] content into your forum post.
[06:40:38:705] Elapsed time 00:00:24.9775390
[06:53:32:618] T:\Automotive\GM_ECU\PcmData\Mine\BDM\12208322_SvN12200411.bin
[06:53:32:657] Validating 512k file.
[06:53:32:667] Start End Stored Needed Verdict Segment Name
[06:53:32:683] 00000 7FFFD 7F53 7F53 Good Operating system
[06:53:32:698] 08002 13FFF 375F 375F Good Engine calibration
[06:53:32:712] 14002 16DFF 0DC8 0DC8 Good Engine diagnostics.
[06:53:32:729] 16E02 1BDFF 01FF 01FF Good Transmission calibration
[06:53:32:745] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[06:53:32:763] 1C802 1E51F 1D08 1D08 Good Fuel system
[06:53:32:782] 1E522 1EE9F 06AE 06AE Good System
[06:53:32:801] 1EEA2 1EF9F 3BEC 3BEC Good Speedometer
[06:53:32:821] Requesting operating system ID...
[06:53:43:567] Operating system request failed, checking for a live kernel...
[06:53:43:613] Kernel version: 010301BB
[06:53:43:631] Asking kernel for the PCM's operating system ID...
[06:53:45:024] PCM and image file are both operating system 12208322
[06:53:45:164] Flash chip: Intel 28F400B, 512kb
[06:53:45:228] Calculating CRCs from file...
[06:53:45:250] Requesting CRCs from PCM...
[06:53:56:042] Range File CRC PCM CRC Verdict Purpose
[06:54:01:979] 060000-07FFFF D5119D18 D5119D18 Same OperatingSystem
[06:54:06:794] 040000-05FFFF EDBD6276 EDBD6276 Same OperatingSystem
[06:54:11:610] 020000-03FFFF B98BA561 B98BA561 Same OperatingSystem
[06:54:15:608] 008000-01FFFF D6327EBB D6327EBB Same Calibration
[06:54:17:256] 006000-007FFF 85B5BB36 01130F9D Different Parameter
[06:54:18:920] 004000-005FFF 390F1E5F 85B5BB36 Different Parameter
[06:54:20:777] 000000-003FFF 023488D6 023488D6 Same Boot
[06:54:20:839] Processing range 006000-007FFF
[06:54:20:859] Erasing.
[06:54:20:918] Unable to erase flash memory. Code: A8
[06:54:20:937] Select the debug tab, click anywhere in the text,
[06:54:20:954] press Ctrl+A to select the text, and Ctrl+C to
[06:54:20:973] copy the text. Press Ctrl+V to paste that content
[06:54:20:992] content into your forum post.
[06:54:21:010] Elapsed time 00:00:36.1210937
Debug log,
PcmHammer_debugLog_20201130@185547.txt
(78.28 KiB) Downloaded 121 times
Going to BDM recover, then test using PcmHammer014 pre-built ...
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!
kur4o
Posts: 953
Joined: Sun Apr 10, 2016 9:20 pm

Re: P01 Write Parameters failure

Post by kur4o »

You have some serious problem. The first 18 bytes got erased in half. Thay changed state to 00, instead of FF.
And you got the error at the end. I guess the erase verification didn`t pass.

If the erase alogorithm is not the issue. Or some timings associated with it or internal vpp voltage you can have a chip failure very soon.

Try cal data only erase and than read the file to confirm erase problems at other areas.

I think the timings might get better. It should also get an error on the first word failure to erase fully, not the 9th.
In-Tech
Posts: 788
Joined: Mon Mar 09, 2020 4:35 pm
Location: California

Re: P01 Write Parameters failure

Post by In-Tech »

Low voltage will allow a 00 and not fuse to FF especially in protected areas that require that small amount of extra current on the substrate. I have not tested on any gm stuff... protected areas in other stufff, usually has an "attribute" check to see if "read only" and then it checks "write allowed/security passed" on each bit change which requires more current/voltage because the processor has more tics involved.
User avatar
Gampy
Posts: 2333
Joined: Sat Dec 15, 2018 7:38 am

Re: P01 Write Parameters failure

Post by Gampy »

Thanks for the responses, sorry for the delay, our power was down for close to 24 hours, fortunately we have a generator, then the internet went down ...

Anyways, there are two bugs in PcmHmmer current, one was introduced by no other then I ... A P01 erase issue.
The other is a Recovery Mode issue that caused Recovery Mode to fail with a Null Reference Exception.

PR's will be posted ASAP.
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