ECU module programming guide using FDRS

[Ajzride]

I think the IPMA as well as it will kick off a CCM? I ran a network scan with the Nano a few times but was careful to check for corruption every time and close fdrs + rescan if found ??‍

About the earlier cancelling talk I’m wondering about something… I did have to cancel once while the button was greyed out. TCU failed on the last configure step. Then multiple times, then it hung on the configure step for an hour+ and I cancelled out (fdrs warns about snorting when doing so) No issue now with the TCU that I can see…. but retrying a configure seems to still fail (didn’t try a PMI or anything). But the module is green so I hope nothing went wrong there. But stuck at 21281 from something…

can you highlight your TCU in the module list and screen shot the strategy and part numbers in the window below.

Sponsored

 

[iceman77]

All the adapters for the TSB are coming Wednesday. My FDRS license has been expired so ill need to get it again. I dont have the Mongoose so ill be attempting this with the Nano (fingers crossed i dont brick anything).

You should be fine with Nano here as FDRS merely uses it to read the module state and certain configuration parameters to initiate the flashboot procedure. Then it will be used to create the USB update flash drive. You should be good to go here!

 

[jordandev]

can you highlight your TCU in the module list and screen shot the strategy and part numbers in the window below.

My TCU below:

Vehicle Information
TCU - Telematic Control Unit Module
- No DTCs Detected
- DID F113 - MU5T-14H074-AAS
- DID DE09 - 4341
- DID D021 - 32
- DID DE02 - 0A00F13530CD523C5E2D005A000F05096050500010002A887D03C267FCA01C4044
- DID A018 - 46383A35353A43443A38393A44453A36410000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
- DID D027 - MU5T-14H241-DG
- DID DE0C - 000102050202020502020205000102050303030A0303030A0002030A0404040F0404040F
- DID DE05 - 00000000000000000000000000000000000000000000000000000000000000000000000000000000
- DID A015 - 6174742E636F6D2F6C696E636F6C6E0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004E2F410000000000000000000000000000000000000000006174742E636F6D2F666F72640000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004E2F41000000000000000000000000000000000000000000
- DID F188 - MU5T-14H085-DG
- DID F18C - ENMHF21097070649
- DID DE0F - 01
- DID DE08 - 0000000000000000000000000000000000000000
- DID A012 - 011E130F010C920000
- DID F166 - 20101411
- DID DE01 - 2D00000010
- DID EEFB - 3332333835303330333033303330333931363930303130373230323130323232
- DID F16C - MU5T-14H100-AAJ
- DID DE0B - 00
- DID F121 - MU5T-14H090-BAY
- DID DE04 - 70726F6430346E6177696669666F7264000000000000000000000000000000000000000000000000
- DID DE0E - 44453031010708
- DID F111 - MU5T-14H089-AAK
- DID F110 - DSMU5T-14H074-AAX
- DID F17F - 1TV14TB2
- DID 41AE - 89011703272164610707
- DID DE07 - 1D00596F
- DID 8068 - MU5T-14H240-DG
- DID DE00 - 1002000000
- DID F120 - MU5T-14H090-ADG
- DID D040 - 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
- DID EEFA - 1B8EED48
- DID F163 - 05
- DID DE0A - AA
- DID F15F - 0805113D030000000000
- DID DE03 - 006496012C006402580A007800050A003C003C00140C
- DID A010 - 24486F7473706F746D447250000000000000000000000000000000000000000000
- DID DE0D - 4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B3C3C3C3C3C3C3C323C3C3C32
- DID DA01 - DSMU5T-14H074-AAX
- DID A01A - 00
- DID DE06 - 0203596F

 

[iceman77]

But the biggest question I have is that if Step 4 is when the files on the USB are copied to the onboard storage location (temporary location I assume?), then what is the significance of the USB stick still needing to be present in the USB port after step 5?
Restarting the truck (step 6) is after the USB stick has provided the transfer of the update files. What does the truck need the USB stick for beyond that point?

I can answer this question with quite of a certainty:

Once your USB update is successful, your truck writes back a file to your insterted flash drive named 1FTFWxxxxxxxxxxxx_vil.json, and your SYNC screen instructs you to take your USB flash drive and insert it back to your laptop, I would assume for validation purposes. However, FDRS seems to perform its own module validation (over CAN) and never asked or cared for the USB flash drive once the operation completes and validation over CAN succeeds.

 

[Snakebitten]

I can answer this question with quite of a certainty:

Once your USB update is successful, your truck writes back a file to your insterted flash drive named 1FTFWxxxxxxxxxxxx_vil.json, and your SYNC screen instructs you to take your USB flash drive and insert it back to your laptop, I would assume for validation purposes. However, FDRS seems to perform its own module validation (over CAN) and never asked or cared for the USB flash drive once the operation completes and validation over CAN succeeds.

Cool. So that explains why the USB would still be in the truck. For the soul purpose of writing the json file to the USB, regardless of whether the file is critical.

So based on that, would that be why it might be possible to exit a "restart loop" simply by removing the stick before you restart the truck and then telling FDRS that the update was successfull?

Afterall, the update was successful regardless of whether the json file ever made it to the USB storage.

Just curious, of course.

 

[dougbillings]

Here to report success. I can't thank the folks in this forum enough ... especially the op @iceman77 and the master himself @Jesse-Infotainment for all the help. My truck was one of the first built (11/2020) and needed SOOO many updates when I first started. I'm not sure if its just a placebo effect but I swear that the truck feels like it drives 10x better than it did before. I was stuck on Sync version 2.1 for a long time. I am now happy to say that I now have Blue Cruise enabled and first test drive was successful ... if not super stressful. I did experience some lane seeking but I will continue to test it in hopes that the system will 'learn' and get better. Once again, thank you all. This community is amazing!

 

[JaHoova]

NOTICE: Ford has recently released a TSB 22-2117 that addresses the stuck APIM update issue cause by the failed 1.7.1 OTA. I am attaching this TSB to this post. Anyone willing to test it out ? Apparently, all you needs is FDRS, an USB mini adapter (something like this), an USB A to A male cable (something like this). If you already own an FDRS license, this is an additional $12 investment. Definitely worth a try.

You will need to access the APIM direct programming interface by removing the driver side floor console side panel (details are in TSB), connect the USB mini adapter to the exposed interface then connect the USB A to A male to the adapter and to your PC. You need to have your Mongoose VCI connected with FDRS running as well to execute the procedure described in the TSB

Iceman, I did the TSB today. Used the following parts:
https://www.amazon.com/dp/B015ORX70S?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/dp/B009GUXG92?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/TRENDnet-Eth...rendnet+usb+to+etherne,electronics,137&sr=1-4

You need those and the mongoose. When you follow the TSB it says to remove the lower console panel but you need to remove the upper as well (see my picture). When you do this in FDRS, it will use the mongoose to reprogram some stuff first. Then it has you turn the truck off and download drivers. When you do this, the file you download installs the driver installer but not the driver itself. Navigate to C:\program files (x86)\sync drivers installer to find the actual installers. There should be an install.bat file somewhere in that folder. Run that before continuing in FDRS. Once you do that follow the prompts. For my truck I needed to use both the USB male-male AND ethernet adapters to recover the truck. Side note, you CAN'T use one of those combined USB hubs with ethernet- the APIM will reject it with an error. Once it is done it does some type of configuration on the APIM which I had to retry once or twice. Once the procedure finally finished I had a sync version and the update buttons were no longer greyed out. From there I ran the USB APIM updates and have since gotten myself to 21281. Let me know if you have questions, this should help those driving around with USB sticks in their truck hoping they will update at some point...

 

[JaHoova]

After clarifying certain things in this TSB with Jesse, you don’t need the ethernet cable or adapter. You will need USB mini adapter and USB A to A cable with FDRS and your Mongoose cable connected to ODB2 port. I have updated my previous post with details.

I think whether you need ethernet or not may be truck dependent. I did mine without it at first (because I only had a combined hub/ethernet which sync doesn't like) and it did not fix the issue. One I added the ethernet it deleted some sync databases and diagnostic files from the APIM, GWM, and TCU which is what finally un-greyed my updates and brought back my sync version.

 

[Thekameleon]

Same concern here. Always flips to green with self test.

I don’t have cams at speed either.
Don’t recommend PMI of IPMA according to other members. I’m going to do an alignment procedure on the IPMA later as recommended in a TSB. My main reason for doing so is that my BC is a little unstable at times. It hugs the right line a lot.

Edit: I’d like to add that I’m the guy that had 4 modules go purple for the obstacle detection sensors. I decided to PMI the IPMA and that didn’t do anything good so it went to the dealer for correction. This is why I think my IPMA may be a bit off on alignment as well.

Did the alignment procedure fix the right line hugging? My truck has done that since I got it off the lot. Still does it with BC active.

 

[Slappy McGee]

Who, me? I can’t. I’m up to date. This is just a theory I’ve kicked around. The hope is that it operates as a hard reboot of the APIM, causing it to recognize the drive once it powers back up. But I can’t actually test it myself.

Do you know if it’s possible to run An APIM self test from FORScan? I don’t want to shell out another $50 but am willing to try the experiment while Waiting for Godot, I mean USB…

 

[JEB]

Do you know if it’s possible to run An APIM self test from FORScan? I don’t want to shell out another $50 but am willing to try the experiment while Waiting for Godot, I mean USB…

I think all the modules have self tests. But check two things before shelling out the cash. FIrst, have someone with an active FDRS license look in the APIM toolbox to verify. Second, FORScan has some diagnostic procedures, including self tests. If there’s an APIM self test in FORScan, you might be able to run it there without the cash outlay.

 

[Slappy McGee]

I think all the modules have self tests. But check two things before shelling out the cash. FIrst, have someone with an active FDRS license look in the APIM toolbox to verify. Second, FORScan has some diagnostic procedures, including self tests. If there’s an APIM self test in FORScan, you might be able to run it there without the cash outlay.

Well, rather than goof around and potentially mess something up with FORScan I’ll do what a true red-blooded American should do an throw money at the problem. Into Ford for another $30 of adapters from Amazon and will try the TSB procedure tomorrow.

 

[BHunted1]

OK, read this several times. Just want to clarify somethings:
I have a new apim installed few months ago. It cleared up the grayed sync update, repopulated the about screen, etc. Shortly after, still never got an ota. Various reps now say the new apim would not help. (After they told dealer to replace it, they backed out reimbursing them for it. Geezus).
Along the way, I've been updating via fdrs. 2 days subs here and there and finally a month sub.
Still no otas.
There has been speculation that folks that originally had the 1.7.1 lockup, were blocked by Ford to receive anything till after they released a fix. I do believe I'm updated to the latest Sync but my OTA history is blank. Ford is perplexed by this. They have to the end of this month according to them to finish the wave of roll outs.
So question is: If you are to believed to be currently updated to the latest mod updates, shouldn't we start getting otas? (mine has not even in between me doing them). Does this latest TSB fix the OTA debacle and allow otas to start happening on their own? Should this TSB be applied even though you are allegedly past 1.7.1 ? Just to fix the ota or would this hurt it? Also, still no BC and my year went away after they fixed my Nav Subscription disappearing.
Thanks....

 

[Ruffiano99]

Iceman, I did the TSB today. Used the following parts:
https://www.amazon.com/dp/B015ORX70S?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/dp/B009GUXG92?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/TRENDnet-Ethernet-Network-Compatible-TU2-ET100/dp/B00007IFED/ref=sr_1_4?crid=3IP8B0TWFG2Q0&keywords=trendnet+usb+to+ethernet&qid=1648443868&s=electronics&sprefix=trendnet+usb+to+etherne,electronics,137&sr=1-4

You need those and the mongoose. When you follow the TSB it says to remove the lower console panel but you need to remove the upper as well (see my picture). When you do this in FDRS, it will use the mongoose to reprogram some stuff first. Then it has you turn the truck off and download drivers. When you do this, the file you download installs the driver installer but not the driver itself. Navigate to C:\program files (x86)\sync drivers installer to find the actual installers. There should be an install.bat file somewhere in that folder. Run that before continuing in FDRS. Once you do that follow the prompts. For my truck I needed to use both the USB male-male AND ethernet adapters to recover the truck. Side note, you CAN'T use one of those combined USB hubs with ethernet- the APIM will reject it with an error. Once it is done it does some type of configuration on the APIM which I had to retry once or twice. Once the procedure finally finished I had a sync version and the update buttons were no longer greyed out. From there I ran the USB APIM updates and have since gotten myself to 21281. Let me know if you have questions, this should help those driving around with USB sticks in their truck hoping they will update at some point...

How long did the TSB take to do?

 

[Ajzride]

My TCU below:

All of the Mu5T numbers line up with mine, so I think your TCU is okay.

Sponsored