First time tuning. Need some help.

[antus]

As this is a conversion, i'd be swapping to an os with a good XDF. There is no benefit to using the original OS, and at this starting point you might as well set yourself up right.

[vvise]

Okay bad news I tried grounding the correct pin but with no success. I tried it with various timing at various points while trying to connect, no success.

I attached some screenshots to explain better where the communication is breaking down. I load up LS Droid select Read, click on P01/P59 then press the bluetooth button in the top right. I can select the device and a prompt comes up with the experimental warning. I get notified by Andriod that Bluetooth is connected. I press continue and the ODB and Host lights on the scanner turn on briefly but go out, nothing happens in the output window and a few seconds later I get a Setup Timed Out popup.

I tried grounding the pin before and after selecting the bluetooth device, during and after pressing continue, and while waiting for it to timeout. No change.

I validated the ODBLinkMX+ is working fine with another car. I also tried LS Driod 2.1, 2.2, 2.2B.
Would my results be different with a different ODB2 interface device and a PC?


EDIT :: I'm having some luck with PCM Hammer right now, it appears to be connected. Will update soon.

[vvise]

I tried reading the PCM with PCM Hammer 014. It worked well at first, but after the read completed it started a verification and failed, after 5 minutes with no update i hit cancel.

Code: Select all

...
[09:08:53:781]  0x0FE000	99%	00:08
[09:08:54:769]  0x0FE400	99%	00:07
[09:08:55:798]  0x0FE800	99%	00:06
[09:08:56:824]  0x0FEC00	99%	00:05
[09:08:57:796]  0x0FF000	99%	00:04
[09:08:58:810]  0x0FF400	99%	00:03
[09:08:59:858]  0x0FF800	99%	00:02
[09:09:00:854]  0x0FFC00	99%	00:01
[09:09:00:864]  Read complete.
[09:09:00:875]  All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[09:09:00:892]  We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[09:09:00:908]  Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[09:09:00:924]  Starting verification...
[09:09:00:943]  Calculating CRCs from file...
[09:09:00:963]  Requesting CRCs from PCM...
[09:09:01:148]  	Range		File CRC		PCM CRC	Verdict	Purpose
[09:09:04:394]  0F0000-0FFFFF	8D0F8F91	8D0F8F91	Same	OperatingSystem
[09:09:07:622]  0E0000-0EFFFF	A50F3C90	A50F3C90	Same	OperatingSystem
[09:09:10:871]  0D0000-0DFFFF	A50F3C90	A50F3C90	Same	OperatingSystem
[09:17:21:318]  Unable to get CRC for memory range 000C0000 / 00010000
[09:22:28:704]  Cancel button clicked.[09:22:28:704]  Cancel button clicked.
[09:23:07:288]  Unable to get CRC for memory range 000B0000 / 00010000
[09:23:40:414]  Unable to get CRC for memory range 000A0000 / 00010000
[09:24:13:536]  Unable to get CRC for memory range 00090000 / 00010000
[09:24:46:656]  Unable to get CRC for memory range 00080000 / 00010000
[09:25:19:779]  Unable to get CRC for memory range 00070000 / 00010000
[09:25:52:905]  Unable to get CRC for memory range 00060000 / 00010000
[09:26:26:031]  Unable to get CRC for memory range 00050000 / 00010000
[09:26:59:150]  Unable to get CRC for memory range 00040000 / 00010000
[09:27:32:271]  Unable to get CRC for memory range 00030000 / 00010000
[09:28:05:393]  Unable to get CRC for memory range 00020000 / 00010000
[09:28:38:517]  Unable to get CRC for memory range 00010000 / 00010000
[09:29:11:635]  Unable to get CRC for memory range 00008000 / 00008000
[09:29:44:756]  Unable to get CRC for memory range 00006000 / 00002000
[09:30:17:877]  Unable to get CRC for memory range 00004000 / 00002000
[09:30:51:000]  Unable to get CRC for memory range 00000000 / 00004000
[09:31:24:125]  ##############################################################################
[09:31:24:137]  There are errors in the data that was read from the PCM. Do not use this file.
[09:31:24:147]  ##############################################################################
[09:31:35:264]  Clearing trouble codes.
[09:32:42:296]  Clearing trouble codes.
[09:33:27:349]  Elapsed time 00:42:01.2923776
[09:33:27:355]  Saving contents to C:\~~~~~~~~~~~~~~~~\PcmHammer014\PcmHammer014\van corrupted test.bin

Okay, so it confirmed the file is junk. all appears to be working well. I'm going to try and flash it back to working order.

[antus]

yeah do a full write of a known good bin, and then set the vin to match your car (or dont... up to you).

I dont know what engine your using it with and Im less familiar with the American stuff but I'd flash the the attached bin with tools/write full flash (clone) after booting it with pin jumped for recovery then from them on use the bin with with the xdf from boardtruckowners repo which you linked already here https://github.com/BoredTruckOwner/LS_B ... es/P59_1Mb

It looks like pcmhammer defaulted to doing a 512kb read, rather than 1mb, which is why the checksum above 1mb failed. This might be a side effect of reading in recovery mode, we probably need to detect the chip type and use that to determine the size. Either way the above is still a good next step to get on to a well supported OS.

[vvise]

I did a test write using the original van bin i had and it failed.

Code: Select all

[09:48:49:008]  C:\Users\Peter\Downloads\PcmHammer014\PcmHammer014\2005Van.bin
[09:48:50:017]  Validating 1024k file.
[09:48:50:022]  	Start	End	Stored	Needed	Verdict	Segment Name
[09:48:50:029]  	00000	FFFFD	8988	8988	Good	Operating system
[09:48:50:035]  	08002	15FEF	F181	F181	Good	Engine calibration
[09:48:50:041]  	15FF2	1912F	9C11	9C11	Good	Engine diagnostics.
[09:48:50:050]  	19132	1D3AF	D6F2	D6F2	Good	Transmission calibration
[09:48:50:056]  	1D3B2	1DCAF	CDDB	CDDB	Good	Transmission diagnostics
[09:48:50:065]  	1DCB2	1F6AF	1475	1475	Good	Fuel system
[09:48:50:073]  	1F6B2	1FF9F	EF62	EF62	Good	System
[09:48:50:083]  	1FFA2	1FFEF	000A	000A	Good	Speedometer
[09:48:50:095]  Requesting operating system ID...
[09:49:12:217]  Operating system request failed, checking for a live kernel...
[09:50:07:971]  Checking for recovery mode...
[09:53:59:107]  PCM is not responding to OSID, kernel version, or recovery mode checks.
[09:53:59:110]  Unlock may not work, but we'll try...
[09:56:34:710]  Unable to send seed request.
[09:56:34:724]  Unlock was not successful.

here's the full debug:

Code: Select all

[09:48:49:008]  C:\Users\Peter\Downloads\PcmHammer014\PcmHammer014\2005Van.bin
[09:48:50:017]  Validating 1024k file.
[09:48:50:022]  	Start	End	Stored	Needed	Verdict	Segment Name
[09:48:50:029]  	00000	FFFFD	8988	8988	Good	Operating system
[09:48:50:035]  	08002	15FEF	F181	F181	Good	Engine calibration
[09:48:50:041]  	15FF2	1912F	9C11	9C11	Good	Engine diagnostics.
[09:48:50:050]  	19132	1D3AF	D6F2	D6F2	Good	Transmission calibration
[09:48:50:056]  	1D3B2	1DCAF	CDDB	CDDB	Good	Transmission diagnostics
[09:48:50:065]  	1DCB2	1F6AF	1475	1475	Good	Fuel system
[09:48:50:073]  	1F6B2	1FF9F	EF62	EF62	Good	System
[09:48:50:083]  	1FFA2	1FFEF	000A	000A	Good	Speedometer
[09:48:50:095]  Requesting operating system ID...
[09:48:50:106]  TX: STPX H:6C10F0, R:1, D:3C0A
[09:49:01:143]  Empty response to STPX with data. That's not OK.
[09:49:01:153]  Send failed. Attempt #1
[09:49:01:160]  TX: STPX H:6C10F0, R:1, D:3C0A
[09:49:12:195]  Empty response to STPX with data. That's not OK.
[09:49:12:208]  Send failed. Attempt #2
[09:49:12:217]  Operating system request failed, checking for a live kernel...
[09:49:12:226]  TX: STPX H:6C10F0, R:1, D:3D00
[09:49:23:263]  Empty response to STPX with data. That's not OK.
[09:49:23:372]  TX: STPX H:6C10F0, R:1, D:3D00
[09:49:34:410]  Empty response to STPX with data. That's not OK.
[09:49:34:533]  TX: STPX H:6C10F0, R:1, D:3D00
[09:49:45:569]  Empty response to STPX with data. That's not OK.
[09:49:45:684]  TX: STPX H:6C10F0, R:1, D:3D00
[09:49:56:719]  Empty response to STPX with data. That's not OK.
[09:49:56:827]  TX: STPX H:6C10F0, R:1, D:3D00
[09:50:07:862]  Empty response to STPX with data. That's not OK.
[09:50:07:971]  Checking for recovery mode...
[09:50:07:979]  TX: STPX H:6C10F0, R:1, D:62
[09:50:19:016]  Empty response to STPX with data. That's not OK.
[09:50:19:023]  Unable to send recovery query message. Attempt #1
[09:50:19:034]  TX: STPX H:6C10F0, R:1, D:62
[09:50:30:069]  Empty response to STPX with data. That's not OK.
[09:50:30:076]  Unable to send recovery query message. Attempt #2
[09:50:31:114]  Timeout during receive.
[09:50:31:122]  TX: STPX H:6C10F0, R:1, D:62
[09:50:42:159]  Empty response to STPX with data. That's not OK.
[09:50:42:168]  Unable to send recovery query message. Attempt #1
[09:50:42:175]  TX: STPX H:6C10F0, R:1, D:62
[09:50:53:210]  Empty response to STPX with data. That's not OK.
[09:50:53:218]  Unable to send recovery query message. Attempt #2
[09:50:54:249]  Timeout during receive.
[09:50:54:254]  TX: STPX H:6C10F0, R:1, D:62
[09:51:05:284]  Empty response to STPX with data. That's not OK.
[09:51:05:288]  Unable to send recovery query message. Attempt #1
[09:51:05:291]  TX: STPX H:6C10F0, R:1, D:62
[09:51:16:322]  Empty response to STPX with data. That's not OK.
[09:51:16:325]  Unable to send recovery query message. Attempt #2
[09:51:17:356]  Timeout during receive.
[09:51:17:359]  TX: STPX H:6C10F0, R:1, D:62
[09:51:28:389]  Empty response to STPX with data. That's not OK.
[09:51:28:398]  Unable to send recovery query message. Attempt #1
[09:51:28:403]  TX: STPX H:6C10F0, R:1, D:62
[09:51:39:434]  Empty response to STPX with data. That's not OK.
[09:51:39:438]  Unable to send recovery query message. Attempt #2
[09:51:40:468]  Timeout during receive.
[09:51:40:472]  TX: STPX H:6C10F0, R:1, D:62
[09:51:51:503]  Empty response to STPX with data. That's not OK.
[09:51:51:506]  Unable to send recovery query message. Attempt #1
[09:51:51:509]  TX: STPX H:6C10F0, R:1, D:62
[09:52:02:540]  Empty response to STPX with data. That's not OK.
[09:52:02:543]  Unable to send recovery query message. Attempt #2
[09:52:03:573]  Timeout during receive.
[09:52:03:576]  TX: STPX H:6C10F0, R:1, D:62
[09:52:14:607]  Empty response to STPX with data. That's not OK.
[09:52:14:611]  Unable to send recovery query message. Attempt #1
[09:52:14:615]  TX: STPX H:6C10F0, R:1, D:62
[09:52:25:646]  Empty response to STPX with data. That's not OK.
[09:52:25:650]  Unable to send recovery query message. Attempt #2
[09:52:26:681]  Timeout during receive.
[09:52:26:685]  TX: STPX H:6C10F0, R:1, D:62
[09:52:37:719]  Empty response to STPX with data. That's not OK.
[09:52:37:722]  Unable to send recovery query message. Attempt #1
[09:52:37:725]  TX: STPX H:6C10F0, R:1, D:62
[09:52:48:756]  Empty response to STPX with data. That's not OK.
[09:52:48:760]  Unable to send recovery query message. Attempt #2
[09:52:49:790]  Timeout during receive.
[09:52:49:793]  TX: STPX H:6C10F0, R:1, D:62
[09:53:00:824]  Empty response to STPX with data. That's not OK.
[09:53:00:827]  Unable to send recovery query message. Attempt #1
[09:53:00:831]  TX: STPX H:6C10F0, R:1, D:62
[09:53:11:862]  Empty response to STPX with data. That's not OK.
[09:53:11:866]  Unable to send recovery query message. Attempt #2
[09:53:12:894]  Timeout during receive.
[09:53:12:898]  TX: STPX H:6C10F0, R:1, D:62
[09:53:23:928]  Empty response to STPX with data. That's not OK.
[09:53:23:933]  Unable to send recovery query message. Attempt #1
[09:53:23:939]  TX: STPX H:6C10F0, R:1, D:62
[09:53:34:970]  Empty response to STPX with data. That's not OK.
[09:53:34:973]  Unable to send recovery query message. Attempt #2
[09:53:36:001]  Timeout during receive.
[09:53:36:004]  TX: STPX H:6C10F0, R:1, D:62
[09:53:47:034]  Empty response to STPX with data. That's not OK.
[09:53:47:037]  Unable to send recovery query message. Attempt #1
[09:53:47:040]  TX: STPX H:6C10F0, R:1, D:62
[09:53:58:071]  Empty response to STPX with data. That's not OK.
[09:53:58:074]  Unable to send recovery query message. Attempt #2
[09:53:59:103]  Timeout during receive.
[09:53:59:107]  PCM is not responding to OSID, kernel version, or recovery mode checks.
[09:53:59:110]  Unlock may not work, but we'll try...
[09:53:59:114]  Suppressing VPW chatter.
[09:53:59:117]  TX: STPX H:6CFEF0, R:1, D:2800
[09:54:10:149]  Empty response to STPX with data. That's not OK.
[09:54:10:152]  Sending 'test device present' notification.
[09:54:10:155]  Setting timeout for Minimum, 0 ms.
[09:54:10:158]  TX: AT ST 01
[09:54:21:163]  Did not recieve expected response.  does not equal OK
[09:54:21:167]  TX: STPX H:8CFEF0, R:0, D:3F
[09:54:32:174]  Setting timeout for ReadProperty, 25 ms.
[09:54:32:174]  TX: AT ST 06
[09:54:43:202]  Did not recieve expected response.  does not equal OK
[09:54:44:228]  Timeout during receive.
[09:54:44:340]  Sending seed request.
[09:54:44:343]  TX: STPX H:6C10F0, R:1, D:2701
[09:54:55:375]  Empty response to STPX with data. That's not OK.
[09:54:55:375]  Unable to send seed request message. Attempt #1
[09:54:55:375]  TX: STPX H:6C10F0, R:1, D:2701
[09:55:06:402]  Empty response to STPX with data. That's not OK.
[09:55:06:407]  Unable to send seed request message. Attempt #2
[09:55:06:411]  TX: STPX H:6C10F0, R:1, D:2701
[09:55:17:443]  Empty response to STPX with data. That's not OK.
[09:55:17:447]  Unable to send seed request message. Attempt #3
[09:55:17:450]  TX: STPX H:6C10F0, R:1, D:2701
[09:55:28:484]  Empty response to STPX with data. That's not OK.
[09:55:28:488]  Unable to send seed request message. Attempt #4
[09:55:28:492]  TX: STPX H:6C10F0, R:1, D:2701
[09:55:39:526]  Empty response to STPX with data. That's not OK.
[09:55:39:530]  Unable to send seed request message. Attempt #5
[09:55:39:533]  TX: STPX H:6C10F0, R:1, D:2701
[09:55:50:564]  Empty response to STPX with data. That's not OK.
[09:55:50:567]  Unable to send seed request message. Attempt #6
[09:55:50:571]  TX: STPX H:6C10F0, R:1, D:2701
[09:56:01:604]  Empty response to STPX with data. That's not OK.
[09:56:01:608]  Unable to send seed request message. Attempt #7
[09:56:01:611]  TX: STPX H:6C10F0, R:1, D:2701
[09:56:12:642]  Empty response to STPX with data. That's not OK.
[09:56:12:645]  Unable to send seed request message. Attempt #8
[09:56:12:649]  TX: STPX H:6C10F0, R:1, D:2701
[09:56:23:681]  Empty response to STPX with data. That's not OK.
[09:56:23:681]  Unable to send seed request message. Attempt #9
[09:56:23:682]  TX: STPX H:6C10F0, R:1, D:2701
[09:56:34:710]  Empty response to STPX with data. That's not OK.
[09:56:34:710]  Unable to send seed request message. Attempt #10
[09:56:34:710]  Unable to send seed request.
[09:56:34:724]  Unlock was not successful.

[Gampy]

[09:09:00:854] 0x0FFC00 99% 00:01
[09:09:00:864] Read complete.
[09:09:00:875] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[09:09:00:892] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.

Says it completed a 1m read successfully, no retries ...
Why the CRC failed is unknown with out further investigation.

Do you have the full Debug log for this read??
if you do, can you either PM it to me or post it as an attachment ... (it's to big paste into a post)

As for the Test Write ... Maybe it all needs to get power cycled, a read was just accomplished, it also gets the OsID and apparently did so successfully, so the PCM appears to be responding.

At least that's what I see.

[antus]

you were not in boot recovery mode, for the flash you'll need to jump the pin to crash it and cause it to reboot in recovery, then you'll see A0 A1 or A2 responses coming back meaning its ready for a load and pcmhammer will throw some errors as it tries to flash normally, but it will then fall back to recovery flash and should flash normally

for the read size - my mistake. I was thinking 512mbyte was FFFFFF and 1mbyte was 1FFFFFF but mental fail 512mb is 7 FF FF FF and 1mbyte is F FF FF FF

[Gampy]

Antus, that's better, you had me questioning my sanity! (and yes that probably needs to happen, but not over this)

And to make it clear for others ...

Code: Select all

  FFFFF - FFC00 = 3FF

FFC00 is the last packet of a 1m read at 1024b per packet.

Pin short should not be necessary.
If it can read it, it should be able to write to it ... It read it, successfully!

[vvise]

I'm trying to collect more data for you guys but I'm having some issues. I rebooted everything and afterwards I had a hard time initializing the device in PCM Hammer. Finally have it connected but now I can't even get a Read Properties to work.

Code: Select all

[11:06:06:992]  PCM Hammer 014
[11:06:08:413]  Voltage: 12.2V
[11:06:08:448]  Elm ID: ELM327 v1.4b
[11:06:08:494]  ScanTool device ID: STN2255 v5.5.3
[11:06:17:411]  VIN query failed: Timeout

Code: Select all

[11:06:06:992]  PCM Hammer 014
[11:06:06:993]  ElmDevice initialization starting.
[11:06:07:293]  TX: 
[11:06:07:304]  TX: AT Z
[11:06:08:344]  ELM327 v1.4b
[11:06:08:345]  TX: AT E0
[11:06:08:365]  AT E0  OK
[11:06:08:365]  TX: AT S0
[11:06:08:381]  OK
[11:06:08:382]  TX: AT RV
[11:06:08:413]  Voltage: 12.2V
[11:06:08:414]  TX: AT I
[11:06:08:448]  Elm ID: ELM327 v1.4b
[11:06:08:449]  Initializing PcmHacking.AllProDeviceImplementation
[11:06:08:449]  TX: AT #1
[11:06:08:486]  This is not an AllPro device.
[11:06:08:487]  Determining whether PcmHacking.ScanToolDeviceImplementation is connected.
[11:06:08:487]  TX: ST I
[11:06:08:494]  ScanTool device ID: STN2255 v5.5.3
[11:06:08:495]  TX: AT ST FF
[11:06:08:504]  OK
[11:06:08:504]  TX: AT AL
[11:06:08:517]  OK
[11:06:08:518]  TX: AT SP2
[11:06:08:525]  OK
[11:06:08:525]  TX: AT DP
[11:06:08:543]  SAE J1850 VPW
[11:06:08:543]  TX: AT AR
[11:06:08:552]  OK
[11:06:08:553]  TX: AT AT0
[11:06:08:570]  OK
[11:06:08:570]  TX: AT SR F0
[11:06:08:581]  OK
[11:06:08:582]  TX: AT H1
[11:06:08:594]  OK
[11:06:08:594]  TX: AT ST 20
[11:06:08:611]  OK
[11:06:16:174]  TX: STPX H:6C10F0, R:1, D:3C01
[11:06:17:411]  Empty response to STPX with data. That's not OK.
[11:06:17:411]  VIN query failed: Timeout
[11:06:17:412]  TX: STPX H:6C10F0, R:1, D:20
[11:06:18:614]  Empty response to STPX with data. That's not OK.

Can someone confirm what I should be trying. I have the ODBLinkMX+ bluetooth connected to my PC. I tried grounding the pin to the negative on my bench harness for 1 second followed by a short wait, then I tried to re-initialize the device. No change. I tried the same thing but then pressing Read Properties, also nothing.

How do I force the device to boot in recovery?

[antus]

you have it all set up and running ready to read then you bridge the pin between the red marks and one of the ground points momentarily. A couple are marked with black Xs, you can identify them as looking like pads but they are connected to large solid areas of the PCB. Then you begin the read or write. This pulls address pin 17 (I think? from memory?) low for a moment which is enough to crash the pcm, cause it to fail to see the calibration or OS signature which means it thinks its unprogrammed, and the address is high enough that the boot block (at the beginning of the chip) is ok to function without interruption which allows the boot mode code to continue running until the flash begins.