28F400 desolder flash backup 2001 Silverado Lb7 Duramax

[Europeuser]

Does anyone have a readout of the 28F400B5 from a 2001 Silverado LB7 Duramax?
I'm referring to the content read with the programmer after desoldering the flash memory. This is my last chance for repair...Osid 15188873


Today I killed another E54 ECU. This is the third one.

Yesterday I read a fully functional ECU to disable VATS and install the ECU in another 2001 Silverado Duramax. (Both belong to a friend of mine, but one was purchased without an engine control unit.) We decided to remove the ECU from the running car and disable VATS, then install it in the other one to make sure the engine was running.
Unfortunately, during the write process, I got a flash erase error code:01.
Since then, I've lost the ability to read and write. Recovery mode doesn't work...

I don't know what to do...both the car I repaired (bought without an ECU) and the donor car are dead.
Im stuppid,i know.

Buying such an ECU is difficult in Europe.

Meybe could someone help me buy an ECU in the US? I'll pay upfront. 500-1000-2000 USD. The amount doesn't matter.
I just need to fix these cars somehow.

Below is the log data from yesterday's reading. Maybe this will be of some help.

[12:12:06:234] VIN: 1GCHK29141E327140
[12:12:06:299] OSID: 15188873
[12:12:06:321] Description: E54 Service No. 9388505
[12:12:06:360] Calibration ID: 15063375
[12:12:06:494] Serial Number: 1157MI114B
[12:12:06:552] Broad Cast Code: DJUD
[12:12:06:601] MEC: 0
[12:12:06:649] Voltage: 12.6

I don't expect free help. I'm happy to pay, as I understand your time is valuable.

[antus]

You should be able to buy on ebay. But they are an expensive PCM. That file is OK.
Stop using pcmhammer 2.00-preview. It is an early test version for developers. If you want to work with E54 PCMs on the test versions of the software use the latest, but understand the risk. To get the latest test version you will need a github account and can download the artifact from here: https://github.com/PcmHammer/PcmHammer/ ... 2173043169
Use bench programming only and use a good power supply.

[08:03:56:300] Examining S:\Silverado LB7 DJUD read ok .bin
[08:03:56:311] Identifying 512KiB file.
[08:03:56:316] File is E54 512KiB.
[08:03:56:322] File operating system ID: 15188873
[08:03:56:326] File is E54 512KiB.
[08:03:56:328] Start End Stored Needed Verdict Segment Name
[08:03:56:333] 20002 6FFFF 1314 1314 Good Operating System
[08:03:56:337] 08002 19FFF 9B2E 9B2E Good Engine Calibration
[08:03:56:341] 1A002 1C7FF 0000 0000 Good Engine Diagnostics
[08:03:56:346] 1C002 1DFFF 0000 0000 Good Fuel
[08:03:56:352] 1E002 1EFFF 1AF4 1AF4 Good System
[08:03:56:359] 1F002 1FFEF A1B0 A1B0 Good Speedometer
[08:03:56:365] All checksums are valid.

[antus]

You can use that bin if you can write it directly to the chip. Note that the byte order is reversed in the pcm for most programmers, so you usually need to do a swap-ab to reverse the byte order before the write. Desolder chip, program and resolder is difficult but not impossible if you have an electronics background and have done this type of thing before.

There may also be BDM options, but you are in new-school territory there is a not a lot of experience with this PCM yet as it is not supported in the official version. Have a look at usb jtag nt product and its BDM function. Check for support and details about how to connect to the PCB and how to use the software. Note that if you are in a hurry it can take a while for it to be delivered from canada where they are made. I was not able to get BDM working on mine, but I think I had a faulty BDM programmer. I have not tried again since I got a new one.

[Europeuser]

You can use that bin if you can write it directly to the chip. Note that the byte order is reversed in the pcm for most programmers, so you usually need to do a swap-ab to reverse the byte order before the write. Desolder chip, program and resolder is difficult but not impossible if you have an electronics background and have done this type of thing before.

There may also be BDM options, but you are in new-school territory there is a not a lot of experience with this PCM yet as it is not supported in the official version. Have a look at usb jtag nt product and its BDM function. Check for support and details about how to connect to the PCB and how to use the software. Note that if you are in a hurry it can take a while for it to be delivered from canada where they are made. I was not able to get BDM working on mine, but I think I had a faulty BDM programmer. I have not tried again since I got a new one.

Thank you very much for your help. You saved me. I didn't know about the need to swap bytes ab.
Today I managed to repair all the ECUs, and both cars are running
Thank you very much
I should also add that after repairing the 28F400, I used the latest version of PCMhammer to read it. Everything went fine, but when I tried to write it, it failed again.
However, it didn't matter, because I fixed it again by writing it directly to the 28F400's Flash.

Best regards and thank you for your help.

[02:35:50:843] PCM Hammer (19.02.2026, 08:49)
[02:35:50:843] czwartek, marca 05 2026 @02:35:50:84
[02:35:51:822] Voltage: 12.7V
[02:35:51:838] Elm ID: ELM327 v1.4b
[02:35:51:870] ScanTool device ID: STN2231 v5.8.1
[02:35:56:750] VIN: 1GCHK29141E327140
[02:35:56:798] OSID: 15188873
[02:35:56:799] Description: E54 Service No 9388505
[02:35:56:830] Calibration ID: 15063375
[02:35:56:926] Serial Number: 1157MI114BM
[02:35:56:959] Broad Cast Code: DJUD
[02:35:56:990] MEC: 0
[02:35:57:022] Voltage: 12,6

[antus]

Ok thanks for your report. That is very helpful. I will lock out E54 in the the development branch so that the latest build blocks write and look in to it when I get a chance.

If you saved the debug log of the brick please send it to me as a reference. If you didnt save it and can confirm it failed at the erase step that is also helpful. but it would also be helpful to know which sector failed and resulted in a brick.

[Europeuser]

Ok thanks for your report. That is very helpful. I will lock out E54 in the the development branch so that the latest build blocks write and look in to it when I get a chance.

If you saved the debug log of the brick please send it to me as a reference. If you didnt save it and can confirm it failed at the erase step that is also helpful. but it would also be helpful to know which sector failed and resulted in a brick.

Hi. I didn't save it, but I can do it. I still have ECU No. 3, which I repaired similarly to the previous ones by directly flashing it.
I'll connect it soon, perform a flash backup, and then save the log.

I also think many people don't realize the need to swap bytes ab if their ECU is damaged during the flash process.
The method involving programming with a simple TL866C is an effective way to repair an E54, even if it's completely dead!
Interestingly... I have EFI tuning (software only), and I uploaded my files there to identify and verify the file is correct.
The file that the EFI considers valid after flashing it to the 28F400 causes the ECU to die. When I upload the file after the previous swap, the EFI considers it corrupted, but the ECU comes back to life

[Europeuser]

Here's the debug log

write error_debug_log..txt

from an attempt to save E54. I hope it's helpful. It was similar in all previous versions.
File that i use to write:

LB7 DJUD_ori_VATS_OFF..bin

[antus]

Thanks. EFI Live does not understand the swap-ab and account for it. it is a hardware quirk on the PCM only due to different CPU type endianness than PC.