Page 30 of 97
Re: PCM Hammer - new ls1 flash tool
Posted: Sat Feb 16, 2019 1:11 pm
by NSFW
Speedy wrote:antus wrote:Can you post up the bin? It looks like it has bad checksums....
Bin "My Xtra P01 PCM" is from the junkyard PCM I am using for all bench harness write tests. The other bin "My 2000 Silverado" comes from the PCM removed from my vehicle, for a test read/comparison.
Both bin files are STOCK. Both are from PCMs sharing the same Serv#09354896 and 9381344 O/S (commonly used in 2000 model year).
It turns out that the checksums are actually fine - I revised the way the app verifies checksums (in order to support P59 PCMs) and antus wondered whether the new approach would fix the issue that you ran into.... so I downloaded your files, and the new code says all checksums are valid.
It's mixed in with some half-baked support for P59 right now, but when the next version is released I think you'll find that writes and compares work with your OS.
Re: PCM Hammer - new ls1 flash tool
Posted: Sat Feb 16, 2019 5:47 pm
by NSFW
I have more code to write before I can do a P59 flash yet, but the quick-compare feature works. With the flash chip being twice as big, it's even less quick than the name would imply though.
Code: Select all
[11:40:57:748] Validating 1024k file.
[11:40:57:763] Start End Stored Expected Verdict Segment Name
[11:40:57:784] 0 FFFFD 17744 4550 Good Operating system
[11:40:57:797] 8002 162CF 49422 C10E Good Engine calibration
[11:40:57:814] 162D2 195FF 4726 1276 Good Engine diagnostics.
[11:40:57:830] 19602 1D8AF 12312 3018 Good Transmission calibration
[11:40:57:848] 1D8B2 1E1AF 5722 165A Good Transmission diagnostics
[11:40:57:864] 1E1B2 1F6BF 35129 8939 Good Fuel system
[11:40:57:880] 1F6C2 1FEAF 8306 2072 Good System
[11:40:57:893] 1FEB2 1FFDF 1492 05D4 Good Speedometer
[11:40:57:908] Requesting operating system ID...
[11:40:58:030] PCM and file are both operating system 12592425
[11:40:58:340] Unlock succeeded.
[11:40:58:413] Attempting switch to VPW 4x
[11:40:58:501] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[11:40:59:358] Uploading kernel to PCM.
[11:41:01:032] Kernel upload 16% complete.
[11:41:02:017] Kernel upload 30% complete.
[11:41:02:691] Kernel upload 44% complete.
[11:41:03:386] Kernel upload 58% complete.
[11:41:04:328] Kernel upload 72% complete.
[11:41:05:018] Kernel upload 86% complete.
[11:41:05:705] Kernel upload 100% complete.
[11:41:05:977] Kernel Version: 010200BB
[11:41:05:990] Kernel uploaded to PCM succesfully.
[11:41:06:296] Flash memory type: 00012258
[11:41:06:317] Flash memory ID: 00012258
[11:41:06:330] Flash memory manufactuer: Amd
[11:41:06:345] Flash memory type: Am29F800B 1Mbyte
[11:41:06:366] Calculating CRCs from file...
[11:41:06:385] Requesting CRCs from PCM...
[11:41:49:182] Range File CRC PCM CRC Verdict Purpose
[11:41:51:477] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[11:41:53:788] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[11:41:56:110] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[11:41:58:425] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[11:42:00:733] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[11:42:03:053] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[11:42:05:372] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[11:42:07:673] 080000-08FFFF 0D3B237A 0D3B237A Same OperatingSystem
[11:42:10:001] 070000-07FFFF 60878AA3 60878AA3 Same OperatingSystem
[11:42:12:336] 060000-06FFFF 3E9A05C9 3E9A05C9 Same OperatingSystem
[11:42:14:686] 050000-05FFFF 5BF26857 5BF26857 Same OperatingSystem
[11:42:17:018] 040000-04FFFF D664E8A4 D664E8A4 Same OperatingSystem
[11:42:19:336] 030000-03FFFF 2E20FF6E 2E20FF6E Same OperatingSystem
[11:42:21:659] 020000-02FFFF EEE5661C EEE5661C Same OperatingSystem
[11:42:23:983] 010000-01FFFF 4D3435D5 4D3435D5 Same Calibration
[11:42:26:312] 008000-00FFFF 0764289B 0764289B Same Calibration
[11:42:28:642] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[11:42:30:947] 004000-005FFF B7FF199D B7FF199D Same Parameter
[11:42:33:256] 000000-003FFF 980E70A7 980E70A7 Same Boot
[11:42:33:545] All ranges are identical.
[11:42:34:228] Clearing trouble codes.
[11:42:35:391] Elapsed time 00:01:37.0351424
The tables line up better in the actual UI.
Re: PCM Hammer - new ls1 flash tool
Posted: Sat Feb 16, 2019 5:54 pm
by antus
Excellent work - so many more blocks in the AMD chips than the Intel!
Re: PCM Hammer - new ls1 flash tool
Posted: Sat Feb 16, 2019 8:58 pm
by Gampy
Sweet ... Awesome job!
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 5:47 am
by flyn-brian
Could some body help me? I have a OBDLink sx. and I get errors. Ive tried several different drivers. I also have HPTuners VCI. Is it possible to get the source code and complile it to work with other pcm drivers I also have a screaming eagle race tuner for my VRod which also uses a delphi pcm
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 6:26 am
by NSFW
It's hard to help when you've given us so little information about what you were doing when things went wrong.
Which features work, and which features fail?
When something fails, how far does it get before it fails?
The app source code is availalble on github,
http://pcmhammer.org is a shortcut to the project there.
Kernel source is in a private repo for reasons I won't get into, but it will be opened up eventually.
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 7:02 am
by flyn-brian
- Hammer read fail error.jpg (187.1 KiB) Viewed 4905 times
It seems to recognize the programmer and load the kernel. But it faults out when trying to read the bin. I'm using both my 05 Avalanche and my homemade bench harness on 3 different p59 pcm's. I alternately tried several different drivers for the OBDLink sx
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 7:21 am
by Gampy
flyn-brian wrote:Could some body help me? I have a OBDLink sx. and I get errors. Ive tried several different drivers. I also have HPTuners VCI. Is it possible to get the source code and complile it to work with other pcm drivers I also have a screaming eagle race tuner for my VRod which also uses a delphi pcm
It would be helpful to provide the full text of the debug log (copy and paste to notepad, attach the notepad file (or paste directly into code tags here)) so where it fails can be seen, not just that it failed.
Please either Attach it as an attachment or put 'code' tags around it ...
[edit]
Your second post/image shows where it fails ... thank you!
[/edit]
Com11 tells me it would also be beneficial to your computers health to clean up the com ports.
To do that, Open a Administrator Command Prompt and type the following:
Code: Select all
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
When device manager opens:
Select: View
Select: Show hidden devices
Expand: Ports (COM & LPT)
Remove all COM ports ...
-Enjoy
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 7:40 am
by Gampy
I've lost track of what reads and what does not with the current release.
That unit appears to be an AMD chipped unit, isn't that one that the current release does not read?
Backtracking from the hardware number, it appears to be one of the following Service Numbers:
12589463
12602802
-Enjoy
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Feb 18, 2019 9:00 am
by antus
I wouldnt rule out vehicle or bench problems yet. My '9463 works. A full debug log would be interesting, there may be something logged earlier with more clues.