Page 54 of 97
Re: PCM Hammer - new ls1 flash tool
Posted: Tue Nov 26, 2019 4:48 pm
by NSFW
This is a little embarrassing, but there's a bug in release 7 that prevents it from reading from P59s.
The fix is...
1) del read-kernel.bin
2) copy write-kernel.bin read-kernel.bin
In other words, write-kernel.bin works for both reading and writing.
The P59 requires a small change in the kernel, and I only made that change in the write kernel, because I forgot that we had two kernels, Because the write kernel does work for both reading and writing. We just weren't using for reading.
I'll put out another release that just has a single "kernel.bin" to simplify things.
It will also verify what gets read, just to be sure that nothing was garbled in transit. I'm working on that now.
Re: PCM Hammer - new ls1 flash tool
Posted: Tue Nov 26, 2019 5:24 pm
by Gampy
And let the floggings begin ... Naw, just can't do that, it happens to the best!
Shit happens!
Re: PCM Hammer - new ls1 flash tool
Posted: Tue Nov 26, 2019 5:55 pm
by NSFW
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 8:46 am
by I420tom
Just joined this forum now
NSFW shared a link here to my post in his ls1tech thread, helping him recover with bdm jtag his p59 amd
I'm trying to help with pcm hammer.
I've been testing 2 p59 Intel flash pcms in car.
So far read stops at 512kb
How can I help further?
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 9:48 am
by DavidBraley
I420tom,
I wanted to thank you for figuring out the fix getting the BDM to read and write to the P59's! I'm now reading and writing to both Intel and AMD based P59's
I've offered to send NSFW an Intel based P59 if it helps too!
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 9:56 am
by Monaro
I have updated to PCM release 8, and have tried twice on a P59 - and read stops at 62% - this has pcm has previously read perfectly with release 6. Using J2534
Seems to be 2 spots where an error appears in debug - read is perfect from 1 to 62%
Have done a quick compare with previous bin file read and appears ok. It's an AMD chip.
Read on bench - as was compare bin file.
Of note - have just readthe same P59 PCM on my laptop as it has Release 6 still on it and that read properly.
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 9:58 am
by Gampy
I420tom wrote:Just joined this forum now
NSFW shared a link here to my post in his ls1tech thread, helping him recover with bdm jtag his p59 amd
I'm trying to help with pcm hammer.
I've been testing 2 p59 Intel flash pcms in car.
So far read stops at 512kb
How can I help further?
Yup, I'd like to say Thank you as well!
It might be helpful if you were to create a debug log and attach it.
[edit]
Are these in vehicle reads that are failing?
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 10:53 am
by Monaro
I420tom wrote:Just joined this forum now
NSFW shared a link here to my post in his ls1tech thread, helping him recover with bdm jtag his p59 amd
I'm trying to help with pcm hammer.
I've been testing 2 p59 Intel flash pcms in car.
So far read stops at 512kb
How can I help further?
FYI Checked my debug afile gainst your error message posted on LS1tech - exactly the same - mine has the AMD chip though.
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 11:17 pm
by Tazzi
Monaro wrote:I have updated to PCM release 8, and have tried twice on a P59 - and read stops at 62% - this has pcm has previously read perfectly with release 6. Using J2534
Seems to be 2 spots where an error appears in debug - read is perfect from 1 to 62%
Have done a quick compare with previous bin file read and appears ok. It's an AMD chip.
Read on bench - as was compare bin file.
Of note - have just readthe same P59 PCM on my laptop as it has Release 6 still on it and that read properly.
Can you please upload the full log in?
I see something interesting appear on your error at 62%:
Code: Select all
[10:08:54:174] Reading from 659456 / 0xA1000, length 4096 / 0x1000
[10:08:54:174] TX: 6D 10 F0 35 01 10 00 0A 10 00
[10:08:56:264] ReadMsgs OBDError: STATUS_NOERROR
When it read the message, it got back a STATUS_NOERROR message which should indicate its received a frame but proceeds on.
Im logging with my nano right now and it doesnt do that at all.
Im wondering if theres some sort of fault settin and the nano is dropping to 1x.. then actually sending a command back to software which we are not processing correctly maybe.
Re: PCM Hammer - new ls1 flash tool
Posted: Wed Nov 27, 2019 11:26 pm
by Tazzi
Actually, I believe I see the problem there.
Ok.. so I just did a full read (On bench) and took only 4:30sec (not including the 30seconds done calculating CRCs at the end).
Whereas looking at your log... it took 5mins just to get to 62%.
When looking at the timestamps between each block for me, here is about a 1second difference. Im almost certain you are running at 1x and not 4x so you will likely have a 3-4sec difference?
Now looking back at your log:
Code: Select all
10:03:49:472] Attempting switch to VPW 4x
[10:03:49:477] TX: 6C FE F0 A0
[10:03:49:507] RX: 6C F0 10 E0 AA
[10:03:49:507] Parsing 6C F0 10 E0 AA
[10:03:49:507] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[10:03:49:512] Sending 'test device present' notification.
[10:03:49:512] TX: 8C FE F0 3F
[10:03:51:523] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:03:51:523] Sending 'test device present' notification.
[10:03:51:523] TX: 8C FE F0 3F
[10:03:51:528] TX: 6C FE F0 A1
[10:03:53:539] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[10:03:53:539] J2534 setting VPW 4X
[10:03:53:664] Sending 'test device present' notification.
[10:03:53:664] TX: 8C FE F0 3F
[10:03:53:669] Sending 'test device present' notification.
[10:03:53:669] TX: 8C FE F0 3F
Theres a 2second gap between tester present frames, so I am wondering if thats long enough to cause it to drop out of 4x mode.