PCM Hammer - new ls1 flash tool

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
Posts: 17
Joined: Wed Dec 06, 2017 1:02 pm

Re: PCM Hammer - new ls1 flash tool

Postby Vampyre » Sat Nov 30, 2019 3:35 am

successfully wrote new vin to v6 pcm this morning

AVT filter configured
[11:19:34:674] TX: 6C 10 F0 3C 0A
[11:19:34:690] RX: 6C F0 10 7C 0A 00 BA 2D F7
[11:19:34:768] TX: 6C 10 F0 3C 01
[11:19:34:784] RX: 6C F0 10 7C 01 00 31 47 32 4E 56
[11:19:34:784] TX: 6C 10 F0 3C 02
[11:19:34:815] RX: 6C F0 10 7C 02 31 32 45 33 59 4D
[11:19:34:815] TX: 6C 10 F0 3C 03
[11:19:34:830] RX: 6C F0 10 7C 03 37 38 37 31 37 30
[11:19:37:048] Sending seed request.
[11:19:37:048] TX: 6C 10 F0 27 01
[11:19:37:064] RX: 6C F0 10 67 01 25 4A
[11:19:37:080] Parsing seed value.
[11:19:37:080] Sending unlock request (4A25, 8259)
[11:19:37:080] TX: 6C 10 F0 27 02 82 59
[11:19:37:111] RX: 6C F0 10 67 02 34
[11:19:37:173] Changing VIN to 1G2NV12E3YM787170
[11:19:37:173] Block 1
[11:19:37:189] TX: 6C 10 F0 3B 01 00 31 47 32 4E 56
[11:19:37:189] Successful write to block 1
[11:19:37:189] Block 2
[11:19:37:205] TX: 6C 10 F0 3B 02 31 32 45 33 59 4D
[11:19:37:205] Successful write to block 2
[11:19:37:205] Block 3
[11:19:37:220] TX: 6C 10 F0 3B 03 37 38 37 31 37 30
[11:19:37:220] Successful write to block 3
[11:19:37:220] VIN successfully updated to 1G2NV12E3YM787170

now issue is program is trying to validate file, but since its got different check sums comes back as invalid file so cant write or clone.

[11:22:41:268] E:\cals\v6\2000gagt1factoryourvinserial.bin
[11:22:41:393] Validating 512k file.
[11:22:41:393] This file does not contain the expected signature at 0x1FFFE.
[11:22:41:408] Start End Stored Needed Verdict Segment Name
[11:22:41:471] Checksum table is corrupt.
[11:22:41:487] This file is corrupt. It would render your PCM unusable.

User avatar
Posts: 219
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Postby NSFW » Sat Nov 30, 2019 9:34 am

Thanks for those logs. The app does recognize the flash chip after all.

The parameter blocks are where the PCM stores information about check-engine lights (and probably some other stuff) so it's totally normal for them to change from one power cycle to the next.
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 10
Joined: Tue Nov 26, 2019 5:29 am

Re: PCM Hammer - new ls1 flash tool

Postby PeterTremonti » Wed Dec 04, 2019 8:14 am

I'm having an issue writing the original bin to a P59 PCM. It seems to loop multiple times and not finish.

First I tried loading just a .cal file. Looped until cancelled.
Recovered to the original bin with LSDroid.
Tried loading a modified bin that removed VATs and it did the same thing. Cancelled again.
Tried loading the original bin to see if that was the issue. No luck.
I can try again if you have any pointers or suggestions.

Not sure what's going on so I'll just leave this here for you smarter people to look over. Here are the Debug Log tab and the Results tab in .txt form from when I tried again today to write the "2003SuburbanDBW5.3FlexFuelpetertcodesandvats.bin" into the PCM with PCM Hammer's "Write Calibration" button.
Attachments
Results Log VATS delete file into original PCM.txt
(279.24 KiB) Downloaded 2 times
Debug Log VATS delete file into original PCM.txt
(14.08 MiB) Downloaded 3 times
2003SuburbanDBW5.3FlexFuelpetertcodesandvats.bin
(1 MiB) Downloaded 3 times

User avatar
Posts: 1888
Joined: Thu May 17, 2012 8:53 pm
Location: WA

Re: PCM Hammer - new ls1 flash tool

Postby Tazzi » Wed Dec 04, 2019 9:34 am

Looking at your log, it gets to writing and the PCM refuses.
[02:56:17:110] Writing...
[02:56:17:141] Sending payload with offset 0x0000, start address 0x008000, length 0x0080.
[02:56:17:157] TX: STPX H:6D10F0, R:1, L:137
[02:56:17:188] TX: 360000800080004D34000200BFEC3541424AFC3132353737383435000000000000000000000000000600000000000000FF0000000000FF0000000000FF0000000000FF0000000000FF0000000000FF00000000000000000000000000FF0000000000FF0000000000FF0000000000FF0000000000FF0000000000FF00000000000000000000000012CD
[02:56:17:345] RX: 6D F0 10 7F 36 00 EE
Image

User avatar
Posts: 219
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Postby NSFW » Wed Dec 04, 2019 12:15 pm

I'm guessing the code that the kernel used to write to the 512k Intel chips doesn't work on the 1mb chips. We'll have to compare the data sheets to see what's different.
Please don't PM me with questions about tuning or flashing - start a thread instead. Thanks!

Posts: 1
Joined: Tue Dec 03, 2019 4:26 am

Re: PCM Hammer - new ls1 flash tool

Postby TE27Levin » Wed Dec 04, 2019 1:09 pm

I am also having an issue verifying the read with my P59, i'm thinking its my autel J2534 device causing the issues though. I had to put the pcm into recovery mode to get it this far.. See attachment That is a different error than my original. Still pretty cool getting this far with it.
Attachments
debugerr2.txt
(55.87 KiB) Downloaded 5 times

Posts: 185
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Postby Gampy » Wed Dec 04, 2019 2:42 pm

I don't know if it helps, confuses or what but I've looked at the code from 10 of these P01/P59 OS's and the Intel Flash code has been the same in all.


Also, finally got a chance to look at the latest kernel code ...

In flash-amd.c line 59, I suspect this FlashLock(); should be replaced.
Code: Select all
         if (!testWrite)
         {
            *address = 0xF0F0;
            *address = 0xF0F0;
-            FlashLock();
+            SIM_CSOR0 = 0x1060;
         }


And a trivial unused int, in common.c line 182,
Code: Select all
-   int stopUsing = 0;

Previous

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: No registered users and 3 guests