pcmhacking.net

hashtagfacts wrote:

NSFW wrote:This adds OS ID 12601904 to the list of known 1mb P12 operating systems.

12589586 is also apart of the p12 line up, can I get a copy of a bin with 12601904 to try and update my os?

Its up above, however i highly recommend not switching over to this OS unless your on a bench with recovery tools.. IF you have a different slave than what this vin calls for on TIS2WEB you will end up with a brick..

darkman5001 wrote:When selecting "Read Properties" there is about a 20 second delay and then it comes back with "Hardware ID Query Failed".

Well throw me in the pit and drag me over the coals for I have proof of failure in testing, yet failed to silence it!

antus wrote:I took it out on one of the test builds, but it was missed in the development branch that turned in to 021.

I added it back and excluded the P12, and as stated above, forgot to exclude the P10.
Now I kinda wish I had added a special case parser for I am curious as to what is returned on other (P10,P12) units, the logs I have show 3C 04 Returns,
. . P10 = 31 38 36
. . P12 = 33 38 36
. . P12b = 30 38 36

hashtagfacts wrote:

NSFW wrote:This adds OS ID 12601904 to the list of known 1mb P12 operating systems.

12589586 is also apart of the p12 line up, can I get a copy of a bin with 12601904 to try and update my os?

My crystal ball shows a resolution to this missing OsID issue in the future ...

Gampy wrote:

antus wrote:I took it out on one of the test builds, but it was missed in the development branch that turned in to 021.

I added it back and excluded the P12, and as stated above, forgot to exclude the P10.
Now I kinda wish I had added a special case parser for I am curious as to what is returned on other (P10,P12) units, the logs I have show 3C 04 Returns,
. . P10 = 31 38 36
. . P12 = 33 38 36
. . P12b = 30 38 36

Ideally we'd parse a 3 or 4 byte response for hardware ID and display as decimal like we do for 4 byte responses but Im just not sure if its useful. If your going to leave it in for P01/P59 it might be best to extend it to support these responses.

[11:19:30:805] PCM Hammer (5/17/2022, 10:46 AM)
[11:19:30:820] Tuesday, May 17 2022 @11:19:30:82
[11:19:30:836] Initializing J2534 Device
[11:19:30:853] Loaded DLL
[11:19:33:419] Connected to the device.
[11:19:33:465] Battery Voltage is: 12.274
[11:19:34:232] Thanks for using PCM Hammer.
[11:19:37:393] VIN: 1GTCS146048136101
[11:19:37:502] OS ID: 12627885
[11:19:37:502] Hardware Type: P12
[11:19:37:596] Calibration ID: 12613418
[11:19:37:815] Serial Number: 6277KH05H
[11:19:37:908] Broad Cast Code: YPUY
[11:19:37:971] MEC: 0
[11:20:28:888] Will save to C:\Users\RAC\Documents\Bins\P12Colorado.bin
[11:20:30:577] Querying operating system of current PCM.
[11:20:30:687] OSID: 12627885
[11:20:30:952] Unlock succeeded.
[11:20:31:000] Attempting switch to VPW 4x
[11:20:31:078] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[11:20:36:151] Kernel upload 23% complete.
[11:20:36:729] Kernel upload 49% complete.
[11:20:37:325] Kernel upload 74% complete.
[11:20:37:888] Kernel upload 100% complete.
[11:20:40:061] Kernel Version: 0103050C
[11:20:40:061] kernel uploaded to PCM succesfully. Requesting data...
[11:20:40:155] Flash chip: AMD AM29BL162C, 2mb
[11:27:16:966] Read complete.
[11:27:16:981] All read-request messages succeeded on the first try. You have an excellent connection to the PCM.
[11:27:17:002] We're not sure how much retrying is normal for a read operation on a 1024kb PCM.
[11:27:17:011] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[11:27:17:019] Starting verification...
[11:27:17:051] Calculating CRCs from file.
[11:27:17:073] Initializing CRC algorithm on PCM, this will take a minute...
[11:27:17:216] Requesting CRCs from PCM.
[11:27:17:229] Range File CRC PCM CRC Verdict Purpose
[11:27:17:246] 1C0000-1FFFFF not needed not needed n/a OperatingSystem
[11:27:17:263] 180000-1BFFFF not needed not needed n/a OperatingSystem
[11:27:17:287] 140000-17FFFF not needed not needed n/a OperatingSystem
[11:27:17:304] 100000-13FFFF not needed not needed n/a OperatingSystem
[11:27:23:444] 0C0000-0FFFFF A8966194 A8966194 Same OperatingSystem
[11:27:29:475] 080000-0BFFFF 02D4F6D2 02D4F6D2 Same OperatingSystem
[11:27:35:401] 040000-07FFFF 8C50F801 8C50F801 Same Calibration
[11:27:40:655] 008000-03FFFF 3AFDDD34 3AFDDD34 Same Calibration
[11:27:40:972] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[11:27:41:299] 004000-005FFF FCCF22B9 FCCF22B9 Same Parameter
[11:27:41:799] 000000-003FFF D0828AD6 D0828AD6 Same Boot
[11:27:41:820] The contents of the file match the contents of the PCM.
[11:27:42:828] Clearing trouble codes.
[11:27:44:606] Clearing trouble codes.
[11:27:45:757] Elapsed time 00:07:14.8050125
[11:27:45:771] Saving contents to C:\Users\RAC\Documents\Bins\P12Colorado.bin

But the file says it's corrupted.

The Flash Chip identified as 'AMD AM29BL162C, 2mb' (P12b), that OsID (12627885) is configured as P12 1m, not P12b 2m!

Is 12627885 actually a 2mb OS?
Or was this a 1mb OS that somehow found its way onto a 2mb PCM?

I'm guessing it's a 2mb OS but I don't want to make any code changes until we know for sure.

@hashtagfacts can you post the bin? Also guessing its a 2mb file, might be able to tell by looking at the first half.

You can definitely tell the difference ...

I'm pretty sure PcmHammer cannot write a P12 (1m) file to a P12b (2m) pcm.

Can't confirm this, but 2 sources claim only 07 p12s were 2mb. That vin is an 04, but I don't know about the OS.

it is correct pcmhammer wont do it, but we dont know if something like winflash would. It seems unlikely, but it is possible.