PDA

View Full Version : Cm 2100 a no communiction after flashing csp5



cumminsDK
August 23rd, 2016, 04:04 AM
I read a file from a 2008 cm2100 ECM and converted the file to csp5 did some editing and flashed the file in. After installing the csp5 switch I proceeded to take a test drive but no go. So far I have checked the files a second time to ensure correct VIN and that both v7.5 and v8 said "ok to flash". I have unhooked the batteries and tried but still no communication. Snap-on scanner reveals no comms with ECM and several other modules with ecm comms dtcs. I have checked power and ground to to the ECM on c2 pins, 45,49,50,60 for 12v and pins 47,48,57 for ground. Also checked can + and can - circuits between ECM and TIPM all checks good. Any other ideas and also can I get the VIN License replaced if we end up with a bad ECM that needs replaced?

thanks
Trent

Move'n Up
August 23rd, 2016, 07:08 AM
I assume you did the RSA patch and also that when you flashed the ECM it completed successfully?

cumminsDK
August 23rd, 2016, 09:18 AM
I assume you did the RSA patch and also that when you flashed the ECM it completed successfully?

I did not do the RSA patch as it did not have the late bootloader revision that will only allow a stock file to be flashed. Am I missing something in a recent update that requires doing the RSA patch even on a 502 bootloader? also yes it did complete successfully.

Move'n Up
August 24th, 2016, 02:18 AM
I did not do the RSA patch as it did not have the late bootloader revision that will only allow a stock file to be flashed. Am I missing something in a recent update that requires doing the RSA patch even on a 502 bootloader? also yes it did complete successfully.
Great and no need to RSA Patch if your OS version isn't one of the later ones that require it. Have you tried to communicate and Flash with just the V2 alone, not via Computer?

Move'n Up
August 24th, 2016, 02:24 AM
BTW - Try it WITHOUT the CSP5 switch connected

GMPX
August 24th, 2016, 08:59 AM
Trent any chance the tune that was in the ECM was already modified by something like Smarty?

cumminsDK
August 26th, 2016, 05:35 AM
Yes it most likely was modified with a smarty I didn't catch it and the V7 .5 software actually said under the B9999 that it was incomplete and do not flash but only on the file I removed from the ECM once I converted it to CSP five it no longer said anything down there and I didn't catch it! Rookie mistake I guess but I was told the truck was programmed currently using EFIlive so I assumed if the file worked being flashed in previously that it would also work for me and when I originally went back to look to see what both software versions said post failure about the file it was only in the CSP five file that I had built and I never did look at the file that was originally in the truck until about 30 minutes ago i've already put another ECM in licensed it and it just finished the flash and were good to go! Thanks for all the help!

Gear head
September 14th, 2016, 11:41 AM
Seems that smarty can cause some problems it must change the file structure in some way.

GMPX
September 14th, 2016, 03:16 PM
The exact problem with the Smarty tuned files is they are not updating a very important table in the ECM that specifies how much of the flash memory is populated, they tend to add some code in to the ECM after the factory data (not sure why), but EFILive is not aware of this additional code because the flash layout table remains stock. End result is a bricked ECM :bawl:

Cougar281
September 15th, 2016, 12:53 AM
The exact problem with the Smarty tuned files is they are not updating a very important table in the ECM that specifies how much of the flash memory is populated, they tend to add some code in to the ECM after the factory data (not sure why), but EFILive is not aware of this additional code because the flash layout table remains stock. End result is a bricked ECM :bawl:
Dumb question... since you know what the smarty is doing that is causing the bricked ECMs, wouldn't it be possible for EFILive look for it and either fix it in the read tune, or put up a big warning to not flash it and to get a clean stock tune?

Sent from my 0PJA2 using Tapatalk

GMPX
September 15th, 2016, 09:15 AM
We do but it kind of works like a virus scanner, if it matches known byte patterns of their mods then you'll see a message in V7.5 saying "Tune File Analysis" - OK to Flash or Do Not Flash.