Re: PCM Hammer - new ls1 flash tool
Posted: Sun Dec 22, 2019 4:38 pm
Yep do a read in recovery mode and you'll have a backup. Be careful with the clone feature, you can trash your license. If this happens we cant help you out.
pcmhacking.net
Electronic Fuel Injection - Developement & Tuning
https://pcmhacking.net/forums/
PCM Hammer P01 and P59 flash tool v015
Page 61 of 97
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Dec 23, 2019 1:18 pm
Thanks again.
Re: PCM Hammer - new ls1 flash tool
Posted: Tue Dec 24, 2019 11:26 pm
To do a vehicle change with a bin of the same OS, only the calibration needs to be written or does the parameter block also need to be written??
Changing from v6 to v8 bins of the same OS.
Changing from v6 to v8 bins of the same OS.
Re: PCM Hammer - new ls1 flash tool
Posted: Thu Dec 26, 2019 8:48 pm
Just calibration and update the vin with the block api (write vin button in pcm hammer) and thats how most tools that allow you to set vin work. The block api maps the same number to the correct address against all GM OS.
Re: PCM Hammer - new ls1 flash tool
Posted: Fri Dec 27, 2019 7:38 am
Thank you ...antus wrote:Just calibration and update the vin with the block api (write vin button in pcm hammer) and thats how most tools that allow you to set vin work. The block api maps the same number to the correct address against all GM OS.
My 411 got a good scrubbing then cause I have cloned it multiple times now with the same OS from a different vehicle.
Re: PCM Hammer - new ls1 flash tool
Posted: Sun Dec 29, 2019 5:38 am
THEFERMANATOR wrote:I ordered a OBDlink SX cable off of amazon so I could start reading .bin's, and ran into an issue. This is on a known good, RUNNING PCM out of my 99 TAHOE that received an 0411(P01) swap. I have flashed it several times now with EFILIVE, but I want to read it out to get the .bin file to look into some hex file changes in it, and I cannot read it. I know it's not the cable,software, or my install because I was able to successfully read the tune out of my spare 0411(identical PCM) that I flashed 2 days ago via TIS2000 using SPS and my TECH2. Here's what it display's when I try to read it.
[01:47:03:983] PCM Hammer 005
[01:47:05:029] Voltage: 13.9V
[01:47:05:044] Elm ID: ELM327 v1.3a
[01:47:05:075] ScanTool device ID: STN1130 v4.0.1
[01:47:09:755] VIN: 1GNDT13W91K218983
[01:47:09:865] OS ID: 12212156
[01:47:09:974] Calibration ID: 4294967295
[01:47:10:067] Hardware ID: 9386530
[01:47:10:333] Serial Number: 1EB18Z821082
[01:47:10:426] Broad Cast Code:
[01:47:10:535] MEC: 0
[01:47:31:221] Will save to C:\Users\Ferman\Documents\TUNERPRO files\.bin files\tahoe file.bin
[01:47:31:237] Querying operating system of current PCM.
[01:47:31:346] OSID: 12212156
[01:47:31:705] Unknown unlock code 0x53
[01:47:35:761] Unable to process unlock response.
[01:47:35:761] Unlock was not successful.
Did you ever figure this out? I got this same error today for the first time. My PCM still works fine and I drove with it. And it was a stock bin that i edited with tunerpro and flashed. I was going back in to remove egr code i left on and got this error. My debug log is below. I've tried a few different version of Pcmhammer too.
Code: Select all
[01:32:51:687] PCM Hammer 008
[01:32:51:687] ElmDevice initialization starting.
[01:32:51:718] TX:
[01:32:51:718] TX: AT Z
[01:32:52:589] ELM327 v1.3a
[01:32:52:589] TX: AT E0
[01:32:52:605] AT E0 OK
[01:32:52:605] TX: AT S0
[01:32:52:621] OK
[01:32:52:621] TX: AT RV
[01:32:52:636] Voltage: 11.5V
[01:32:52:636] TX: AT I
[01:32:52:652] Elm ID: ELM327 v1.3a
[01:32:52:668] Initializing PcmHacking.AllProDeviceImplementation
[01:32:52:668] TX: AT #1
[01:32:52:668] This is not an AllPro device.
[01:32:52:668] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[01:32:52:668] TX: ST I
[01:32:52:683] ScanTool device ID: STN1130 v4.5.1
[01:32:52:683] TX: AT AL
[01:32:52:699] OK
[01:32:52:699] TX: AT SP2
[01:32:52:714] OK
[01:32:52:714] TX: AT DP
[01:32:52:730] SAE J1850 VPW
[01:32:52:730] TX: AT AR
[01:32:52:746] OK
[01:32:52:746] TX: AT AT0
[01:32:52:761] OK
[01:32:52:761] TX: AT SR F0
[01:32:52:777] OK
[01:32:52:777] TX: AT H1
[01:32:52:793] OK
[01:32:52:793] TX: AT ST 20
[01:32:52:808] OK
[01:33:09:911] D:\Downloads\2002 Silverado 4X4 60 4L80 flash.bin
[01:33:09:927] Validating 512k file.
[01:33:09:927] Start End Stored Needed Verdict Segment Name
[01:33:09:943] 00000 7FFFD EFCC EFCC Good Operating system
[01:33:09:958] 08002 13FFF E3C8 E3C8 Good Engine calibration
[01:33:09:958] 14002 16DFF A637 A637 Good Engine diagnostics.
[01:33:09:958] 16E02 1BDFF 750B 750B Good Transmission calibration
[01:33:09:974] 1BE02 1C7FF EDDD EDDD Good Transmission diagnostics
[01:33:09:974] 1C802 1E51F 9672 9672 Good Fuel system
[01:33:09:990] 1E522 1EE9F 69AC 69AC Good System
[01:33:09:990] 1EEA2 1EF9F 46AD 46AD Good Speedometer
[01:33:10:005] Requesting operating system ID...
[01:33:10:021] Setting timeout for ReadProperty, 47 ms.
[01:33:10:021] TX: AT ST 0B
[01:33:10:036] OK
[01:33:10:036] Setting timeout for ReadProperty, 47 ms.
[01:33:10:036] TX: AT ST 0B
[01:33:10:052] OK
[01:33:10:068] TX: STPX H:6C10F0, R:1, L:2
[01:33:10:083] TX: 3C0A
[01:33:10:208] RX: 6C F0 10 7C 0A 00 BA 57 BC
[01:33:10:208] PCM and file are both operating system 12212156
[01:33:10:240] Suppressing VPW chatter.
[01:33:10:240] TX: STPX H:6CFEF0, R:1, L:2
[01:33:10:240] TX: 2800
[01:33:10:255] RX: 6C F0 29 68 00
[01:33:10:271] Sending 'test device present' notification.
[01:33:10:271] TX: AT SH 8C FE F0
[01:33:10:271] Set header response: OK
[01:33:10:271] TX: 3F
[01:33:10:349] Setting timeout for ReadProperty, 47 ms.
[01:33:10:349] TX: AT ST 0B
[01:33:10:349] OK
[01:33:10:349] Sending seed request.
[01:33:10:365] TX: STPX H:6C10F0, R:1, L:2
[01:33:10:365] TX: 2701
[01:33:10:400] RX: 6C F0 10 67 01 75 FF
[01:33:10:400] Parsing seed value.
[01:33:10:415] Sending unlock request (FF75, 93D8)
[01:33:10:415] TX: STPX H:6C10F0, R:1, L:4
[01:33:10:415] TX: 270293D8
[01:33:10:447] RX: 6C F0 10 67 02 35
[01:33:10:462] Unknown unlock code 0x53
[01:33:10:790] Timeout during receive.
[01:33:10:790] No response to unlock request. Attempt #2
[01:33:11:094] Timeout during receive.
[01:33:11:094] No response to unlock request. Attempt #3
[01:33:11:406] Timeout during receive.
[01:33:11:406] No response to unlock request. Attempt #4
[01:33:11:715] Timeout during receive.
[01:33:11:715] No response to unlock request. Attempt #5
[01:33:12:028] Timeout during receive.
[01:33:12:028] No response to unlock request. Attempt #6
[01:33:12:340] Timeout during receive.
[01:33:12:340] No response to unlock request. Attempt #7
[01:33:12:653] Timeout during receive.
[01:33:12:653] No response to unlock request. Attempt #8
[01:33:12:952] Timeout during receive.
[01:33:12:952] No response to unlock request. Attempt #9
[01:33:13:264] Timeout during receive.
[01:33:13:264] No response to unlock request. Attempt #10
[01:33:13:576] Timeout during receive.
[01:33:13:576] No response to unlock request. Attempt #11
[01:33:13:889] Timeout during receive.
[01:33:13:889] No response to unlock request. Attempt #12
[01:33:14:201] Timeout during receive.
[01:33:14:201] No response to unlock request. Attempt #13
[01:33:14:514] Timeout during receive.
[01:33:14:514] No response to unlock request. Attempt #14
[01:33:14:514] Unable to process unlock response.
[01:33:14:530] Unlock was not successful.
Re: PCM Hammer - new ls1 flash tool
Posted: Sun Dec 29, 2019 5:48 am
notime2d8 wrote:THEFERMANATOR wrote:I ordered a OBDlink SX cable off of amazon so I could start reading .bin's, and ran into an issue. This is on a known good, RUNNING PCM out of my 99 TAHOE that received an 0411(P01) swap. I have flashed it several times now with EFILIVE, but I want to read it out to get the .bin file to look into some hex file changes in it, and I cannot read it. I know it's not the cable,software, or my install because I was able to successfully read the tune out of my spare 0411(identical PCM) that I flashed 2 days ago via TIS2000 using SPS and my TECH2. Here's what it display's when I try to read it.
[01:47:03:983] PCM Hammer 005
[01:47:05:029] Voltage: 13.9V
[01:47:05:044] Elm ID: ELM327 v1.3a
[01:47:05:075] ScanTool device ID: STN1130 v4.0.1
[01:47:09:755] VIN: 1GNDT13W91K218983
[01:47:09:865] OS ID: 12212156
[01:47:09:974] Calibration ID: 4294967295
[01:47:10:067] Hardware ID: 9386530
[01:47:10:333] Serial Number: 1EB18Z821082
[01:47:10:426] Broad Cast Code:
[01:47:10:535] MEC: 0
[01:47:31:221] Will save to C:\Users\Ferman\Documents\TUNERPRO files\.bin files\tahoe file.bin
[01:47:31:237] Querying operating system of current PCM.
[01:47:31:346] OSID: 12212156
[01:47:31:705] Unknown unlock code 0x53
[01:47:35:761] Unable to process unlock response.
[01:47:35:761] Unlock was not successful.
Did you ever figure this out? I got this same error today for the first time. My PCM still works fine and I drove with it. And it was a stock bin that i edited with tunerpro and flashed. I was going back in to remove egr code i left on and got this error. My debug log is below. I've tried a few different version of Pcmhammer too.
Code: Select all
[01:32:51:687] PCM Hammer 008 [01:32:51:687] ElmDevice initialization starting. [01:32:51:718] TX: [01:32:51:718] TX: AT Z [01:32:52:589] ELM327 v1.3a [01:32:52:589] TX: AT E0 [01:32:52:605] AT E0 OK [01:32:52:605] TX: AT S0 [01:32:52:621] OK [01:32:52:621] TX: AT RV [01:32:52:636] Voltage: 11.5V [01:32:52:636] TX: AT I [01:32:52:652] Elm ID: ELM327 v1.3a [01:32:52:668] Initializing PcmHacking.AllProDeviceImplementation [01:32:52:668] TX: AT #1 [01:32:52:668] This is not an AllPro device. [01:32:52:668] Determining whether PcmHacking.ScanToolDeviceImplementation is connected. [01:32:52:668] TX: ST I [01:32:52:683] ScanTool device ID: STN1130 v4.5.1 [01:32:52:683] TX: AT AL [01:32:52:699] OK [01:32:52:699] TX: AT SP2 [01:32:52:714] OK [01:32:52:714] TX: AT DP [01:32:52:730] SAE J1850 VPW [01:32:52:730] TX: AT AR [01:32:52:746] OK [01:32:52:746] TX: AT AT0 [01:32:52:761] OK [01:32:52:761] TX: AT SR F0 [01:32:52:777] OK [01:32:52:777] TX: AT H1 [01:32:52:793] OK [01:32:52:793] TX: AT ST 20 [01:32:52:808] OK [01:33:09:911] D:\Downloads\2002 Silverado 4X4 60 4L80 flash.bin [01:33:09:927] Validating 512k file. [01:33:09:927] Start End Stored Needed Verdict Segment Name [01:33:09:943] 00000 7FFFD EFCC EFCC Good Operating system [01:33:09:958] 08002 13FFF E3C8 E3C8 Good Engine calibration [01:33:09:958] 14002 16DFF A637 A637 Good Engine diagnostics. [01:33:09:958] 16E02 1BDFF 750B 750B Good Transmission calibration [01:33:09:974] 1BE02 1C7FF EDDD EDDD Good Transmission diagnostics [01:33:09:974] 1C802 1E51F 9672 9672 Good Fuel system [01:33:09:990] 1E522 1EE9F 69AC 69AC Good System [01:33:09:990] 1EEA2 1EF9F 46AD 46AD Good Speedometer [01:33:10:005] Requesting operating system ID... [01:33:10:021] Setting timeout for ReadProperty, 47 ms. [01:33:10:021] TX: AT ST 0B [01:33:10:036] OK [01:33:10:036] Setting timeout for ReadProperty, 47 ms. [01:33:10:036] TX: AT ST 0B [01:33:10:052] OK [01:33:10:068] TX: STPX H:6C10F0, R:1, L:2 [01:33:10:083] TX: 3C0A [01:33:10:208] RX: 6C F0 10 7C 0A 00 BA 57 BC [01:33:10:208] PCM and file are both operating system 12212156 [01:33:10:240] Suppressing VPW chatter. [01:33:10:240] TX: STPX H:6CFEF0, R:1, L:2 [01:33:10:240] TX: 2800 [01:33:10:255] RX: 6C F0 29 68 00 [01:33:10:271] Sending 'test device present' notification. [01:33:10:271] TX: AT SH 8C FE F0 [01:33:10:271] Set header response: OK [01:33:10:271] TX: 3F [01:33:10:349] Setting timeout for ReadProperty, 47 ms. [01:33:10:349] TX: AT ST 0B [01:33:10:349] OK [01:33:10:349] Sending seed request. [01:33:10:365] TX: STPX H:6C10F0, R:1, L:2 [01:33:10:365] TX: 2701 [01:33:10:400] RX: 6C F0 10 67 01 75 FF [01:33:10:400] Parsing seed value. [01:33:10:415] Sending unlock request (FF75, 93D8) [01:33:10:415] TX: STPX H:6C10F0, R:1, L:4 [01:33:10:415] TX: 270293D8 [01:33:10:447] RX: 6C F0 10 67 02 35 [01:33:10:462] Unknown unlock code 0x53 [01:33:10:790] Timeout during receive. [01:33:10:790] No response to unlock request. Attempt #2 [01:33:11:094] Timeout during receive. [01:33:11:094] No response to unlock request. Attempt #3 [01:33:11:406] Timeout during receive. [01:33:11:406] No response to unlock request. Attempt #4 [01:33:11:715] Timeout during receive. [01:33:11:715] No response to unlock request. Attempt #5 [01:33:12:028] Timeout during receive. [01:33:12:028] No response to unlock request. Attempt #6 [01:33:12:340] Timeout during receive. [01:33:12:340] No response to unlock request. Attempt #7 [01:33:12:653] Timeout during receive. [01:33:12:653] No response to unlock request. Attempt #8 [01:33:12:952] Timeout during receive. [01:33:12:952] No response to unlock request. Attempt #9 [01:33:13:264] Timeout during receive. [01:33:13:264] No response to unlock request. Attempt #10 [01:33:13:576] Timeout during receive. [01:33:13:576] No response to unlock request. Attempt #11 [01:33:13:889] Timeout during receive. [01:33:13:889] No response to unlock request. Attempt #12 [01:33:14:201] Timeout during receive. [01:33:14:201] No response to unlock request. Attempt #13 [01:33:14:514] Timeout during receive. [01:33:14:514] No response to unlock request. Attempt #14 [01:33:14:514] Unable to process unlock response. [01:33:14:530] Unlock was not successful.
lol, I just read a few pages back....guess i didn't use a stock bin file. I'm off now to figure out how to get into recovery mode. It's weird that it took a while before i started getting this unlock code error. I've flashed it a few times before. I didn't get this error until after i took it out for a long drive and came back to remove a egr code.
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Dec 30, 2019 5:10 pm
What program software you guys using for pcm hammer and writing kernels. I got visual basic but its hurting my head sifting through all the code to bounce around.
Is there a software that is more visual so I can follow paths easier.
Also what serial port monitor do you use, I flashed my pcm using winflash and captured all the data, but monitor I used has read and write in 2 seperate windows so its a pain to follow.
I have the current programs write kernel saved. I copied the hex and saved in hxd as a bin file, anyway to load it to ida or some other software to see how it works. it doesn't change serial or other main parameter blocks like your stuff does for cloning.
This is all for the blue/clear v6 pcms
Does anyone have a data sheet or can point me in the direction of the mode lists, I found them before but forgot to save or book mark them, looking for mode 36 structure mainly but full list wound be cool to have.
Is there a software that is more visual so I can follow paths easier.
Also what serial port monitor do you use, I flashed my pcm using winflash and captured all the data, but monitor I used has read and write in 2 seperate windows so its a pain to follow.
I have the current programs write kernel saved. I copied the hex and saved in hxd as a bin file, anyway to load it to ida or some other software to see how it works. it doesn't change serial or other main parameter blocks like your stuff does for cloning.
This is all for the blue/clear v6 pcms
Does anyone have a data sheet or can point me in the direction of the mode lists, I found them before but forgot to save or book mark them, looking for mode 36 structure mainly but full list wound be cool to have.
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Dec 30, 2019 5:29 pm
I've been using Visual Studio 2017 Community Edition to do all of the Windows programming. It's in C#. The "Solution Explorer" window will show you a tree of files, which helps with navigating the code. You can also press F12 to have jump to the origin of whatever the cursor is on - for example if you put the cursor on the name of a function, it will jump to the implementation of that function. I use that a lot.
I'm using an Arduino to monitor the serial port, the Arduino code for that is in the same repository as the apps and the kernel. (That was written by a user here named Thaniel if I remember right.) There is a way to do monitoring with ScanTool interfaces but I haven't used them for that very much... if I remember right, you can use a terminal program, type "ATM" and the Scantool will log all of the data that it seems. That's basically what the Arduino does too, but all you have to do is open the serial port monitor window in the Arduino app, no need to type anything.
The kernel code is compiled with GCC, which runs via the command line. There are links to get GCC in the ReadMe file in this directory:
https://github.com/LegacyNsfw/PcmHacks/ ... op/Kernels
There's no need to use IDA to reverse engineer the kernel, the source code is on github and it's easier to read than assembly code.
It was written almost entirely in C, with a tiny bit of inline assembly here and there.
There's also a batch file (build.bat) that does everything needed to build the kernel. There's a makefile as well, which Antus uses, but I don't have 'make' installed on my desktop or laptop.
This page has been my main reference for OBD2 stuff:
https://www.fastfieros.com/tech/vpw_com ... otocol.htm
For Mode 36, look at the CreateBlockMessage in PcmLibrary\Messages\Protocol.ReadWrite.cs file. That's the code that builds the mode-36 messages that the app sends.
I'm using an Arduino to monitor the serial port, the Arduino code for that is in the same repository as the apps and the kernel. (That was written by a user here named Thaniel if I remember right.) There is a way to do monitoring with ScanTool interfaces but I haven't used them for that very much... if I remember right, you can use a terminal program, type "ATM" and the Scantool will log all of the data that it seems. That's basically what the Arduino does too, but all you have to do is open the serial port monitor window in the Arduino app, no need to type anything.
The kernel code is compiled with GCC, which runs via the command line. There are links to get GCC in the ReadMe file in this directory:
https://github.com/LegacyNsfw/PcmHacks/ ... op/Kernels
There's no need to use IDA to reverse engineer the kernel, the source code is on github and it's easier to read than assembly code.
It was written almost entirely in C, with a tiny bit of inline assembly here and there.There's also a batch file (build.bat) that does everything needed to build the kernel. There's a makefile as well, which Antus uses, but I don't have 'make' installed on my desktop or laptop.
This page has been my main reference for OBD2 stuff:
https://www.fastfieros.com/tech/vpw_com ... otocol.htm
For Mode 36, look at the CreateBlockMessage in PcmLibrary\Messages\Protocol.ReadWrite.cs file. That's the code that builds the mode-36 messages that the app sends.
Re: PCM Hammer - new ls1 flash tool
Posted: Mon Dec 30, 2019 5:36 pm
thanks, I was mainly asking about the kernel stuff so I could try and look at what my current v6 flashing software is doing, It will clone pcm perfectly but doesnt change serial. I would like to get the cloning, read, write setup for you guys as much as I can.