Page 74 of 97

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 10, 2020 4:35 am
by Gampy
MudDuck514 wrote:Gampy, that is exactly the reason why when a friend offered to give me a working Simpson 260, I jumped at the offer!
That's what I was raised on, my dad had a couple ... I hope to wind up with them if the estate ever gets settled.

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 3:17 pm
by Vampyre
Is the code to differentiate between clone, Cal and cal os write program side or kernel side. and what file is it located in.

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 3:26 pm
by antus
program side, they cover different chip segments.

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 4:52 pm
by Gampy
Vampyre wrote:Is the code to differentiate between clone, Cal and cal os write program side or kernel side. and what file is it located in.
All the buttons are handled in MainForm.cs.
For example, button: Read Full Contents
Is: readFullContentsButton_Click(...)

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 5:23 pm
by Vampyre
got that part, tried to follow the code but cant find where it seperates the different segment calls. would be much easier with a tree view i believe

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 6:12 pm
by antus
Its one level back from https://github.com/LegacyNsfw/PcmHacks/ ... ter.cs#L14 but it does the thing based on whats requested.

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 6:48 pm
by Vampyre
yeah im looking for where its requested, would it be in the button calls. man i suck at this

edit

found it, yes it was in mainform buttons

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 7:38 pm
by jfitzy
Hi everyone, first reply to a thread here so go easy on me if this has been covered but I have spent some time reading through some topics and as of so far have not been able to rectify my issue. Im having trouble pulling the .bin file from my 0411. OS 1273003. I will attach the debug files, im having the errors "Ïnterface does not support VPW x4" followed by "Permission to upload kernal was denied".

I have tried several PCM resets, disconnecting battery, and countless ign cycles to no avail. Always having same problem unfortunately.

Anyone shed some light on this? If ive missed any important info please let me know.

Results:
[08:23:23:769] PCM Hammer 011
[08:23:24:796] Voltage: 12.2V
[08:23:24:828] Elm ID: ELM327 v1.3a
[08:23:24:890] ScanTool device ID: STN1130 v4.0.1
[08:23:29:016] VIN: 6H8VXK69F2L776239
[08:23:29:094] OS ID: 1273003
[08:23:29:172] Calibration ID: 92108769
[08:23:29:266] Hardware ID: 9386530
[08:23:29:469] Serial Number: 1EB1UE0N1215
[08:23:29:547] Broad Cast Code: DFNN
[08:23:29:625] MEC: 0
[08:23:36:017] Will save to C:\Users\jwpfi\OneDrive\Documents\TunerPro Files\Bins\1.bin
[08:23:46:187] Querying operating system of current PCM.
[08:23:46:265] OSID: 1273003
[08:23:46:500] PCM is already unlocked
[08:23:46:500] Unlock succeeded.
[08:23:46:578] This interface does not support VPW 4x
[08:23:46:671] Uploading kernel to PCM.
[08:23:46:781] Permission to upload kernel was denied.
[08:23:46:796] This can usually be solved by cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[08:23:46:812] Failed to upload kernel to PCM
[08:23:47:015] Clearing trouble codes.
[08:23:47:984] Elapsed time 00:00:01.4689132
[08:23:48:000] Read failed, Error


Debug Log:
[08:23:23:769] PCM Hammer 011
[08:23:23:775] ElmDevice initialization starting.
[08:23:23:906] TX:
[08:23:23:921] TX: AT Z
[08:23:24:750] ELM327 v1.3a
[08:23:24:750] TX: AT E0
[08:23:24:765] AT E0 OK
[08:23:24:765] TX: AT S0
[08:23:24:781] OK
[08:23:24:781] TX: AT RV
[08:23:24:796] Voltage: 12.2V
[08:23:24:796] TX: AT I
[08:23:24:828] Elm ID: ELM327 v1.3a
[08:23:24:843] Initializing PcmHacking.AllProDeviceImplementation
[08:23:24:843] TX: AT #1
[08:23:24:859] This is not an AllPro device.
[08:23:24:859] Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[08:23:24:875] TX: ST I
[08:23:24:890] ScanTool device ID: STN1130 v4.0.1
[08:23:24:906] TX: AT ST FF
[08:23:24:921] OK
[08:23:24:937] TX: AT AL
[08:23:24:937] OK
[08:23:24:953] TX: AT SP2
[08:23:24:953] OK
[08:23:24:968] TX: AT DP
[08:23:24:984] SAE J1850 VPW
[08:23:24:999] TX: AT AR
[08:23:25:015] OK
[08:23:25:031] TX: AT AT0
[08:23:25:046] OK
[08:23:25:062] TX: AT SR F0
[08:23:25:078] OK
[08:23:25:093] TX: AT H1
[08:23:25:109] OK
[08:23:25:125] TX: AT ST 20
[08:23:25:156] OK
[08:23:28:785] TX: STPX H:6C10F0, R:1, D:3C01
[08:23:28:887] RX: 6C F0 10 7C 01 00 36 48 38 56 58
[08:23:28:891] TX: STPX H:6C10F0, R:1, D:3C02
[08:23:28:938] RX: 6C F0 10 7C 02 4B 36 39 46 32 4C
[08:23:28:953] TX: STPX H:6C10F0, R:1, D:3C03
[08:23:29:000] RX: 6C F0 10 7C 03 37 37 36 32 33 39
[08:23:29:016] VIN: 6H8VXK69F2L776239
[08:23:29:031] TX: STPX H:6C10F0, R:1, D:3C0A
[08:23:29:094] RX: 6C F0 10 7C 0A 00 13 6C AB
[08:23:29:094] OS ID: 1273003
[08:23:29:110] TX: STPX H:6C10F0, R:1, D:3C08
[08:23:29:172] RX: 6C F0 10 7C 08 05 7D 77 E1
[08:23:29:172] Calibration ID: 92108769
[08:23:29:188] TX: STPX H:6C10F0, R:1, D:3C04
[08:23:29:250] RX: 6C F0 10 7C 04 00 8F 3A 22
[08:23:29:266] Hardware ID: 9386530
[08:23:29:282] TX: STPX H:6C10F0, R:1, D:3C05
[08:23:29:329] RX: 6C F0 10 7C 05 31 45 42 31
[08:23:29:344] TX: STPX H:6C10F0, R:1, D:3C06
[08:23:29:391] RX: 6C F0 10 7C 06 55 45 30 4E
[08:23:29:407] TX: STPX H:6C10F0, R:1, D:3C07
[08:23:29:454] RX: 6C F0 10 7C 07 31 32 31 35
[08:23:29:469] Serial Number: 1EB1UE0N1215
[08:23:29:500] TX: STPX H:6C10F0, R:1, D:3C14
[08:23:29:532] RX: 6C F0 10 7C 14 44 46 4E 4E
[08:23:29:547] Broad Cast Code: DFNN
[08:23:29:563] TX: STPX H:6C10F0, R:1, D:3CA0
[08:23:29:610] RX: 6C F0 10 7C A0 00
[08:23:29:625] MEC: 0
[08:23:36:017] Will save to C:\Users\jwpfi\OneDrive\Documents\TunerPro Files\Bins\1.bin
[08:23:46:187] Querying operating system of current PCM.
[08:23:46:202] TX: STPX H:6C10F0, R:1, D:3C0A
[08:23:46:265] RX: 6C F0 10 7C 0A 00 13 6C AB
[08:23:46:265] OSID: 1273003
[08:23:46:281] Suppressing VPW chatter.
[08:23:46:296] TX: STPX H:6CFEF0, R:1, D:2800
[08:23:46:359] RX: 6C F0 10 68 00
[08:23:46:359] Sending 'test device present' notification.
[08:23:46:375] TX: STPX H:8CFEF0, R:0, D:3F
[08:23:46:406] Empty response to STPX with data. That's OK
[08:23:46:406] Sending seed request.
[08:23:46:421] TX: STPX H:6C10F0, R:1, D:2701
[08:23:46:484] RX: 6C F0 10 67 01 37 3A
[08:23:46:500] PCM is already unlocked
[08:23:46:500] Unlock succeeded.
[08:23:46:515] Sending 'test device present' notification.
[08:23:46:531] TX: STPX H:8CFEF0, R:0, D:3F
[08:23:46:562] Empty response to STPX with data. That's OK
[08:23:46:578] This interface does not support VPW 4x
[08:23:46:593] Sending 'test device present' notification.
[08:23:46:609] TX: STPX H:8CFEF0, R:0, D:3F
[08:23:46:640] Empty response to STPX with data. That's OK
[08:23:46:656] Loaded C:\Users\jwpfi\Desktop\PcmHammer011\kernel.bin
[08:23:46:671] Uploading kernel to PCM.
[08:23:46:671] Sending upload request for kernel size 8212, loadaddress FF8000
[08:23:46:687] TX: STPX H:6C10F0, R:1, D:34001000FF8000
[08:23:46:750] RX: 6C F0 10 7F 34 00 10 00 FF 80 33
[08:23:46:765] Found response, Refused
[08:23:46:781] Permission to upload kernel was denied.
[08:23:46:796] This can usually be solved by cutting power to the PCM, restoring power, waiting ten seconds, and trying again.
[08:23:46:812] Failed to upload kernel to PCM
[08:23:46:828] Halting the kernel.
[08:23:46:828] TX: STPX H:6C10F0, R:1, D:20
[08:23:47:015] Clearing trouble codes.
[08:23:47:015] TX: STPX H:686AF0, R:1, D:04
[08:23:47:187] TX: STPX H:686AF0, R:1, D:04
[08:23:47:859] TX: STPX H:8CFEF0, R:1, D:14
[08:23:47:906] RX: 8C F0 10 54
[08:23:47:922] TX: STPX H:8CFEF0, R:1, D:14
[08:23:47:968] RX: 8C F0 10 54
[08:23:47:984] Elapsed time 00:00:01.4689132
[08:23:48:000] Read failed, Error

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 7:50 pm
by Gampy
jfitzy wrote: [08:23:29:094] OS ID: 1273003
It has a Custom OS on it ...

Re: PCM Hammer - new ls1 flash tool

Posted: Fri Jan 17, 2020 7:56 pm
by Gampy
Vampyre wrote:would be much easier with a tree view i believe
Explore your interface ...

As I used to tell Windows beginners back in the day, Explore, Explore, Explore ... But ALWAYS cancel out, NEVER make changes while exploring.
Find something you want to change, CANCEL out, then go directly to the change and save it ... Then return to exploring.

This helps prevent the problem of, to many changes (or unintentional) and now it's broke and I don't know what the <bleep> to undo or even remember all the <bleeping> changes I made!
It's back to eating an Elephant 101 ... One Step at a time.
That's life!