trouble with PCM now...

[RH_K1500]

[06:31:32:443] C:\Users\mlove\OneDrive\Documents\TunerPro Files\Bins\modified truck 4.84x4 12208322.bin
[06:31:32:472] Validating 512k file.
[06:31:32:493] Start End Stored Needed Verdict Segment Name
[06:31:32:513] 00000 7FFFD 7F53 7F53 Good Operating system
[06:31:32:542] 08002 13FFF 0698 0698 Good Engine calibration
[06:31:32:557] 14002 16DFF 4E09 4E09 Good Engine diagnostics.
[06:31:32:576] 16E02 1BDFF 05FE 05FE Good Transmission calibration
[06:31:32:596] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[06:31:32:625] 1C802 1E51F C026 C026 Good Fuel system
[06:31:32:661] 1E522 1EE9F 830B 830B Good System
[06:31:32:689] 1EEA2 1EF9F 34C8 34C8 Good Speedometer
[06:31:32:711] Requesting operating system ID...
[06:31:32:872] Operating system IDs do not match.
[06:31:32:917] PCM operating system ID: 12205612
[06:31:32:949] File operating system ID: 12208322
[06:31:32:979] Changing PCM to operating system 12208322
[06:31:33:190] Unlock succeeded.
[06:31:33:326] This interface does not support VPW 4x
[06:31:33:375] Requesting permission to upload kernel.
[06:31:33:457] Upload permission granted.
[06:31:34:307] Kernel upload 9% complete.
[06:31:35:414] Kernel upload 22% complete.
[06:31:36:465] Kernel upload 35% complete.
[06:31:37:586] Kernel upload 48% complete.
[06:31:38:690] Kernel upload 61% complete.
[06:31:39:795] Kernel upload 74% complete.
[06:31:40:857] Kernel upload 87% complete.
[06:31:41:980] Kernel upload 100% complete.
[06:31:43:440] Kernel Version: 010302BB
[06:31:43:467] Kernel uploaded to PCM succesfully.
[06:31:43:587] Changing PCM to operating system 12208322
[06:31:43:776] Flash chip: Intel 28F400B, 512kb
[06:31:43:845] Calculating CRCs from file.
[06:31:43:872] Initializing CRC algorithm on PCM, this will take a minute...
[06:31:54:725] Requesting CRCs from PCM.
[06:31:54:785] Range File CRC PCM CRC Verdict Purpose
[06:32:00:003] 060000-07FFFF D5119D18 A57FD6CC Different OperatingSystem
[06:32:05:222] 040000-05FFFF EDBD6276 AE68FAB6 Different OperatingSystem
[06:32:10:583] 020000-03FFFF B98BA561 A4123191 Different OperatingSystem
[06:32:14:908] 008000-01FFFF 7809F88F CB627408 Different Calibration
[06:32:14:939] 006000-007FFF not needed not needed n/a Parameter
[06:32:14:966] 004000-005FFF not needed not needed n/a Parameter
[06:32:16:921] 000000-003FFF 023488D6 19F13196 Different Boot
[06:32:16:989] Processing range 060000-07FFFF
[06:32:17:017] Erasing.
[06:32:31:734] Unable to erase flash memory: Error
[06:32:31:756] Select the debug tab, click anywhere in the text,
[06:32:31:778] press Ctrl+A to select the text, and Ctrl+C to
[06:32:31:804] copy the text. Press Ctrl+V to paste that content
[06:32:31:825] content into your forum post.
[06:32:31:847] Elapsed time 00:00:58.6094158


this is after a successful write test, i tried to preform a write OS, calibration and boot with the new .bin yes the OS is different then the Factory OS because i could not find an XDF for 12205612 OS... and now the truck wont do anything but crank.. did i brick the ECM??? if so, how do i "un-brick" it? or if i go get another PCM from a yard, one from the same year, with the same motor, trans, and 4x4 will i be able to plug that one in on the truck and get it to start? i was using PCM Hammer and Tuner Pro with OBDLink LX. can someone help please?


this was the test write:
[06:23:44:345] C:\Users\mlove\OneDrive\Documents\TunerPro Files\Bins\modified truck 4.84x4 12208322.bin
[06:23:44:371] Validating 512k file.
[06:23:44:417] Start End Stored Needed Verdict Segment Name
[06:23:44:500] 00000 7FFFD 7F53 7F53 Good Operating system
[06:23:44:517] 08002 13FFF 0698 0698 Good Engine calibration
[06:23:44:533] 14002 16DFF 4E09 4E09 Good Engine diagnostics.
[06:23:44:550] 16E02 1BDFF 05FE 05FE Good Transmission calibration
[06:23:44:564] 1BE02 1C7FF B4CC B4CC Good Transmission diagnostics
[06:23:44:568] 1C802 1E51F C026 C026 Good Fuel system
[06:23:44:585] 1E522 1EE9F 830B 830B Good System
[06:23:44:598] 1EEA2 1EF9F 34C8 34C8 Good Speedometer
[06:23:44:614] Requesting operating system ID...
[06:23:44:888] Operating system IDs do not match.
[06:23:44:913] PCM operating system ID: 12205612
[06:23:44:931] File operating system ID: 12208322
[06:23:44:949] PCM and image file are different operating systems.
[06:23:44:981] But we'll ignore that because this is just a test write.
[06:23:45:160] Unlock succeeded.
[06:23:45:237] This interface does not support VPW 4x
[06:23:45:271] Requesting permission to upload kernel.
[06:23:45:363] Upload permission granted.
[06:23:46:201] Kernel upload 9% complete.
[06:23:47:224] Kernel upload 22% complete.
[06:23:48:260] Kernel upload 35% complete.
[06:23:49:355] Kernel upload 48% complete.
[06:23:50:407] Kernel upload 61% complete.
[06:23:51:470] Kernel upload 74% complete.
[06:23:52:509] Kernel upload 87% complete.
[06:23:53:607] Kernel upload 100% complete.
[06:23:55:079] Kernel Version: 010302BB
[06:23:55:101] Kernel uploaded to PCM succesfully.
[06:23:55:235] PCM and image file are different operating systems.
[06:23:55:258] But we'll ignore that because this is just a test write.
[06:23:55:540] Flash chip: Intel 28F400B, 512kb
[06:23:55:611] Calculating CRCs from file.
[06:23:55:640] Initializing CRC algorithm on PCM, this will take a minute...
[06:24:06:693] Requesting CRCs from PCM.
[06:24:06:730] Range File CRC PCM CRC Verdict Purpose
[06:24:06:757] 060000-07FFFF not needed not needed n/a OperatingSystem
[06:24:06:787] 040000-05FFFF not needed not needed n/a OperatingSystem
[06:24:06:811] 020000-03FFFF not needed not needed n/a OperatingSystem
[06:24:11:223] 008000-01FFFF 7809F88F CB627408 Different Calibration
[06:24:11:249] 006000-007FFF not needed not needed n/a Parameter
[06:24:11:270] 004000-005FFF not needed not needed n/a Parameter
[06:24:11:285] 000000-003FFF not needed not needed n/a Boot
[06:24:11:339] Processing range 008000-01FFFF
[06:24:11:352] Pretending to erase.
[06:24:11:372] Pretending to write...
[06:25:57:844] Calculating CRCs from file.
[06:25:57:865] Initializing CRC algorithm on PCM, this will take a minute...
[06:25:58:021] Requesting CRCs from PCM.
[06:25:58:053] Range File CRC PCM CRC Verdict Purpose
[06:25:58:076] 060000-07FFFF not needed not needed n/a OperatingSystem
[06:25:58:104] 040000-05FFFF not needed not needed n/a OperatingSystem
[06:25:58:131] 020000-03FFFF not needed not needed n/a OperatingSystem
[06:26:02:412] 008000-01FFFF 7809F88F CB627408 Different Calibration
[06:26:02:441] 006000-007FFF not needed not needed n/a Parameter
[06:26:02:471] 004000-005FFF not needed not needed n/a Parameter
[06:26:02:491] 000000-003FFF not needed not needed n/a Boot
[06:26:02:550] Test write complete.
[06:26:02:580] All write-request messages succeeded on the first try. You have an excellent connection to the PCM.
[06:26:02:611] We're not sure how much retrying is normal for a write operation on a 512kb PCM.
[06:26:02:637] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[06:26:02:795] Clearing trouble codes.
[06:26:03:969] Elapsed time 00:02:18.7853503

[B52Bombardier1]

Yes, it could be bricked and I hope you still have a functional PCM somewhere. Always experiment with a spare PCM. You Tube has a video for how to unbrick a P01 PCM. It is done by grounding a particular pin on the PCM printed circuit board and then IMMEDIATELY launching PCM Hammer or LS Droid. You have about a 15 second window of opportunity here to assert control over your PCM.

Did you perform your failed write on a bench harness? I highly recommend doing all of this with a bench harness and you will certainly need one to recover this PCM. A bench harness gives you better control of the PCM input power to keep it above about 12.2 volts.

A bench harness is also electronically quiet compared to writing with the PCM in a vehicle.

An exact same PCM from a different but configured the same junk yard vehicle won't immediately help you. It still has VATS enabled and will prevent you from starting your vehicle. Tuner Pro editing will be required here.

Rick

[RH_K1500]

Thank you for responding! Yes I have a spare, but I did make the mistake of attempting this on the truck, hope I didn't jack anything else up �� can you tell me where I went wrong in my process? Other than using the truck?

[kur4o]

Didn`t you do a test read first, than try write cal only to confirm everything is good and you are still able to recover the pcm.

If the boot block[which looks like] is erased start looking for a replacement pcm.

[B52Bombardier1]

It is impossible to know where it went wrong for you. As suggested, if the truck voltage went low or other modules in the vehicle caused noisy chatter while you were writing is where my suspicions lie.

LS Droid now enforces three successful "Cal only" writes on Android devices before unlocking the capability to write a complete OS BIN to any PCM. I recently went through this unlocking process on my Android Kindle and Android Samsung phone. Tedious? Yes. But it relatively ensures that you have a reliable ability to perform the work and not brick a PCM.

Rick