ECU module programming guide using FDRS

[Snakebitten]

Jesse, just curious if there is a simple explanation for what is actually going on with the typical APIM/USB update procedure. I mean step-by-step.

1. USB stick with files copied to it, via FDRS, is inserted into the trucks USB port.
2. USB device is detected by the truck (by what module? Gateway?)
3. USB storage is indexed
4. USB files are "recognized" as an update and the Sync screen responds with "Updating System" notification. But technically the ONLY thing that is happening is that the files on the USB stick are being copied somewhere (?) onboard the truck.
5. After the files are copied successfully, the Sync screen prompts the user to "Restart the Truck" I assume that at this point NOTHING has been updated or overwritten or altered in any way?
6. Restarting the truck is the first opportunity for the new files (not the copy on the USB, but rather the copy that was previously copied from the USB) to be "processed".
7. After whatever "processing" the new updated files actually means, there is some point in that procedure that the truck is supposed to notify the user that the update was successfull and the USB stick can be removed.

First, I'm sure that I probably have already made some errors in the 7 steps as I understand them, so feel free to correct anything that needs to be.
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?

Sponsored

 

[Whoskyle]

I’ll volunteer for the TSB. Have stuff on its way, will be here in the morning

 

[iceman77]

Wait, for the "dealer fix" you do not need the mongoose? That would be much more appealing than buying the mongoose and/or jacking around with the dealer.

Nope, this is just a “fastboot” procedure to kick your APIM out of the failed 1.7.1 OTA purgatory. Once done, you need to proceed normally with FDRS and Mongoose cable to update your APIM. If you have a USB flash drive with your APIM update ready, you don’t need FDRS to kick off your update. Just insert your USB flash drive while your ignition is KOER, it should kick of within few minutes

 

[iceman77]

I’ll volunteer for the TSB. Have stuff on its way, will be here in the morning

I can’t wait for your test results tomorrow, especially if successful, I would want to update the guide with exact steps to follow. So please make sure you document each step FDRS instructs you to do

 

[Jesse-Infotainment]

Jesse, just curious if there is a simple explanation for what is actually going on with the typical APIM/USB update procedure. I mean step-by-step.

1. USB stick with files copied to it, via FDRS, is inserted into the trucks USB port.
2. USB device is detected by the truck (by what module? Gateway?)
3. USB storage is indexed
4. USB files are "recognized" as an update and the Sync screen responds with "Updating System" notification. But technically the ONLY thing that is happening is that the files on the USB stick are being copied somewhere (?) onboard the truck.
5. After the files are copied successfully, the Sync screen prompts the user to "Restart the Truck" I assume that at this point NOTHING has been updated or overwritten or altered in any way?
6. Restarting the truck is the first opportunity for the new files (not the copy on the USB, but rather the copy that was previously copied from the USB) to be "processed".
7. After whatever "processing" the new updated files actually means, there is some point in that procedure that the truck is supposed to notify the user that the update was successfull and the USB stick can be removed.

First, I'm sure that I probably have already made some errors in the 7 steps as I understand them, so feel free to correct anything that needs to be.
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’ll try to get a look at this in the am and have some kind of answer

 

[Ruffiano99]

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).

 

[jperry5835]

Update. After 6 hours everything is up to date. Looks like I lost all my forscan changes such as glare free lighting but hopefully tomorrow blue cruise works. Thanks again everyone for getting this worked out.

 

[CUL8ER]

Update. After 6 hours everything is up to date. Looks like I lost all my forscan changes such as glare free lighting but hopefully tomorrow blue cruise works. Thanks again everyone for getting this worked out.

Was this for the IPC? And was it the main F120 file that took this long?

 

[Snakebitten]

I’ll try to get a look at this in the am and have some kind of answer

Absolutely no hurry at all.

 

[JJ_Tex]

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).

If you are able to do the "dealer fix" for your stuck 1.7.1. I believe (or hope) that your OTAs would start back up. If that is the case, do you really want to risk it with the Nano?

 

[iceman77]

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.

 

[iceman77]

If you are able to do the "dealer fix" for your stuck 1.7.1. I believe (or hope) that your OTAs would start back up. If that is the case, do you really want to risk it with the Nano?

You are not risking anyrhing with Nano as long as you stay away from FDRS Network Scan and/or CCM module update. If you need to create USB update flash drive for modules such as APIM, TCU or GWM, Nano will work just as good as the Mongoose interface

 

[iceman77]

@Whoskyle not sure what you have ordered, but aparently you don’t need ethernet adapter and cable. See my updated post here for details.

Please DM me once you attempted the repair

 

[jordandev]

You are not risking anyrhing with Nano as long as you stay away from FDRS Network Scan and/or CCM module update. If you need to create USB update flash drive for modules such as APIM, TCU or GWM, Nano will work just as good as the Mongoose interface

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…

 

[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