PCM Hammer
Edit: Went back to the yard since it's close, got another blue plug and ALDL. I'll build an offboard later today and test it out.
Last edited by digitaloutsider; Feb 2, 2019 at 04:07 PM.
We have write success!
Built a new offboard for the 0411. PCM was out of an '01 4.3 Blazer. Started with reading the calibration, which worked perfectly. Opened it in TunerCATS to confirm that everything looked good, it did (didn't readily have an XDF for this OS for TunerPro). Went to write the calibration for my Corvette onto the new PCM. Doh! PCM Hammer halts in this scenario since the OS is a mismatch. Forced a write using TunerCATS. Re-read the PCM with PCM Hammer, edited it, then wrote it back. Success!! Re-read the PCM and everything looked good.
If you need someone to test writing different OSs, let me know when you're ready for that. I won't cry if I brick this PCM.
I like the messages about finding a less important PCM haha.
Last edited by digitaloutsider; Feb 2, 2019 at 07:57 PM.
Glad you like the messages, too. The software is new enough that I'm still a little worried someone will use it on a car they need to get to work the next day, and that'll be the way we find out about some terrible bug that hasn't been found yet.
But so far there hasn't been a single report of a bricked PCM, which is really encouraging.
Fired up tunerpro with the referenced XDF and all looks good.
How confident are we with Checksums and writing?
Also I haven't been able to get hold of a base bin file for the car. Can anyone help with that?
Finally, how do I / can I datalog with the AllPro / PCM Hammer?
Many many thanks so far.....
I've tweaked a couple things with Tuner Pro and flashed my car, and it's still driving. But it's still pretty new software. So if it's your only car, I wouldn't advise it just yet. But if you have a backup car... go for it.
I actually did screw up the checksums for my first flash, and went through what I think is the worst that can happen right now... I had to remove the PCM from the car, remove the back panel, and ground one circuit, then reflash it using a workbench wiring harness. It's all good now. When the checksums don't match, the PCM assumes the flash chip is defective, so it won't accept a reflash without a little extra work.
And that's why the app now validates checksums before it will let you write.
Hopefully that won't happen to anyone else.Details on workbench reflashing are here, just in case: https://github.com/LegacyNsfw/PcmHac...bench-Flashing
I've talked a little bit with a guy who is working on an ADX file for Tuner Pro that will allow data logging with the AllPro. It's not ready yet but I think it's coming.
I added the 2 dll files to the tunerpro folder as per the very nice pdf file, but how do you `point` tunerpro to these when modifying the bin file?
What are the click / tick steps to get the checksum working?
Not my only car but I`m about 3000miles from another PCM!!!!
PM'd
You can do a test write with the app to validate the checksums and also to test your interface, wiring, etc. If the test write goes well, I'd expect a full write to work fine too. The test write process is almost identical, it just doesn't interact with the flash chip, so it should catch any issues and can't cause any trouble.
The Best of Corvette for Corvette Enthusiasts
https://github.com/LegacyNsfw/PcmHac.../2019.02.09.01
1 of the files let me connect ok but rate is ~1Hz and i'm not getting anything coming back. 2 files let me connect but with rolling errors and no data. The other files don't even get me connected....
https://github.com/LegacyNsfw/PcmHacks/ ... 9.12.14.01
This fixes a problem with in-vehicle reflashing with ScanTool interface devices.
Flashing of parameter blocks of disabled in this release due to a problem that's still under investigation.
Operating system replacement is supported for P01 PCMs (2001-2002 C5s) but only calibration writes are supported for P59s (2003-2004).
Both of those limitations will hopefully be resolved in the next release.
This release also includes a primitive data logging app, PCM Logger.
EDIT: a user on pcmhacking.net reported a problem trying to flash a P59 with an Intel 1mb chip. That doesn't work yet. No real harm done, but he had to use LS Droid to fix it. I'm hoping to get that fixed in the next day or two. For now though, anyone with a P59 should confirm that it has an AMD flash chip before trying to write to it using PCM Hammer.
Just to be clear:
Intel 512kb chips work for reading and writing.
AMD 1mb chips work for reading and writing.
Intel 1mb chips work for reading, but not for writing. Yet.
Last edited by NSFW; Dec 16, 2019 at 08:36 PM.
https://github.com/LegacyNsfw/PcmHac.../2019.12.18.01
There's also a data logger now (PcmLogger.exe) and it works pretty well. But you'll have to edit XML files by hand if you want to change what gets logged.
Work is underway to consolidate all of the various XDF files from around the internet, so finding an XDF for your operating system should get a lot easier very soon.
Last edited by NSFW; Jan 11, 2020 at 02:30 AM.
https://github.com/BoredTruckOwner/L...ine_Repository
That should make it easier for people to find the files they need for tuning and/or OS changes.
Note that there are no proprietary custom operating systems in that repository, such as the 2-bar / 3-bar COSs from HP Tuners and EFI Live. Nor will there ever be. If you want their operating systems, you should buy their products.
I am hoping that we'll have open-source operating system patches for boost and other fun stuff eventually, but there's no ETA for that.
Last edited by NSFW; Feb 2, 2020 at 04:52 PM.
This adds full-flash capability for P59 PCMs, which were used in
Last edited by NSFW; Mar 5, 2020 at 01:25 PM.














