PCM Hammer Release 021

[abs351]

Thanks Gumpy, for your feedback. i was going to attempt it but Antus has sent a revised PcmLibrary.DLL to address this matter.
So success with unlock but error still appears, please see attached log.
kernel error

VZ2.PNG (44.32 KiB) Viewed 3087 times

Is there anything in need to assist the matter?

[Gampy]

The PCM is failing to respond to a Mode 34 Request Permission to Upload.

Please do not hit Read Properties first, I have known for it to cause failures ...

Would you please try disabling 4x, then do a Read Entire PCM.
You can disable 4x in the Select Device dialog.

-Enjoy

[abs351]

Hello Gampy,

Thanks for the reply, I had done exactly your request and was able to retrieve the binary file, but I noticed that within PCMhammer there was a CRC error appearing once completed, but I assume this is normal as the RC will need to be recalculated? happy to share screen shots if in need.

I have loaded the binary in tuner Pro and was successfully able to see values to reflect such car example vin. I used the 12592433-metric.xdf as a stop gap. Next challenge is to find the 1273057 XDF file.
Which I doubt even exists!

I loaded into universal patcher and able to see parameters.
I'm new to the GM PCM tuning, I thought ill attempt this rather than looking at HPT Tuner application for the GM cars.

I'm sure there will be more questions, ill lodge them in another thread that's suitable.

Many thanks team for your help and Antus for his direct input for recompiling PCM hammer to include the OS 1273057.
ABS

[antus]

CRC error might be a problem depending what it is. If its a CRC error between the file and what the PCM saw then it is suspicious. Do post up a debug log.

[abs351]

Hi Antus,

i have performed another read and the same error appears.
do see attached, kindly share feedback if there is any assistance needed from my end?


Abs

[antus]

Ahh ok, thats fine. Its because its the latest development version of pcmhammer, but you are running the older standard version of the flash kernel. We changed how the CRCs work and you just found a bug we'll need to look at in the development version. But the read was fine. You can do a tools -> test file checksums and check the file that it wrote. It should come up OK. We'll have to look in to that issue before we release the next version, and we'll have to fix it before you'll be able to write.

[abs351]

Ahh ok, thats fine. Its because its the latest development version of pcmhammer, but you are running the older standard version of the flash kernel. We changed how the CRCs work and you just found a bug we'll need to look at in the development version. But the read was fine. You can do a tools -> test file checksums and check the file that it wrote. It should come up OK. We'll have to look in to that issue before we release the next version, and we'll have to fix it before you'll be able to write.

All good, thanks for the quick response. tested the checksum values, see below results.
[09:06:48:040] Validating 1024k file.
[09:06:48:043] Start End Stored Needed Verdict Segment Name
[09:06:48:043] 00000 FFFFD 91C0 91C0 Good Operating system
[09:06:48:059] 08002 162DF A4B6 A4B6 Good Engine calibration
[09:06:48:059] 162E2 1964F 63FF 63FF Good Engine diagnostics.
[09:06:48:059] 19652 1D8DF 9F48 9F48 Good Transmission calibration
[09:06:48:059] 1D8E2 1E1DF 0A7E 0A7E Good Transmission diagnostics
[09:06:48:075] 1E1E2 1F6EF 6CD5 6CD5 Good Fuel system
[09:06:48:075] 1F6F2 1FEDF 6C6D 6C6D Good System
[09:06:48:075] 1FEE2 1FFCF D1FF D1FF Good Speedometer
[09:06:48:090] All checksums are valid.

If there is any further testing, please reach out, I'm happy to assist where needed.

Abs

[Gampy]

Antus,

Is this one of your test builds ??

It appears to be a half baked new implementation of CRC, it's using an old C Kernel, yet new Assembly Kernel CRC technique.
That's a for sure failure, the new CRC technique will not wait on an old slow C Kernel ... It's in to much of a hurry and to impatient, just like the rest of this modern world!

If I knew what was done to resolve the previous unlock issue, I would build a current custom OsID build that should do abs351 up right and sweet ...

-Enjoy

[antus]

There was nothing done to fix the unlock, it just needed to be added as a definition so it didnt default to image size 0. Yes its the development build I was working on on my pc on the day I built it for him, before your branch with the CRC switch for both kernel types landed on github. We need to put this OSID in the main app, and I noticed this branch from plastic racer with some more P12 OSIDs too. https://github.com/LegacyNsfw/PcmHacks/ ... ks:develop We can probably add the P12 OSIDs and ABS351's to pcmhammer at the same time.

[Gampy]

Whaaaa Booo Hooo, I got deleted ...

Yea, I get it, it was a duplicate, just having fun.

-Enjoy