PCM Hammer P01 and P59 flash tool v015

They go by many names, P01, P59, VPW, '0411 etc. Also covering E38 and newer here.
megajuz3003
Posts: 74
Joined: Sun Aug 26, 2012 9:47 pm
cars: 2001 VU SS
Location: Brisbane

Re: PCM Hammer - new ls1 flash tool

Post by megajuz3003 »

NSFW wrote:I just uploaded a .zip file of the new release here:

https://github.com/LegacyNsfw/PcmHacks/ ... F12%2F08.1

This should fix the issues with J2534 tools. If you have one, please give it a try and let us know how it goes.

this release worked perfectly with my VXDiag cable :thumbup:

great work on the software... cant wait for write support now :punk:
Attachments
VU SS 5.7L 4L60E Tune.bin
(512 KiB) Downloaded 373 times
User avatar
Gampy
Posts: 2330
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

A few years back got this SparkFun Car Diagnostics Kit and the SparkFun FTDI Basic Breakout 5v as a gift, glued the two together to form a usb -> obd adapter, low and behold it worked as it should!

Saw this PcmHammer thingy a few days back thought I would check it out, ran down to the local JY and picked up a 12200411 and pigtail.

Bit O work later it was all hooked up ... Then ... I flipped the switch.
Cool, I didn't teach it to smoke!

Opened PcmHammer in VS and hit F5, And the results were (after pushin some buttons) ...

Results

Code: Select all

[01:50:54:884]  Voltage: 14.1V
[01:50:54:884]  Elm ID: ELM327 v1.3a
[01:50:54:962]  ScanTool device ID: STN1110 v3.2.0
[01:51:11:275]  VIN: 1GCEC14W81Z213440
[01:51:11:369]  OS ID: 12208322
[01:51:11:447]  Calibration ID: 12208511
[01:51:11:541]  Hardware ID: 9386530
[01:51:11:806]  Serial Number: 1EB0U52R0349
[01:51:11:900]  Broad Cast Code: DLAC
[01:51:11:994]  MEC: 0
[01:51:22:337]  Querying operating system of current PCM.
[01:51:22:462]  OSID: 12208322
[01:51:22:759]  Unlock succeeded.
[01:51:22:869]  This interface does not support VPW 4x
[01:51:22:884]  Uploading kernel to PCM.
[01:51:23:869]  Kernel upload 9% complete.
[01:51:24:306]  Kernel upload 14% complete.
[01:51:24:744]  Kernel upload 19% complete.
[01:51:25:181]  Kernel upload 24% complete.
[01:51:25:603]  Kernel upload 29% complete.
[01:51:26:041]  Kernel upload 34% complete.
[01:51:26:494]  Kernel upload 39% complete.
[01:51:26:916]  Kernel upload 44% complete.
[01:51:27:353]  Kernel upload 49% complete.
[01:51:27:775]  Kernel upload 54% complete.
[01:51:28:212]  Kernel upload 59% complete.
[01:51:28:650]  Kernel upload 64% complete.
[01:51:29:072]  Kernel upload 69% complete.
[01:51:29:525]  Kernel upload 74% complete.
[01:51:29:962]  Kernel upload 79% complete.
[01:51:30:384]  Kernel upload 84% complete.
[01:51:30:822]  Kernel upload 89% complete.
[01:51:31:259]  Kernel upload 94% complete.
[01:51:31:697]  Kernel upload 100% complete.
[01:51:31:712]  kernel uploaded to PCM succesfully. Requesting data...
[01:53:23:212]  Unable to read block from 0 to 499
[01:53:25:384]  Read failed, Error
Debug Log

Code: Select all

[01:50:52:134]  ElmDevice initialization starting.
[01:50:52:744]  TX: 
[01:50:52:822]  TX: AT Z
[01:50:53:666]  AT Z    ELM327 v1.3a
[01:50:53:666]  TX: AT E0
[01:50:54:822]  AT E0  OK
[01:50:54:822]  TX: AT S0
[01:50:54:822]  OK
[01:50:54:822]  TX: AT RV
[01:50:54:884]  Voltage: 14.1V
[01:50:54:884]  TX: AT I
[01:50:54:884]  Elm ID: ELM327 v1.3a
[01:50:54:900]  Initializing PcmHacking.AllProDeviceImplementation
[01:50:54:900]  TX: AT #1
[01:50:54:931]  This is not an AllPro device.
[01:50:54:947]  Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[01:50:54:947]  TX: ST I
[01:50:54:962]  ScanTool device ID: STN1110 v3.2.0
[01:50:54:962]  TX: AT AL
[01:50:55:009]  OK
[01:50:55:009]  TX: AT SP2
[01:50:55:025]  OK
[01:50:55:025]  TX: AT DP
[01:50:55:041]  SAE J1850 VPW
[01:50:55:041]  TX: AT AR
[01:50:55:056]  OK
[01:50:55:056]  TX: AT AT0
[01:50:55:072]  OK
[01:50:55:072]  TX: AT SR F0
[01:50:55:087]  OK
[01:50:55:087]  TX: AT H1
[01:50:55:119]  OK
[01:50:55:119]  TX: AT ST 20
[01:50:55:134]  OK
[01:51:10:916]  Setting timeout for ReadProperty, 47 ms.
[01:51:10:916]  TX: AT ST 0B
[01:51:10:931]  OK
[01:51:10:962]  TX: AT SH 6C 10 F0 
[01:51:10:962]  Set header response: OK
[01:51:10:962]  TX: 3C01 
[01:51:11:119]  RX: 6C F0 10 7C 01 00 31 47 43 45 43
[01:51:11:119]  TX: 3C02 
[01:51:11:197]  RX: 6C F0 10 7C 02 31 34 57 38 31 5A
[01:51:11:197]  TX: 3C03 
[01:51:11:275]  RX: 6C F0 10 7C 03 32 31 33 34 34 30
[01:51:11:275]  VIN: 1GCEC14W81Z213440
[01:51:11:291]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:291]  TX: AT ST 0B
[01:51:11:291]  OK
[01:51:11:291]  TX: 3C0A 
[01:51:11:369]  RX: 6C F0 10 7C 0A 00 BA 48 C2
[01:51:11:369]  OS ID: 12208322
[01:51:11:369]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:369]  TX: AT ST 0B
[01:51:11:384]  OK
[01:51:11:384]  TX: 3C08 
[01:51:11:447]  RX: 6C F0 10 7C 08 00 BA 49 7F
[01:51:11:447]  Calibration ID: 12208511
[01:51:11:447]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:447]  TX: AT ST 0B
[01:51:11:462]  OK
[01:51:11:462]  TX: 3C04 
[01:51:11:541]  RX: 6C F0 10 7C 04 00 8F 3A 22
[01:51:11:541]  Hardware ID: 9386530
[01:51:11:556]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:556]  TX: AT ST 0B
[01:51:11:556]  OK
[01:51:11:556]  TX: 3C05 
[01:51:11:634]  RX: 6C F0 10 7C 05 31 45 42 30
[01:51:11:634]  TX: 3C06 
[01:51:11:712]  RX: 6C F0 10 7C 06 55 35 32 52
[01:51:11:728]  TX: 3C07 
[01:51:11:806]  RX: 6C F0 10 7C 07 30 33 34 39
[01:51:11:806]  Serial Number: 1EB0U52R0349
[01:51:11:806]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:806]  TX: AT ST 0B
[01:51:11:822]  OK
[01:51:11:822]  TX: 3C14 
[01:51:11:900]  RX: 6C F0 10 7C 14 44 4C 41 43
[01:51:11:900]  Broad Cast Code: DLAC
[01:51:11:900]  Setting timeout for ReadProperty, 47 ms.
[01:51:11:900]  TX: AT ST 0B
[01:51:11:916]  OK
[01:51:11:916]  TX: 3CA0 
[01:51:11:994]  RX: 6C F0 10 7C A0 00
[01:51:11:994]  MEC: 0
[01:51:22:337]  Querying operating system of current PCM.
[01:51:22:337]  Setting timeout for ReadProperty, 47 ms.
[01:51:22:353]  TX: AT ST 0B
[01:51:22:353]  OK
[01:51:22:353]  TX: 3C0A 
[01:51:22:462]  RX: 6C F0 10 7C 0A 00 BA 48 C2
[01:51:22:462]  OSID: 12208322
[01:51:22:478]  Suppressing VPW chatter.
[01:51:22:478]  TX: AT SH 6C FE F0 
[01:51:22:509]  Set header response: OK
[01:51:22:509]  TX: 2800 
[01:51:22:572]  RX: 6C F0 10 68 00
[01:51:22:572]  Setting timeout for ReadProperty, 47 ms.
[01:51:22:572]  TX: AT ST 0B
[01:51:22:587]  OK
[01:51:22:587]  Sending seed request.
[01:51:22:587]  TX: AT SH 6C 10 F0 
[01:51:22:603]  Set header response: OK
[01:51:22:603]  TX: 2701 
[01:51:22:681]  RX: 6C F0 10 67 01 40 59
[01:51:22:681]  Parsing seed value.
[01:51:22:681]  Sending unlock request (5940, 3A0D)
[01:51:22:681]  TX: 27023A0D 
[01:51:22:759]  RX: 6C F0 10 67 02 34
[01:51:22:759]  Unlock succeeded.
[01:51:22:775]  Sending 'test device present' notification.
[01:51:22:775]  TX: AT SH 8C FE F0 
[01:51:22:791]  Set header response: OK
[01:51:22:791]  TX: 3F 
[01:51:22:853]  Unexpected response to message content: NO DATA
[01:51:22:869]  This interface does not support VPW 4x
[01:51:22:884]  Loaded T:\Automotive\PcmHacks\PcmHacks\Apps\PcmHammer\bin\Debug\read-kernel.bin
[01:51:22:884]  Uploading kernel to PCM.
[01:51:22:884]  Sending upload request with payload size 3818, loadaddress FF8000
[01:51:22:900]  TX: AT SH 6C 10 F0 
[01:51:22:900]  Set header response: OK
[01:51:22:900]  TX: 34000EEAFF8000 
[01:51:22:978]  RX: 6C F0 10 74 00 44
[01:51:22:994]  Found response, succeeded.
[01:51:22:994]  Going to load a 3818 byte payload to 0xFF8000
[01:51:22:994]  Setting timeout for SendKernel, 213 ms.
[01:51:22:994]  TX: AT ST 35
[01:51:22:994]  OK
[01:51:22:994]  Sending remainder payload with offset 0xE40, start address 0xFF8E40, length 0xAA.
[01:51:23:009]  TX: AT SH 6D 10 F0 
[01:51:23:025]  Set header response: OK
[01:51:23:025]  TX: 360000AAFF8E4024014C3C2C0051EB851FEA802401D482958220429088E5882400E58A2042D0882400E58A2042D0882401948020024A8066044EBAF9E052AF0006206F0006B1EF00146D9E4EBAF9CE302F000A241F508F4E75598F202F000C3F400002700AD0AF0008322F0002E0491201118109B000FFC000700BD0AF0008322F00021201118109B000FFC000588F4E7500FFF60000FFF60600FFF60C00FFF60D00FFF60E00FFF60F00FFFA2700FFD006411E 
[01:51:23:431]  RX: 6D F0 10 76 00 73
[01:51:23:431]  Found response, succeeded.
[01:51:23:431]  Sending payload with offset 0xD80, start address 0xFF8D80, length 0xC0.
[01:51:23:431]  TX: 360000C0FF8D8000FF2240202F000802800000FF00E088100010000280000000FF2040202F0008028000FF000042404840100042811200202F00087418E4A8100010000280000000FF2F092F082F012F004EBAFF16508F508F241F4E75518F426F000670042F400002601C202F0002068000FFC000204010101000024000FFD16F000652AF00027009B0AF00026CDC302F0006508F4E75518F2F024EBAFA3E426F000A42AF00066058202F0006D0AF0010204010101F4000054240102F0005D16F000A222F000630AF 
[01:51:23:869]  RX: 6D F0 10 76 00 73
[01:51:23:869]  Found response, succeeded.
[01:51:23:869]  Kernel upload 9% complete.
[01:51:23:869]  Sending payload with offset 0xCC0, start address 0xFF8CC0, length 0xC0.
[01:51:23:884]  TX: 360000C0FF8CC013C000FFC0074878000548780008487900FFC0004EBAFC3E508F588F4EBAFBCA60FE518F518F2F02226F0018206F001C222F0020202F002434091F42000A34081F4200081F4100061F4000041F7CFF8C000D1F7CFFFE000E1F7CFFF0000F1F7C003F0010422F0011422F0012422F0013102F000A1F400011102F00081F400012102F00061F400013102F00041F40001448780005487800087015D08F2F004EBAFBB4508F588F4EBAFB6E241F508F508F4E752F02202F000810001000028000003362 
[01:51:24:306]  RX: 6D F0 10 76 00 73
[01:51:24:306]  Found response, succeeded.
[01:51:24:306]  Kernel upload 14% complete.
[01:51:24:306]  Sending payload with offset 0xC00, start address 0xFF8C00, length 0xC0.
[01:51:24:306]  TX: 360000C0FF8C000004D2AF000C20411210118109B000FFC000222F000424014C3C2C0051EB851FEA802401D482958220429088E5882400E58A2042D0882400E58A2042D0882401948020024A8066044EBAFC0A53AF00044AAF00046CA0241F588F4E754EBAFC4A13FC006C00FFC00013FCFFF000FFC00113FC001000FFC00213FC006000FFC003202F00047218E2A8100013C000FFC004202F0004028000FF000042404840100013C000FFC005202F000402800000FF00E088100013C000FFC006202F0004100042BD 
[01:51:24:744]  RX: 6D F0 10 76 00 73
[01:51:24:744]  Found response, succeeded.
[01:51:24:744]  Kernel upload 19% complete.
[01:51:24:744]  Sending payload with offset 0xB40, start address 0xFF8B40, length 0xC0.
[01:51:24:744]  TX: 360000C0FF8B40C0002040108152AF000C6072203C00FFF60F20401210202F001420401081203C00FFF60C204010BC00024AAF000C6602604C202F00142040101049C07230C0817230B280660E202F0018204010BC00024280604C202F0018204010BC0001202F000C603C4E71203C00FFF60E20401010202F0018204010BC000B428060224EBAFC9452AF00080CAF0000752F00086F00FEE4202F0018204010BC000A202F000C508F508F4E75598F2F02202F001053802F400004605A202F0004D0AF0014222F339A 
[01:51:25:181]  RX: 6D F0 10 76 00 73
[01:51:25:181]  Found response, succeeded.
[01:51:25:181]  Kernel upload 24% complete.
[01:51:25:181]  Sending payload with offset 0xA80, start address 0xFF8A80, length 0xC0.
[01:51:25:181]  TX: 360000C0FF8A8000031F41001F4A2F001F670A0CAF000000F9000E6FBA4EBAFE3E4FEF00204E75518F518F4EBAFDAE42AF000C42AF0008600001140CAF000013EC000C6612202F0018204010BCFFEE202F000C60000112203C00FFF60E2040101049C0721F4601C081EA801F4000034280102F00037207B280650000CA303B0A064EFB00020010002E002E00A6002E004E004E004E42AF0004600C4EBAFD3E4EBAFD8452AF00047009B0AF00046CEC60000094203C00FFF60F204010101200202F000C068000FF38D5 
[01:51:25:603]  RX: 6D F0 10 76 00 73
[01:51:25:603]  Found response, succeeded.
[01:51:25:603]  Kernel upload 29% complete.
[01:51:25:603]  Sending payload with offset 0x9C0, start address 0xFF89C0, length 0xC0.
[01:51:25:603]  TX: 360000C0FF89C0001F0C2F0002001F67080C2F0003001F660A0CAF000000F900166FB052AF001A206F001AB1EF00066D00FF6E7004C0AF002C4A80670000A4203C00FFF60C204010BC000C223C00FFF60D202F00285380D0AF002420401010204110804EBAFE80203C00FFF60C204010BC0003203C00FFF60D20404210203C00FFF60E204010101200020100031F41001F42AF000E603652AF000E42AF000A600C4EBAFDF84EBAFE3E52AF000A7063B0AF000A6CEC4EBAFDE4203C00FFF60E20401010120002013B83 
[01:51:26:041]  RX: 6D F0 10 76 00 73
[01:51:26:041]  Found response, succeeded.
[01:51:26:041]  Kernel upload 34% complete.
[01:51:26:056]  Sending payload with offset 0x900, start address 0xFF8900, length 0xC0.
[01:51:26:056]  TX: 360000C0FF890000FFC4002040421052977063B0976CEC588F4E754FEFFFE04EBAFF3A7001C0AF002C4A80670C203C00FFF60C204010BC00147004C0AF002C4A806708202F002853806004202F00282F40000642AF000242AF001A6000008A223C00FFF60D202F001AD0AF002420401010204110804EBAFEE4203C00FFF60E204010101200020100031F41001F42AF0016603652AF001642AF0012600C4EBAFEBC4EBAFF0252AF00127031B0AF00126CEC4EBAFEA8203C00FFF60E204010101200020100031F413F7D 
[01:51:26:478]  RX: 6D F0 10 76 00 73
[01:51:26:478]  Found response, succeeded.
[01:51:26:494]  Kernel upload 39% complete.
[01:51:26:494]  Sending payload with offset 0x840, start address 0xFF8840, length 0xC0.
[01:51:26:494]  TX: 360000C0FF884088A8101749C02F004EB900FF8C5C588F508F4E75203C00FFFA27204010BC0055203C00FFFA27204010BCFFAA223C00FFD006203C00FFD006204010100200007F20411080223C00FFD006203C00FFD006204010100000FF80204110804E754E714E714E714E714E75518F42AF000460184EBAFFA2429760064EBAFFE452977009B0976CF452AF00040CAF0000270F00046FDE508F4E75598F4297600E2017068000FFC0002040421052970C97000003FF6FEA588F4E75598F4297600E2017068045F3 
[01:51:26:916]  RX: 6D F0 10 76 00 73
[01:51:26:916]  Found response, succeeded.
[01:51:26:916]  Kernel upload 44% complete.
[01:51:26:916]  Sending payload with offset 0x780, start address 0xFF8780, length 0xC0.
[01:51:26:916]  TX: 360000C0FF878000FFC00310000280000000FF42A742A72F00487800B24EB900FF8CE2508F508F603E103900FFC00510000280000000FF2040103900FFC00442811200103900FFC00310000280000000FF2F082F012F00487800AA4EB900FF8CE2508F508F4E714E75518F202F000C1E801F7CFF8C00031F7CFFFE00041F7CFFF000051F7C003F00061F5700074878000148780005700BD08F2F004EB900FF8914508F588F487800042F2F0014487900FFC4004EB900FF8914508F588F4EB900FF88A84EB900FF426C 
[01:51:27:353]  RX: 6D F0 10 76 00 73
[01:51:27:353]  Found response, succeeded.
[01:51:27:353]  Kernel upload 49% complete.
[01:51:27:353]  Sending payload with offset 0x6C0, start address 0xFF86C0, length 0xC0.
[01:51:27:353]  TX: 360000C0FF86C0007600FFC0034878000548780004487900FFC0004EB900FF8914508F588F0C2FFF800019660E2F6F00100006202F000620404E90241F4FEF00204E75103900FFC0010C0000106710103900FFC0010C00FFFE6704600000CA103900FFC0020C00FFF06704600000BA103900FFC00310000280000000FF7235B28067287235B2806D087234B280671060587236B280671A7237B2806728604A4EBAFBC64EB900FF88F6607C4EBAF9FA6076103900FFC0000C00006D66064EBAFCAA606460621039459A 
[01:51:27:775]  RX: 6D F0 10 76 00 73
[01:51:27:775]  Found response, succeeded.
[01:51:27:775]  Kernel upload 54% complete.
[01:51:27:791]  Sending payload with offset 0x600, start address 0xFF8600, length 0xC0.
[01:51:27:791]  TX: 360000C0FF860000FFC009202F0014100013C000FFC00A487800054878000B487900FFC0004EB900FF8914508F588F600000CA42AF000A42AF001A6066222F001A24014C3C2C0051EB851FE8802401D482958220429088D0802400E58A2042D0882400E58A2042D0882401948020027201B28066064EB900FF8854202F001A242F0010D4802F42000A222F000A700AD0AF001A103009B000FFC0002041108052AF001A202F001AB0AF0014659013FC006D00FFC00013FCFFF000FFC00113FC001000FFC00213FC42E1 
[01:51:28:212]  RX: 6D F0 10 76 00 73
[01:51:28:212]  Found response, succeeded.
[01:51:28:212]  Kernel upload 59% complete.
[01:51:28:212]  Sending payload with offset 0x540, start address 0xFF8540, length 0xC0.
[01:51:28:212]  TX: 360000C0FF8540002252AF001E222F001E700AD0AF0014B08162C2700AD0AF0014103009B000FFC00010000280000000FFE1883200700BD0AF0014103009B000FFC0001000024000FF80413F40000E302F000EB06F00226700009A13FC006D00FFC00013FCFFF000FFC00113FC001000FFC00213FC007F00FFC00313FC003600FFC004302F0022E048100013C000FFC005302F0022100013C000FFC006302F000EE048100013C000FFC007302F000E100013C000FFC008202F001402800000FF00E088100013C03EC9 
[01:51:28:650]  RX: 6D F0 10 76 00 73
[01:51:28:650]  Found response, succeeded.
[01:51:28:650]  Kernel upload 64% complete.
[01:51:28:650]  Sending payload with offset 0x480, start address 0xFF8480, length 0xC0.
[01:51:28:650]  TX: 360000C0FF848010000280000000FF81AF0010202F0010E1882F400010103900FFC00910000280000000FF81AF00100CAF00001000001462140CAF00FF9FFF0010630A0CAF00FFB0000010634413FC006D00FFC00013FCFFF000FFC00113FC001000FFC00213FC007F00FFC00313FC003600FFC0044878000548780005487900FFC0004EB900FF8914508F588F600001EC426F002270042F40001E6030202F001E0280000003FF4A8066064EB900FF8854202F001E068000FFC000204010101000024000FFD16F3E29 
[01:51:29:072]  RX: 6D F0 10 76 00 73
[01:51:29:072]  Found response, succeeded.
[01:51:29:072]  Kernel upload 69% complete.
[01:51:29:087]  Sending payload with offset 0x3C0, start address 0xFF83C0, length 0xC0.
[01:51:29:087]  TX: 360000C0FF83C0003400FFC0044878000548780005487900FFC0004EB900FF8914508F588F603E13FC006C00FFC00013FCFFF000FFC00113FC001000FFC00213FC007400FFC003423900FFC0044878000548780005487900FFC0004EB900FF8914508F588F508F4E754FEFFFE02F021F7900FFC0040019103900FFC00510000280000000FF2F400014202F0014E1882F400014103900FFC00610000280000000FF81AF0014103900FFC00710000280000000FF2F400010202F0010E1882F400010103900FFC0084205 
[01:51:29:525]  RX: 6D F0 10 76 00 73
[01:51:29:525]  Found response, succeeded.
[01:51:29:525]  Kernel upload 74% complete.
[01:51:29:525]  Sending payload with offset 0x300, start address 0xFF8300, length 0xC0.
[01:51:29:525]  TX: 360000C0FF8300588F4878000448780002700AD08F2F004EB900FF8914508F588F508F588F4E75518F103900FFC00510000280000000FF2F400004202F0004E1882F400004103900FFC00610000280000000FF81AF0004103900FFC00710000280000000FF2E802017E1882E80103900FFC00810000280000000FF81972017E1882E80103900FFC00910000280000000FF81970CAF00001000000462080C9700FFA000674213FC006C00FFC00013FCFFF000FFC00113FC001000FFC00213FC007F00FFC00313FC3F54 
[01:51:29:962]  RX: 6D F0 10 76 00 73
[01:51:29:962]  Found response, succeeded.
[01:51:29:962]  Kernel upload 79% complete.
[01:51:29:962]  Sending payload with offset 0x240, start address 0xFF8240, length 0xC0.
[01:51:29:962]  TX: 360000C0FF8240C00013FCFFF000FFC00113FC001000FFC00213FC003600FFC00313FC000100FFC004202F0008E088100013C000FFC005202F0008100013C000FFC006202F000442404840100013C000FFC007202F0004E088100013C000FFC008202F0004100013C000FFC009487800014878000A487900FFC0004EB900FF8914508F588F4EB900FF8DD63F400002222F0008202F00042F012F004EB900FF8E10508F3200302F0002D0413F400002222F0008202F0004487800022F012F004EB900FF8914508F3BE7 
[01:51:30:384]  RX: 6D F0 10 76 00 73
[01:51:30:384]  Found response, succeeded.
[01:51:30:384]  Kernel upload 84% complete.
[01:51:30:400]  Sending payload with offset 0x180, start address 0xFF8180, length 0xC0.
[01:51:30:400]  TX: 360000C0FF8180103900FFC00610000280000000FF81AF0008103900FFC00710000280000000FF2F400004202F0004E1882F400004103900FFC00810000280000000FF81AF0004202F0004E1882F400004103900FFC00910000280000000FF81AF000413FC006C00FFC00013FCFFF000FFC00113FC001000FFC00213FC007500FFC00313FC000100FFC00413FC005400FFC00513FC006C00FFC00613FCFFF000FFC0074878000548780008487900FFC0004EB900FF8914508F588F4EB900FF88A813FC006D00FF43F6 
[01:51:30:822]  RX: 6D F0 10 76 00 73
[01:51:30:822]  Found response, succeeded.
[01:51:30:822]  Kernel upload 89% complete.
[01:51:30:822]  Sending payload with offset 0xC0, start address 0xFF80C0, length 0xC0.
[01:51:30:822]  TX: 360000C0FF80C06000009A60000096102F000349C07230C0814A80670460000084102F00020C0000016732102F000242811200102F000210000280000000FF2F012F00487800BB487800BB4EB900FF8CE2508F508F4EB900FF88A86046123900FFC003202F000C068000FFC4002040108152AF000C2F6F00140010103900FFC0030C00002066164EB900FF88A82F2F000C4878FFEE4EB900FF87E2508F4EB900FF86FC6000FF18518F598F103900FFC00510000280000000FF2F400008202F0008E1882F4000083C3A 
[01:51:31:259]  RX: 6D F0 10 76 00 73
[01:51:31:259]  Found response, succeeded.
[01:51:31:259]  Kernel upload 94% complete.
[01:51:31:275]  Sending payload with offset 0x0, start address 0xFF8000, length 0xC0.
[01:51:31:275]  TX: 368000C0FF80004FEFFFE8007C07004EB900FF8854203900FF8ECE204042104EB900FF88A8203900FF8ED2204010BC0003203900FF8ED6204042104EB900FF88D64EB900FF889E42A742A742A742A74EB900FF8CE2508F508F4EB900FF88A842AF001470642F400008202F001490AF0008220052812F41001042AF000C52AF00144EB900FF885450EF000350EF0002200F54802F00200F5E802F004EB900FF8AA0508F2F4000044AAF00046622202F0010D0AF0008B0AF00146C104878FFFF4EB900FF8C5C588F4999 
[01:51:31:697]  RX: 6D F0 10 76 00 73
[01:51:31:697]  Found response, succeeded.
[01:51:31:697]  Kernel upload 100% complete.
[01:51:31:712]  kernel uploaded to PCM succesfully. Requesting data...
[01:51:31:712]  Setting timeout for ReadMemoryBlock, 1113 ms.
[01:51:31:712]  TX: AT ST FF
[01:51:31:728]  OK
[01:51:31:728]  Sending 'test device present' notification.
[01:51:31:728]  TX: AT SH 8C FE F0 
[01:51:31:744]  Set header response: OK
[01:51:31:744]  TX: 3F 
[01:51:33:072]  Empty response to message content.
[01:51:33:087]  Reading from 0, length 500
[01:51:33:087]  TX: AT SH 6D 10 F0 
[01:51:33:087]  Set header response: STOPPED
[01:51:33:087]  TX: AT SH 6D 10 F0 
[01:51:33:103]  Set header response: ?
[01:51:33:103]  Unexpected response to set-header command: ?
[01:51:33:103]  Unable to send read request.
[01:51:33:103]  TX: AT SH 6D 10 F0 
[01:51:33:103]  Set header response: OK
[01:51:33:103]  TX: 350101F4000000 
[01:51:34:181]  RX: 6C F0 10 75 01 54 6C F0
[01:51:34:181]  Processing message
[01:51:34:181]  Read request allowed, expecting for payload...
[01:51:35:541]  Timeout during receive.
[01:51:35:541]  No payload following read request.
[01:51:36:869]  Timeout during receive.
[01:51:36:884]  No payload following read request.
[01:51:38:212]  Timeout during receive.
[01:51:38:212]  No payload following read request.
[01:51:39:572]  Timeout during receive.
[01:51:39:587]  No payload following read request.
[01:51:40:916]  Timeout during receive.
[01:51:40:931]  No payload following read request.
[01:51:42:259]  Timeout during receive.
[01:51:42:275]  No payload following read request.
[01:51:43:634]  Timeout during receive.
[01:51:43:634]  No payload following read request.
[01:51:44:947]  Timeout during receive.
[01:51:44:947]  No payload following read request.
[01:51:46:291]  Timeout during receive.
[01:51:46:291]  No payload following read request.
[01:51:47:619]  Timeout during receive.
[01:51:47:619]  No payload following read request.
[01:51:48:947]  Timeout during receive.
[01:51:48:962]  No payload following read request.
[01:51:50:322]  Timeout during receive.
[01:51:50:322]  No payload following read request.
[01:51:51:650]  Timeout during receive.
[01:51:51:666]  No payload following read request.
[01:51:53:041]  Timeout during receive.
[01:51:53:041]  No payload following read request.
[01:51:54:431]  Timeout during receive.
[01:51:54:431]  No payload following read request.
[01:51:54:447]  TX: 350101F4000000 
[01:51:55:509]  Unexpected response to message content: NO DATA
[01:51:55:509]  Unable to send read request.
[01:51:55:509]  TX: 350101F4000000 
[01:51:56:634]  RX: 6C F0 10 75 01 54 6C F0
[01:51:56:650]  Processing message
[01:51:56:650]  Read request allowed, expecting for payload...
[01:51:57:994]  Timeout during receive.
[01:51:57:994]  No payload following read request.
[01:51:59:306]  Timeout during receive.
[01:51:59:306]  No payload following read request.
[01:52:00:619]  Timeout during receive.
[01:52:00:619]  No payload following read request.
[01:52:01:947]  Timeout during receive.
[01:52:01:947]  No payload following read request.
[01:52:03:275]  Timeout during receive.
[01:52:03:275]  No payload following read request.
[01:52:04:619]  Timeout during receive.
[01:52:04:619]  No payload following read request.
[01:52:05:931]  Timeout during receive.
[01:52:05:931]  No payload following read request.
[01:52:07:337]  Timeout during receive.
[01:52:07:337]  No payload following read request.
[01:52:08:728]  Timeout during receive.
[01:52:08:728]  No payload following read request.
[01:52:10:056]  Timeout during receive.
[01:52:10:056]  No payload following read request.
[01:52:11:369]  Timeout during receive.
[01:52:11:369]  No payload following read request.
[01:52:12:697]  Timeout during receive.
[01:52:12:697]  No payload following read request.
[01:52:14:025]  Timeout during receive.
[01:52:14:041]  No payload following read request.
[01:52:15:353]  Timeout during receive.
[01:52:15:353]  No payload following read request.
[01:52:16:712]  Timeout during receive.
[01:52:16:712]  No payload following read request.
[01:52:16:712]  TX: 350101F4000000 
[01:52:17:775]  Unexpected response to message content: NO DATA
[01:52:17:775]  Unable to send read request.
[01:52:17:775]  TX: 350101F4000000 
[01:52:18:837]  RX: 6C F0 10 75 01 54 6C F0
[01:52:18:853]  Processing message
[01:52:18:853]  Read request allowed, expecting for payload...
[01:52:20:181]  Timeout during receive.
[01:52:20:181]  No payload following read request.
[01:52:21:494]  Timeout during receive.
[01:52:21:494]  No payload following read request.
[01:52:22:837]  Timeout during receive.
[01:52:22:837]  No payload following read request.
[01:52:24:150]  Timeout during receive.
[01:52:24:150]  No payload following read request.
[01:52:25:478]  Timeout during receive.
[01:52:25:478]  No payload following read request.
[01:52:26:791]  Timeout during receive.
[01:52:26:791]  No payload following read request.
[01:52:28:119]  Timeout during receive.
[01:52:28:119]  No payload following read request.
[01:52:29:431]  Timeout during receive.
[01:52:29:431]  No payload following read request.
[01:52:30:759]  Timeout during receive.
[01:52:30:759]  No payload following read request.
[01:52:32:103]  Timeout during receive.
[01:52:32:103]  No payload following read request.
[01:52:33:431]  Timeout during receive.
[01:52:33:431]  No payload following read request.
[01:52:34:759]  Timeout during receive.
[01:52:34:759]  No payload following read request.
[01:52:36:087]  Timeout during receive.
[01:52:36:087]  No payload following read request.
[01:52:37:462]  Timeout during receive.
[01:52:37:462]  No payload following read request.
[01:52:38:775]  Timeout during receive.
[01:52:38:775]  No payload following read request.
[01:52:38:775]  TX: 350101F4000000 
[01:52:39:837]  Unexpected response to message content: NO DATA
[01:52:39:837]  Unable to send read request.
[01:52:39:837]  TX: 350101F4000000 
[01:52:40:947]  RX: 6C F0 10 75 01 54 6C F0
[01:52:40:947]  Processing message
[01:52:40:947]  Read request allowed, expecting for payload...
[01:52:42:322]  Timeout during receive.
[01:52:42:322]  No payload following read request.
[01:52:43:634]  Timeout during receive.
[01:52:43:634]  No payload following read request.
[01:52:45:025]  Timeout during receive.
[01:52:45:025]  No payload following read request.
[01:52:46:384]  Timeout during receive.
[01:52:46:384]  No payload following read request.
[01:52:47:697]  Timeout during receive.
[01:52:47:697]  No payload following read request.
[01:52:49:041]  Timeout during receive.
[01:52:49:041]  No payload following read request.
[01:52:50:353]  Timeout during receive.
[01:52:50:353]  No payload following read request.
[01:52:51:681]  Timeout during receive.
[01:52:51:681]  No payload following read request.
[01:52:52:994]  Timeout during receive.
[01:52:52:994]  No payload following read request.
[01:52:54:337]  Timeout during receive.
[01:52:54:337]  No payload following read request.
[01:52:55:666]  Timeout during receive.
[01:52:55:666]  No payload following read request.
[01:52:56:994]  Timeout during receive.
[01:52:56:994]  No payload following read request.
[01:52:58:353]  Timeout during receive.
[01:52:58:353]  No payload following read request.
[01:52:59:666]  Timeout during receive.
[01:52:59:666]  No payload following read request.
[01:53:01:025]  Timeout during receive.
[01:53:01:025]  No payload following read request.
[01:53:01:025]  TX: 350101F4000000 
[01:53:02:087]  Unexpected response to message content: NO DATA
[01:53:02:087]  Unable to send read request.
[01:53:02:087]  TX: 350101F4000000 
[01:53:03:212]  RX: 6C F0 10 75 01 54 6C F0
[01:53:03:212]  Processing message
[01:53:03:212]  Read request allowed, expecting for payload...
[01:53:04:541]  Timeout during receive.
[01:53:04:541]  No payload following read request.
[01:53:05:900]  Timeout during receive.
[01:53:05:900]  No payload following read request.
[01:53:07:212]  Timeout during receive.
[01:53:07:212]  No payload following read request.
[01:53:08:541]  Timeout during receive.
[01:53:08:541]  No payload following read request.
[01:53:09:853]  Timeout during receive.
[01:53:09:853]  No payload following read request.
[01:53:11:212]  Timeout during receive.
[01:53:11:212]  No payload following read request.
[01:53:12:541]  Timeout during receive.
[01:53:12:541]  No payload following read request.
[01:53:13:869]  Timeout during receive.
[01:53:13:869]  No payload following read request.
[01:53:15:212]  Timeout during receive.
[01:53:15:212]  No payload following read request.
[01:53:16:525]  Timeout during receive.
[01:53:16:525]  No payload following read request.
[01:53:17:884]  Timeout during receive.
[01:53:17:884]  No payload following read request.
[01:53:19:197]  Timeout during receive.
[01:53:19:197]  No payload following read request.
[01:53:20:541]  Timeout during receive.
[01:53:20:541]  No payload following read request.
[01:53:21:853]  Timeout during receive.
[01:53:21:853]  No payload following read request.
[01:53:23:212]  Timeout during receive.
[01:53:23:212]  No payload following read request.
[01:53:23:212]  Unable to read block from 0 to 499
[01:53:23:228]  Cleaning up Flash Kernel
[01:53:23:228]  TX: AT SH 6C 10 F0 
[01:53:23:228]  Set header response: OK
[01:53:23:244]  TX: 20 
[01:53:24:291]  Unexpected response to message content: NO DATA
[01:53:24:291]  Clear DTCs
[01:53:24:291]  TX: AT SH 68 6A F0 
[01:53:24:306]  Set header response: OK
[01:53:24:306]  TX: 04 
[01:53:25:384]  Unexpected response to message content: NO DATA
[01:53:25:384]  Read failed, Error
Well, I just gotta say WHOO HOO folks great job!
Even though it failed in the end, I didn't expect it to work at all in it's current state of development with this adapter.

Any ideas on the failure ... I'm pretty rusty at dis shit.

Guess it's time to look into the code some ... Gawsh I do so dislike C#.

Not kickin anyone in the knees, however, wouldn't MDI be a better ui, especially if y'all ever plan on table comparasion and the like in the future.
I dunno know ...

Anyways hats off to y'all.

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

It looks like that interface is having trouble receiving the response to the "read block" request. It's hard to say why for sure, but I suspect that the reply is overflowing the interface's receive buffer. Since you've got the tools, try cutting the buffer size in half. It's set in scantooldevice.cs, in the constructor if I remember right.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
Gampy
Posts: 2330
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

Just to be clear this is the develop branch ...

So, I opened ScanToolDeviceImplementation.cs and reduced:

Code: Select all

            this.MaxReceiveSize = 500 + 12;
down to 200 then to 50 then 10 with no success.
I have it at 50 now, gonna leave it there for now unless directed otherwise.

I am also using the test kernel button with the "micro-kernel.bin" section commented out now. Shorting things up a bit ...
(The above posted log is from the "Read Full Contents" button.)

Still trying to wrap my teeth around the sequence of things here ...

I would like to hammer on this and see if I can get it to work while I await the allpro to arrive, it's been shipped.
Nothing better to do unfortunately.

How can I confirm the kernel is running on the ecm?

Thanks for your reponse.

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by antus »

My obdlink sx is a "STN1130 v4.0.1" and it looks like yours is an "STN1110 v3.2.0". Maybe see if a firmware upgrade to 4.x is available from scantool? It seems to be ok until the point where it needs to receive 2 responses in a row. This is not a common use case, and maybe it requires a firmware 4.x?
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
antus
Site Admin
Posts: 8237
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer - new ls1 flash tool

Post by antus »

Also, which kernel is it? I think we need to start putting version numbers in the app, logs, and maybe the kernel headers.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
Gampy
Posts: 2330
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

Started my own thread on this here: PcmHammer with ST1110 (sparkfun version)

Thank y'all for doing what ya do ...

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

Yes, ScanToolDeviceImplementation is where you want to make that change, I was assuming you were dealing with one of the release branches. The develop branch is probably a better choice though. :)

With the develop branch, you should be able to read the PCM using read-kernel, using the supported devices. Others might work, and to be honest I'm a little surprised the Sparkfun doesn't work, but you're the first person to try it.

micro-kernel just echoes back any messages that are sent to it, with a short prefix to distinguish them as echoes. The "Test Kernel" code in the develop branch will load the read-kernel, read one block, then load the micro-kernel, then send some messages for it to respond to. Those should be visible in the debug tab. Having one kernel load another kernel may or may not actually be useful, but it was an interesting exercise. Pete had a pretty cool idea about keeping the PCM kernel running after flashing, to help recover from failed flashes, and I thought it might be interesting to take that a step further and make it possible to switch kernels on-the-fly as well. But mostly I just wanted to write more kernel code for the sake of getting better at writing kernel code, before I tackle flashing.

Speaking of flashing... I've switched to a private branch right now for the write kernel. We're going to keep that kernel under wraps for a little while, due to some shady behavior around previous LS flash tools. But I'm hoping to post a working binary release within a week or two (probably supporting calibration reflashing only), with open sourcing of the kernel to follow later. I'm still pushing C# stuff to github though, and I have no plans to change that.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
NSFW
Posts: 679
Joined: Fri Feb 02, 2018 3:13 pm

Re: PCM Hammer - new ls1 flash tool

Post by NSFW »

Also regarding MDI and viewing/editing tables... You're right... but we're focused on reading and writing for now, and we suggest using Tuner Pro to view and edit the files.

That said, the project is already split into an EXE (PcmHammer) that contains mostly just UI and platform-specific stuff, and a DLL (PcmLibrary) that contains platform-agnostic stuff. If someone wants to add this read-write code to an existing open-source editor, just use the code in PcmLibrary, and look at the PcmHammer code as a reference for how to use it.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
User avatar
Gampy
Posts: 2330
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer - new ls1 flash tool

Post by Gampy »

NSFW wrote:With the develop branch, you should be able to read the PCM using read-kernel, using the supported devices. Others might work, and to be honest I'm a little surprised the Sparkfun doesn't work, but you're the first person to try it.
I had it, thought I'd try it ... Now the bug is in me and I gotta prove it one way or the other!
NSFW wrote:micro-kernel just echoes back any messages that are sent to it, with a short prefix to distinguish them as echoes. The "Test Kernel" code in the develop branch will load the read-kernel, read one block, then load the micro-kernel, then send some messages for it to respond to. Those should be visible in the debug tab. Having one kernel load another kernel may or may not actually be useful, but it was an interesting exercise. Pete had a pretty cool idea about keeping the PCM kernel running after flashing, to help recover from failed flashes, and I thought it might be interesting to take that a step further and make it possible to switch kernels on-the-fly as well. But mostly I just wanted to write more kernel code for the sake of getting better at writing kernel code, before I tackle flashing.
Thank you!

And I get 'for the sake of getting better' ... That's me, I am here to feed the brain after all.
NSFW wrote:We're going to keep that kernel under wraps for a little while, due to some shady behavior around previous LS flash tools.
All who shall pay for the greed of a few while hungry brains weep for the food of knowledge!
NSFW wrote:That said, the project is already split into an EXE (PcmHammer) that contains mostly just UI and platform-specific stuff, and a DLL (PcmLibrary) that contains platform-agnostic stuff. If someone wants to add this read-write code to an existing open-source editor, just use the code in PcmLibrary, and look at the PcmHammer code as a reference for how to use it.
Yup, been admiring the design and layout ...

Thank you
-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
Post Reply