2009 Dodge Ram Cummins 3500 6.7L Diesel - Shutoff driving -No Crank no start

This is definitely a weird one again. Customer states that truck shut off while driving and wouldn't start back up. Customer called me to setup an appointment and I got it towed in. This is what the customer explained over text message..

 

I started by checking th TIPM for issues but didn't see anything wrong. I checked all powers and grounds and communications, fuses, wires under the box and output signals to test the circuits. All Good. So now check engine wiring, injector wiring back to the ECU. Didn't find any issues. Some dirty connectors but nothing to cause a no start. Moved on to why no communications still. I was getting data but it was bad data with packet collisions with other modules. I separated the TIPM off the network, same issue. Instrument cluster, same issue, Unplugged the ECU and the data collisions went away. I pulled the ECU and bench tested the pins. All looked good, ECU was drawing a little extra current that what I like to see which was 0.53Amps at 13.8V.

 
 
 

After some testing and trying to read the processor MPC555 and hooking up also to the EEPROM and removing it to read (not pictured here),
I was able to determine it was a problem with the MPC555. when its commanded to start on a certain address line on the EEPROM nothing came from the processor. Im guessing when a tune was written it would continue and not error out and no one would know the difference. The tune was read back on the tuner also but it saved corrupt data. EFILive tool had no Idea it was corrupted. It has no CRC verification I would assume like most tuning devices. I did a compare of the file vs the OEM flash file that I had from a good working CM2100A 5258003 I cloned a while back from another customer ECU. I compared and it was significantly different as far as the tuning and the parts of that tune that run on the software that the ECU CPU understands.

Anyways, I took my good OEM file and flashed the EEPROM. Then I had to take the SKIM module off the steering column and open it up to read the EEPROM in it so I can get the security key number to program the keys. I think a tool exist to read the number via OBD2 but I didn't have one and had to convert encrypted data.
Reprogrammed the key and it started right up! It ran but when checking for codes it said incorrect injector coding data. I turned the truck off, pulled the valve cover off and got the injector data and programmed it all in. it said it successfully written the information for each injector. I turn the key off and back on and the truck ran much smoother but still had a code for the #1 injector so I tried again and it said written successfully, turned the key on an crank, the same issue. that when i started to think it was a processor or EEPROM issue so I replaced the EEPROM, same issue so it pointed to a faulty CPU processor MPC555. I have another one but I don't have a setup to rework a BGA on flex board which its like a plastic sheet that high temp that has copper traces between the sheets. Ill eventually have to get a good BGA station once the funds come in for it. Told the customer of my findings that the CPU of the ECU is shot so now we ordered another ECU. Luckily I already have the Injector data and the code for the SKIM so Im set for the new ECU to come in. I spent several days testing all these thing on this vehicle thinking it was TIPM, security, damaged wiring. the no communications where the ECU was still spitting out data confused me at first because I unplugged all the modules watching each talk on the CAN Bus. I guess it was wishful thinking the ECU was okay but I guess it wasn't. I didn't realize the packet collisions were going on till I hooked up the Oscilloscope to the data lines and seen errors. That’s what made me investigate further, rule out modules one by one because bad data can block the security module and also cause a no start too. 
Now Im waiting on the new reman ECU to come in.