ECU module programming guide using FDRS

[iceman77]

Well if I could go back one day in my life I would start today all over and WAIT before I rushed to do that latest update pack (IPMA/CCM/PSM)

The Cruise Control update failed and left me with a PURPLE CCM. ???

The IPMA has DTC's and for whatever reason, and I don't have a clue, the APIM throws about a MILLION communication DTC's as a result?

Worn out. Tired of sitting in the truck. Lol

Drove it around and indeed I have lost Adaptive Cruise Control.

My luck finally ran out. I must have had 20 updates since January with nary a problem. Arggghhh

Locate CCM, disconnect, wait a little, reconnect, and try a PMI. I have a strong belief that bricked modules can be brought back to life 90% of time! I have bricked my GSM module when I accidentally switched from J2534 to IDS emulation (on VCX nano), and I was able to recover it. Have faith my friend!

All other DTCs are probably a result of a bricked CCM module

Sponsored

 

[iceman77]

Little more info for you Snake:

Either way, no need to panic. Your module is "Purple" not "Gray". Meaning it communicates over CAN. Its not dead. You need to try to flash it again. If FDRS is a no go we can try ForScan route. I can get you all the files you need. Hope you have a recent config saved somewhere or we can extract from your AB. Ping me in the morning. Me and @Jesse-Infotainment will help you out

 

[Snakebitten]

No panic. I promise. It's just a truck part, if you know what I mean.

And thanks for the encouragement. Good to see you must be feeling better yourself.

I'll pull the plug on it tomorrow and see if that helps. I'll ping you if I hit a dead end.
I downloaded my AB data a couple of weeks ago from that Motorcraft link I think one of you gurus provided? (if that helps)
I never edited the CCM in Forscan so never backed it up that method.

Regardless, again thanks for the assist. I'll let ya know the progress.

 

[Snakebitten]

Note: it fails the update and the PMI when it tries to block erase some filename I don't remember. Stops at like 3 or 4 of 257 steps.
Barely gets started and pops up "failed, do you want to retry?"

 

[Thekameleon]

Well if I could go back one day in my life I would start today all over and WAIT before I rushed to do that latest update pack (IPMA/CCM/PSM)

The Cruise Control update failed and left me with a PURPLE CCM. ???

The IPMA has DTC's and for whatever reason, and I don't have a clue, the APIM throws about a MILLION communication DTC's as a result?

Worn out. Tired of sitting in the truck. Lol

Drove it around and indeed I have lost Adaptive Cruise Control.

My luck finally ran out. I must have had 20 updates since January with nary a problem. Arggghhh

Same thing has happened to me. The CCM failed when trying to erase the blocks.

 

[ENG430]

Hi.... would someone be able to run my VIN and see what updates I need.

1FTFW1E51MFC37912

 

[Bob_Mac]

You found the fix me button when you and I were on the phone. I don’t remember you running the debug. But if it worked, great.

EDIT: I just double-checked my Mongoose. Running debug is not necessary. Debug only enables the logging feature in case you need to send an error log to someone for further diagnosis. If I remember correctly, you found “Fix Me” when you ran either the Vehicle Check or the Device Check.

Yes, it occurred during the Device Check but several users reported it showing when in Debug so it mus have been a timing thing. I just confirmed your findings as well...

 

[Fordphanatic]

Hi.... would someone be able to run my VIN and see what updates I need.

1FTFW1E51MFC37912

Your truck has a bunch of updates available

 

[Bob_Mac]

Your truck has a bunch of updates available

@ENG430 Start with the GWM first!

 

[JEB]

These look odd in my AB information. This is for the IPMA. PSCM looks normal.

You’re getting this junk running a Mongoose? Try running the first three diagnostics (Install Check, Vehicle Check, Device Check) under the Support tab in the J2534 Toolbox. The Mongoose should be connected and the ignition on when you run the diagnostics. Correct any errors you find with the “Fix Me” button and then run another network scan in FDRS.

 

[ENG430]

Your truck has a bunch of updates available

Thanks alot. I'll ask dealer to update them in the next service.

 

[ENG430]

@ENG430 Start with the GWM first!

Can you please write down the sequence of what should I start until the last one.
Regards

 

[JEB]

Yes, it occurred during the Device Check but several users reported it showing when in Debug so it mus have been a timing thing. I just confirmed your findings as well...

I suspect that Debug didn’t really “find” anything. It probably just logged an error uncovered by another diagnostic.

 

[JEB]

Thanks alot. I'll ask dealer to update them in the next service.

That is unlikely to work. A dealer will not update a module just because it’s out of date. As long as it’s working properly, they can’t get warranty reimbursement. You have to be able to tie a specific vehicle complaint to a specific out of date or malfunctioning module so they can classify it as a repair.

 

[Bob_Mac]

Can you please write down the sequence of what should I start until the last one.
Regards

1. GWM
2. TRM
3. DDM
4. PDM
5. DSP
6. SCCM
7. CCM - This will also do the PSCM & IPMA

Sponsored