PCM Hammer Release 021
-
- Posts: 6
- Joined: Fri May 14, 2021 3:01 am
Re: PCM Hammer Release 021
Recover and try again.
Curious about your recovery technique?
Curious about your recovery technique?
- antus
- Site Admin
- Posts: 8250
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
"Unable to erase flash memory: Error"
This is usually a problem with low voltage or a noisy power supply. This happens on the other types of PCMs too. Try a bigger / slightly higher voltage power supply. If you dont have one try a car battery. Phone chargers / wall warts etc often dont work well enough for a write, though you'll get a read.
That second fail, I am not sure what that means. I'll ping NSFW and see if he can help.
This is usually a problem with low voltage or a noisy power supply. This happens on the other types of PCMs too. Try a bigger / slightly higher voltage power supply. If you dont have one try a car battery. Phone chargers / wall warts etc often dont work well enough for a write, though you'll get a read.
That second fail, I am not sure what that means. I'll ping NSFW and see if he can help.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: PCM Hammer Release 021
My recovery was posted in the p12 development thread I believe, but have to remove back cover and flash the chip directly.Festus Hagen wrote:Recover and try again.
Curious about your recovery technique?
-
- Posts: 6
- Joined: Fri May 14, 2021 3:01 am
Re: PCM Hammer Release 021
If I’m understanding correctly the failure in the 2nd log is because the PCM is no longer responding!antus wrote:"That second fail, I am not sure what that means. I'll ping NSFW and see if he can help.
Note the OsID command (3C0A) failure, pretty sure it’s the first comms to pcm.
I suspect it’s because pcmhammer has an erase/write order failure on full writes, it should do the calibration segment first, if it succeeds, then continue with the rest of the segments.
It’s easier to recover a Calibration write failure.
- antus
- Site Admin
- Posts: 8250
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
This is not quite right. You can see it CRC-16s the segments and only the calibration segments have changed. So it would be erasing calibration only. But the erase fails, so the pcm should be untouched. If it is bad, then it would only be the calibration would be partly erased.
The erase happen to blocks that have changes only, starting at the end, and working back towards the boot sector. The idea is for the boot sector to be erased the other segments need to succeed. This logic works for the P01 and the P59, but I dont know how P10/P12/P12a boot sectors work and if they have the same recovery potential as the earlier ones. You can see the erase request at [01:44:26:289] TX: 6C 10 F0 3D 05 02 00 00 where the 3D is kernel, the 05 is erase, and its erasing sector starting at 02 00 00, which is calibration. But annoyingly, the calibration in the P12 doesnt map to the hardware sectors, so the erase actually starts a little earlier at the end of the OS because it has to due to hardware limitations. But it still doesnt touch the boot sector. In the file engine calibration starts at 2052C, but we have a [01:44:51:794] Flash chip: AMD AM29BL802C, 1mb, and we can see the hardware sectors we can possibly erase here: https://github.com/LegacyNsfw/PcmHacks/ ... ip.cs#L167 (note 16 bit addressing, so multiply by 2 to get 8 bit addresses like we normally deal with.. this is because the chips are in 16bit mode and this is the addresses fed to the hardware)
They dont 1:1 line up like the P01 and P59.
[01:45:09:179] Trying P12 1Mb
[01:45:09:179] Start End Stored Needed Verdict Segment Name
[01:45:09:205] 00000 03FFF 15DD 15DD Good Boot Block
[01:45:09:234] 08002 FFFFF F437 F437 Good OS
[01:45:09:261] 2052C 3261B 8B96 8B96 Good Engine Calibration
[01:45:09:292] 3261E 36FF5 5655 5655 Good Engine Diagnostics
[01:45:09:331] 36FF8 3F117 FAAA FAAA Good Transmission Calibration
[01:45:09:359] 3F11A 3FFFB F5E8 F5E8 Good Transmission Diagnostics
[01:45:09:398] 20002 20087 3037 3037 Good Speedometer
[01:45:09:429] 2008A 20529 96EE 96EE Good System
The erase happen to blocks that have changes only, starting at the end, and working back towards the boot sector. The idea is for the boot sector to be erased the other segments need to succeed. This logic works for the P01 and the P59, but I dont know how P10/P12/P12a boot sectors work and if they have the same recovery potential as the earlier ones. You can see the erase request at [01:44:26:289] TX: 6C 10 F0 3D 05 02 00 00 where the 3D is kernel, the 05 is erase, and its erasing sector starting at 02 00 00, which is calibration. But annoyingly, the calibration in the P12 doesnt map to the hardware sectors, so the erase actually starts a little earlier at the end of the OS because it has to due to hardware limitations. But it still doesnt touch the boot sector. In the file engine calibration starts at 2052C, but we have a [01:44:51:794] Flash chip: AMD AM29BL802C, 1mb, and we can see the hardware sectors we can possibly erase here: https://github.com/LegacyNsfw/PcmHacks/ ... ip.cs#L167 (note 16 bit addressing, so multiply by 2 to get 8 bit addresses like we normally deal with.. this is because the chips are in 16bit mode and this is the addresses fed to the hardware)
They dont 1:1 line up like the P01 and P59.
[01:45:09:179] Trying P12 1Mb
[01:45:09:179] Start End Stored Needed Verdict Segment Name
[01:45:09:205] 00000 03FFF 15DD 15DD Good Boot Block
[01:45:09:234] 08002 FFFFF F437 F437 Good OS
[01:45:09:261] 2052C 3261B 8B96 8B96 Good Engine Calibration
[01:45:09:292] 3261E 36FF5 5655 5655 Good Engine Diagnostics
[01:45:09:331] 36FF8 3F117 FAAA FAAA Good Transmission Calibration
[01:45:09:359] 3F11A 3FFFB F5E8 F5E8 Good Transmission Diagnostics
[01:45:09:398] 20002 20087 3037 3037 Good Speedometer
[01:45:09:429] 2008A 20529 96EE 96EE Good System
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: PCM Hammer Release 021
I believe I have already set my power supply up to 13.5v but I’ll double check and try again
-
- Posts: 6
- Joined: Fri May 14, 2021 3:01 am
Re: PCM Hammer Release 021
I have multiple bench top variable power supplies that do not work ...
Seems I’ve made a life full of bad decisions!
Seems I’ve made a life full of bad decisions!
- antus
- Site Admin
- Posts: 8250
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
Its not just voltage, its also electrical noise. Best to try another power source to rule it out. Battery is best because its a DC source, so you cant get any electrical noise like you get on a cheap switch mode ac/dc where they've cheapened out on not enough smoothing capacitors. This is very common for that type of supply and often a cause of failures on new backyard test benches. If yours is a variable voltage lab supply this probably doesnt apply, but its still worth ruleing out.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
- lsxautumn
- Posts: 21
- Joined: Sun Oct 30, 2022 6:36 am
- cars: 02 sierra 2500HD LQ4 4L80E
AKA a void that eats all my money
Re: PCM Hammer Release 021
Read my junkyard P59 perfectly the first time without any issues and also was able to update PCM to my 2002 truck VIN without a hitch. Used VCXNano and bench harness with 4x disabled. Absolutely awesome software, I'm excited to dive into messing with this pcm
Re: PCM Hammer Release 021
Awesome!lsxautumn wrote:Read my junkyard P59 perfectly the first time without any issues and also was able to update PCM to my 2002 truck VIN without a hitch. Used VCXNano and bench harness with 4x disabled. Absolutely awesome software, I'm excited to dive into messing with this pcm
Was unaware the VCX Nano had issues with 4x, if you are having issues could you please provide a debug log, maybe it can be resolved ... Pretty sure it's a widely used VCI.
Thank you
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!