PCM Hammer P01 and P59 flash tool v015

[Holden202T]

ok this is starting to get a bit off topic!

[Gampy]

Actually it's getting a bit old ...

[TE27Levin]

Any one have any luck on a P01 full flash?

[Gampy]

I believe it works fine ... I have Os swapped before, but that was a bit ago.

I'll try it shortly, currently watching a Os swap on a Intel chipped P59!
Os swapped a AMD chipped P59 many many times in the last two days.

[edit]
And done ... Os swap on a Intel P59 accomplished!

[edit 2]
Done, Os swap on a P01 tested!
I am a bit ahead of Release 11, but the unit I tested on already had a Os swap on it, it had to be done in October or November, so Release 11 should do a full write on a P01 no problem.

[edit 3]
And swapped the P01 back to the Os I want on it ...

[edit 4]
Couple small (but important) bit's (x5) to fix for Intel and it's looking good.
I'm not on head, will pull shortly now that Intel is fingered and test on head.

[Gampy]

Write to Flash packet sizes over 1024 fail ...

A log,

[07:59:12:690] TX: STPX H:6D10F0, R:1, L:2057
[07:59:12:707] TX: 36000800080000 ... wacked.
[07:59:14:354] Empty response to STPX payload. That's not OK.
[07:59:14:354] Unexpected response to STPX payload:
[07:59:14:376] WritePayload: Unable to send message.
[07:59:14:377] TX: STPX H:6D10F0, R:1, L:2057
[07:59:14:753] Unexpected response to STPX header: STOPPED

DebugLog.txt

(82.39 KiB) Downloaded 203 times

[antus]

Hmmm that means we might need to change this:

Code: Select all

               else if (stID.Contains("STN1110") || // SparkFun OBD-II UART
                    stID.Contains("STN1150") || // MX version 1
                    stID.Contains("STN1151") || // MX version 2
                    stID.Contains("STN1155") || // LX
                    stID.Contains("STN2255"))   // MX+
                {
                    // 2048 works, but doesn't write measurably faster.
                    this.MaxSendSize = 1024 + 12;
                    this.MaxReceiveSize = 1024 + 12;
                }

Can you determine the max packet size it can handle?

[Gampy]

Naw that doesn't need changing, that works solid.

The smallest over 1024 (+12) I tried was 1536 (+12), it failed ... didn't see no point in finding the edge.

Since I started playing with the P04 I have been bumping the SparkFun up to 3000 Send (3002 MAX) and 2996 Receive (2998 MAX), it works awesome with that except for Flash Writes.
Surprisingly, that does increase the performance a bit, 1024 to 2048 does little for performance, but 1024 to 3k does make a nice difference. IIRC near 10 minutes for a 1m full read.

Not a big deal, just thought I would throw it out there.

And to be clear, Intel needs the same bit change as the AMD, but in 5 places ... Then I'd say HEAD is release ready.

Done much write testing over the last two days, P01, Intel and AMD P59 ... Full binary writes. (ie Cloning ... Os, Calibration, Parameters) With ZERO hickups!

[antus]

Awesome thanks for that. Im not sure why the interface would have said STOPPED, but the details are helpful. Im testing on a GM MDI, OBD Pro (beta) and sometimes on AVT though I know that device has issues at the moment. I do have a scantool, but I kinda hate that interface and have my hands full with the others I dont want to name anyone but someone else will probably look at it if they can reproduce the problem on a PCM they do have.

[Gampy]

Just read a post from NSFW here where he mentions the AVT not working now, the AVT is 4x.

My (I hear others complaining as well) Allpro fails miserably with 4x on, turn it off and it works like a champ, albeit a bit slow ... The Allpro used to work awesome in 4x!

For you that have an Allpro (or 4x device that errors) and want to try with 4x off, you can edit the file PcmHammer.exe.Config in the PcmHammer directory and disable 4x, see example below.

Code: Select all

  <appSettings>
    <add key="DeviceCategory" value="Serial" />
    <add key="J2534DeviceType" />
    <add key="SerialPort" value="COM3" />
    <add key="SerialPortDeviceType" value="ObdLink or AllPro" />
    <add key="Enable4xReadWrite" value="False" />
  </appSettings>

Enable4xReadWrite ... If it's not there, add it.

I do have a Options menu PR, just have not pushed it up yet, the Full Write release is priority to me.
I've done all the Full .bin Write testing I'm going to do, so maybe I'll cleanup the Menu PR and push it up, it is just a base to grow on with only "Enable 4x ReadWrite" currently.

[Gampy]

Whoops, it's a new case with the last round of commits.

Code: Select all

        /// <summary>
        /// Calculate the checksum for a given block of VPW data.
        /// </summary>
-        public static UInt16 CalcBlockChecksum(byte[] block)
+        public static UInt16 CalcBlockChecksum(byte[] Block)
        {
            UInt16 Sum = 0;

            for (int i = 4; i < Block.Length - 2; i++) // start after prio, dest, src, mode, stop at end of payload
            {
-                Sum += block[i];
+                Sum += Block[i];
            }

            return Sum;
        }