PCM Hammer P04 Support Project

[darkman5001]

The P04 Aurora PCM will not read. Here are the logs.

PcmHammer_debugLog_20230314@191115.txt

PcmHammer_userLog_20230314@191053.txt

The kernel is to big for this VCI ...

That is the problem with the P04, it will only accept the kernel in one single packet ... This VCI is breaking it into two packets!
Or more properly stated PcmHammer is splitting it so this VCI can handle it ...

-Enjoy

Gampy, are you saying kernel is too big for his tool meaning too big for his ELM 327 adapter that he is using to connect with?

[antus]

I guess we need a way to flag the kernel can not be split, and a check on if it will be split, so we can abort with an error if the interface is too small. That should be reasonably easy to add for now. Then while we can keep developing p04 support if anyone can start looking in to implementing the loader kernel that can handle a split kernel, and ideally fit it in 512bytes (not likely?) it'd be great to tick that off the list and mean more interfaces can be supported with P04.

edit: just saw your post. Im not gampy but yes, the read kernel does not fit in one packet with that allpro, so its split. P01/P59/P10/P12 can handle this. P04 cannot. Write kernel, and/or flash chip id read kernel will be larger again.

[darkman5001]

So far, I have been able to successfully read three P04 PCMs using 4x High Speed enabled with no issues after some modifications to PCM Hammer. I am using a GM MDI2 J2534 to read these. Currently Intel P04s read 4x times faster at 2048 block size while AMDs currently reading a block size of 512. I have compared their bins with reads I did using Jet Tuners on the same PCMs and the bins matched 100%. Here are some logs and the bins pulled using PCM Hammer. I would like those with access to some P04s to test give me your OSIDs and which flash chip it has so I can send you a test version to see how your P04 reacts. Let me know any input you may have. Thanks.

[Cincinnatus]

I have a p04. Tried reading it in past unsuccessfully. Is the new version of pcmhammer capable now, or is this someone's beta?

[darkman5001]

I have a p04. Tried reading it in past unsuccessfully. Is the new version of pcmhammer capable now, or is this someone's beta?

It is neither. It's just developing in the works so only a test version, and can only read at the time. Do you know your OSID and what flash chip is in the PCM? I can add yours in and send you a version to test. Also which tool are using to connect to the PCM? We are learning with the P04 that some adapters may have issues completing the successful reads due to differences in tool memory which will have to be addressed.

[Gampy]

We are learning with the P04 that some adapters may have issues completing the successful reads due to differences in tool memory which will have to be addressed.

'We' are not learning the P04 cannot handle multiple packets, 'we' have known this for several years, that is why the P04 was pushed aside. See here: V6 ability for pcm hammer

The P04 is going to take a m68k assembly programmer to duplicate what we have in C, or create a tiny tiny loader kernel (3600/3680) that can then take a larger C kernel on board.

And then, PCMHammer itself is going to need to be re-written to handle this loader kernel loading the full kernel.

Then there is the issue with the E54, another VPW PCM that is basically like the P01/P59 except it only has 5,296 (0x14B0) bytes of continuous memory ...

So the real solution is to just do the kernel in assembly ... Because C is just to bloated!

-Enjoy

[Cincinnatus]

Here was my attempt with my vcx nano.

[02:27:48:037] PCM Hammer - TEST BUILD 018-824-9.1 (8/5/2021, 3:52 AM)
[02:27:48:037] Initializing J2534 Device
[02:27:48:069] Loaded DLL. (Success)
[02:27:50:631] Connected to the device. (Success)(0x00000000)
[02:27:50:662] Battery Voltage is: 12.354
[02:27:52:053] Protocol Set
[02:27:52:100] Device initialization complete.
[02:27:57:725] TX: 6C 10 F0 3C 01
[02:27:57:788] RX: 6C F0 10 7C 01 00 31 47 32 57 52
[02:27:57:788] TX: 6C 10 F0 3C 02
[02:27:57:850] RX: 6C F0 10 7C 02 35 32 31 38 58 46
[02:27:57:850] TX: 6C 10 F0 3C 03
[02:27:57:897] RX: 6C F0 10 7C 03 32 30 39 31 37 36
[02:27:57:897] VIN: 1G2WR5218XF209176
[02:27:57:913] TX: 6C 10 F0 3C 0A
[02:27:57:975] RX: 6C F0 10 7C 0A 00 F7 D9 52
[02:27:57:975] OS ID: 16243026
[02:27:57:975] TX: 6C 10 F0 3C 08
[02:27:58:100] RX: 6C F0 10 7C 08 00 F7 D6 58
[02:27:58:100] Calibration ID: 16242264
[02:27:58:116] TX: 6C 10 F0 3C 04
[02:27:58:179] RX: 6C F0 10 7C 04 00 8E C8 80
[02:27:58:179] Hardware ID: 9357440
[02:27:58:179] TX: 6C 10 F0 3C 05
[02:27:58:257] RX: 6C F0 10 7C 05 32 44 37 32
[02:27:58:257] TX: 6C 10 F0 3C 06
[02:27:58:319] RX: 6C F0 10 7C 06 54 51 38 32
[02:27:58:319] TX: 6C 10 F0 3C 07
[02:27:58:382] RX: 6C F0 10 7C 07 34 30 FC EE
[02:27:58:382] Serial Number: 2D72TQ8240
[02:27:58:397] TX: 6C 10 F0 3C 14
[02:27:58:460] RX: 6C F0 10 7F 3C 14 31
[02:27:58:460] Received an unexpected response. Attempt #1, status UnexpectedResponse.
[02:28:00:476] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[02:28:00:476] Sending 'test device present' notification.
[02:28:00:476] TX: 8C FE F0 3F
[02:28:02:491] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[02:28:02:491] Sending 'test device present' notification.
[02:28:02:491] TX: 8C FE F0 3F
[02:28:04:507] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[02:28:04:507] Sending 'test device present' notification.
[02:28:04:507] TX: 8C FE F0 3F
[02:28:06:523] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[02:28:06:523] Sending 'test device present' notification.
[02:28:06:523] TX: 8C FE F0 3F
[02:28:08:539] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[02:28:08:539] Receive timed out. Attempt #6, Timeout #5.

[Thorwon]

The P04 Aurora PCM will not read. Here are the logs.

PcmHammer_debugLog_20230314@191115.txt

PcmHammer_userLog_20230314@191053.txt

The kernel is to big for this VCI ...

That is the problem with the P04, it will only accept the kernel in one single packet ... This VCI is breaking it into two packets!
Or more properly stated PcmHammer is splitting it so this VCI can handle it ...

-Enjoy

So what would be a VCI that will handle the kernel in one package?

I would like to find one that doesn't break the bank.

[Gampy]

Truth is, there isn't any, that would require a buffer something along the lines of 8192 bytes ...

However,

Any VCI that can handle 2048 bytes or more is what is needed to handle the current whittled down P04 kernel.
The Allpro is only good for 1024 bytes.

Most real J2534 VCI's will do at least 2048 bytes, most ScanTool (STN) VCI's will do at least 2048 bytes.

Many use the VxDiag VCX Nano, I personally do not like it!
I have a GM MDI w/WiFi clone from obd2tools.com, it does it's job and it will handle 4096 byte packets. Find it here: GM MDI w/WiFi
I also have a OBDII UART from Sparkfun (it's a ScanTool (STN1110) chipped unit) it works well and handles 2048 bytes.

The GM MDI II has the smallest that I know of in the J2534 world and it's limited to 2048 bytes, I do not know the limits of the VCX Nano, I'm sure it handles at least 2048 bytes.

There are other choices ... Maybe someone will chime in with their picks.

Cincinnatus,
I would not expect the "Properties" to work at this time, NOTHING has been done there for the P04!
Please try a read.

BTW, you have an interesting PcmHammer version ...

-Enjoy

[Cincinnatus]

I've been reading Gampy. Not sure what the "properties" are. That version was when I couldn't get the Microsoft store version to work and you so kindly sent me a test version so we could figure out why.