E54 Tunerlock Help
- antus
- Site Admin
- Posts: 8999
- 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: E54 Tunerlock Help
I believe we have E54 working properly. I've sent you a test version if you want to try it.
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
-
- Posts: 22
- Joined: Fri Apr 05, 2019 11:33 pm
- cars: 68 Camaro LS3
99 S10 LS1
18 Volt
07 2500HD 6.0L
Re: E54 Tunerlock Help
I am very sorry for being late to the game. Thanks everyone and In-tech for all of this. I appreciate it so much. I did end up failing my customer.. I wasnt able to get it to boot pin read. But I have ordered a spare E54 to play on.
Antus, will the beta test version be available soon with E54? Thanks much!
Antus, will the beta test version be available soon with E54? Thanks much!
- antus
- Site Admin
- Posts: 8999
- 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: E54 Tunerlock Help
Perhaps. We have one pcm reading and writing properly, but the other test pcm that had something wrong with the bin wouldnt erase. We put the bad bin on another pcm, then it suddenly couldnt erase either. With testing more things that one bricked. rjdrew is posting it half way around the world to me now (2 weeks post?) then i'll try and figure out bdm and bdm cfg file (if needed) and recover it then repeat the process and try and improve the kernel so it doesnt have the same trouble with the erase step. All of this may take some time, so there probably wont be a public beta for at least a few weeks, maybe more. I can share the private beta with you, but it might brick and testing wont help as there will be more changes now before its done.
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
- 04silverado6.0
- Posts: 24
- Joined: Wed Nov 29, 2023 1:39 pm
- Location: Kentucky
Re: E54 Tunerlock Help
I have successfully used the ground method on these ecms in the past. I do not remember which pin. I took a p01 and traced the boot pin to a pin on the chip and did the same on the dmax. Took a few tries but did work.
Re: E54 Tunerlock Help
e54 are notorious for corrupting eeprom area for no reason. It needs special exit sequence after flash is done, so pcm reboots correctly, without overwriting the eeprom with some garbage data.
- antus
- Site Admin
- Posts: 8999
- 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: E54 Tunerlock Help
Can confirm In-Techs location on the second page of this thread is correct. Most apps I tried were not able to do a recovery flash though. I did get my test E54 going again, and was able to get PCMHammer working on E54 for write. I am not doing anything special and so far no bricks at shutdown. I think that may just be issues which the factory flash kernel, and the PCM Hammer one is fine. Hopefully I am correct about that and not speaking too soon
It looks like E54 just needed the CPU Status register set a little different to what we have needed before. A write of the register with the right configuration, rather than an or. Without checking exactly why, I would say it likely had something to do with enabling supervisor mode or some of the other hardware access configuration. None the less the work that was already done was good with a write of 0x2700 to %sr instead of an just an ori with 0x700 to sr like works for all of the other targets so far at flash kernel init.

[03:09:58:732] PCM Hammer (5/10/2024, 3:09 PM)
[03:09:58:745] Saturday, October 05 2024 @03:09:58:74
[03:09:58:753] Initializing J2534 Device
[03:09:58:783] Loaded DLL
[03:10:02:434] Connected to the device.
[03:10:02:451] Battery Voltage is: 13.201
[03:10:02:463] Thanks for using PCM Hammer.
[03:10:26:723] S:\backedup\ecu\E54 Duramax LB7\rons stock bin\E54.bin
[03:10:26:837] Identifying 512KiB file.
[03:10:26:842] File is E54 512KiB.
[03:10:26:850] File operating system ID: 15189044
[03:10:26:854] File is E54 512KiB.
[03:10:26:857] Start End Stored Needed Verdict Segment Name
[03:10:26:862] 20002 6FFFF F157 F157 Good Operating System
[03:10:26:868] 08002 19FFF BE72 BE72 Good Engine Calibration
[03:10:26:873] 1A002 1C7FF D26A D26A Good Engine Diagnostics
[03:10:26:881] 1C002 1DFFF 0000 0000 Good Fuel
[03:10:26:887] 1E002 1EFFF 9BEA 9BEA Good System
[03:10:26:896] 1F002 1FFEF 1689 1689 Good Speedometer
[03:10:26:908] Requesting operating system ID...
[03:10:27:028] File is E54 512KiB.
[03:10:27:037] PCM and file are both for the same Hardware E54
[03:10:27:045] File is E54 512KiB.
[03:10:27:054] Operating system IDs do not match.
[03:10:27:062] PCM operating system ID: 15094441
[03:10:27:069] File operating system ID: 15189044
[03:10:27:077] File is E54 512KiB.
[03:10:27:087] Changing PCM to operating system 15189044
[03:10:27:251] Unlock succeeded.
[03:10:27:273] Attempting switch to VPW 4x
[03:10:27:314] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[03:10:33:489] Upload permission granted.
[03:10:33:920] Kernel upload 100% complete.
[03:10:33:939] Kernel Version: 82400236
[03:10:33:949] Kernel uploaded to PCM successfully.
[03:10:33:973] File is E54 512KiB.
[03:10:33:985] Changing PCM to operating system 15189044
[03:10:34:010] Flash chip: Intel 28F400B, 512KiB
[03:10:34:024] Calculating CRCs from file.
[03:10:34:038] Requesting CRCs from PCM.
[03:10:34:046] Range File CRC PCM CRC Verdict Purpose
[03:10:36:153] 060000-07FFFF 65750A22 91363E84 Different OperatingSystem
[03:10:38:396] 040000-05FFFF 57DBDAAF E9ADD311 Different OperatingSystem
[03:10:40:638] 020000-03FFFF B53C9045 EEF4EFC8 Different OperatingSystem
[03:10:42:338] 008000-01FFFF 8BDEFFCE 5748F9D1 Different Calibration
[03:10:42:499] 006000-007FFF 192D1BB0 71DA7600 Different Parameter
[03:10:42:663] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[03:10:42:967] 000000-003FFF CED58D53 CED58D53 Same Boot
[03:10:42:982] Processing range 060000-07FFFF
[03:10:42:996] Erasing.
[03:10:43:725] Writing...
[03:11:41:400] Processing range 040000-05FFFF
[03:11:41:413] Erasing.
[03:11:42:153] Writing...
[03:12:39:133] Processing range 020000-03FFFF
[03:12:39:142] Erasing.
[03:12:39:886] Writing...
[03:13:37:102] Processing range 008000-01FFFF
[03:13:37:116] Erasing.
[03:13:37:773] Writing...
[03:14:20:645] Processing range 006000-007FFF
[03:14:20:653] Erasing.
[03:14:21:035] Writing...
[03:14:24:623] Calculating CRCs from file.
[03:14:24:639] Requesting CRCs from PCM.
[03:14:24:650] Range File CRC PCM CRC Verdict Purpose
[03:14:26:757] 060000-07FFFF 65750A22 65750A22 Same OperatingSystem
[03:14:28:996] 040000-05FFFF 57DBDAAF 57DBDAAF Same OperatingSystem
[03:14:31:240] 020000-03FFFF B53C9045 B53C9045 Same OperatingSystem
[03:14:32:931] 008000-01FFFF 8BDEFFCE 8BDEFFCE Same Calibration
[03:14:33:094] 006000-007FFF 192D1BB0 192D1BB0 Same Parameter
[03:14:33:260] 004000-005FFF 85B5BB36 85B5BB36 Same Parameter
[03:14:33:572] 000000-003FFF CED58D53 CED58D53 Same Boot
[03:14:33:594] All relevant ranges are identical.
[03:14:33:613] All write-request messages succeeded on the first try. You have an excellent connection to the PCM.
[03:14:33:632] Flash successful!
[03:14:33:664] Clearing trouble codes.
[03:14:34:755] Elapsed time 00:04:07.4948140
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