ECU module programming guide using FDRS

[joeco]

Just select no, or force close FDRS and reopen. You can do the other modules while you wait for the APIM update to kick off.

Copy, thanks. Are there any module updates I should avoid while the APIM is in progress?

Sponsored

 

[rugedraw]

Copy, thanks. Are there any module updates I should avoid while the APIM is in progress?

Not really. It is possible that when you update all the other modules, you will see some codes in FDRS that you cannot clear. This is because the firmware in the GWM will not be fully compatible with the newer firmware on the modules you updated, but it won't cause any real world problems.

 

[joeco]

Took the truck to run some errands and got USB error 0 again….while cursing at the screen, I noticed it said “system updating” in the background. I let it do its thing, and it prompted restart required. Weird.

Now I’m waiting 10+ minutes to restart, and crossing my fingers I’ll get the elusive update successful shortly after restarting.

 

[svtzx2]

Took the truck to run some errands and got USB error 0 again….while cursing at the screen, I noticed it said “system updating” in the background. I let it do its thing, and it prompted restart required. Weird.

Now I’m waiting 10+ minutes to restart, and crossing my fingers I’ll get the elusive update successful shortly after restarting.

Did it work? We’re waiting in anticipation.

 

[joeco]

I never saw update successful, BUT for the first time ever I now see a sync version (21146_Product) and revision (145). Hopefully this means I’m out of purgatory!

edit: I confirmed in FDRS that the update was successful. Auto-update is now turned on. APIM is no longer in the list of available updates. An update for GWM appeared, so I’ll do that next assuming that will unlock the next APIM update.

 

[joeco]

In case it helps others, two things I did different this time:

1. When formatting my USB, I unselected “quick format”
2. After it prompted “restart required”, I shut it off then disconnected the negative terminal of the battery and charged it to 100% before restarting. This took well over the recommended 10 min wait.

 

[joeco]

So got up to APIM version 22293, and when trying to run the IPC update, the cluster powers off, and then the update just fails and refuses. I have to unplug the mongoose before the system resets and the dash lights back up. Is this a known issue? Any resolution?

Did you get this resolved? I am running into the same issue.

 

[bigbearbruin]

Did you get this resolved? I am running into the same issue.

Not yet, been in the middle of moving the last couple of weeks, so haven't had the time to try again. Someone recommended trying to downgrade FDRS and trying again, so maybe try that? I will try again next week when I have more time.

 

[joeco]

Happy to report that I am now on Sync version 22293 revision 610, which gave me full screen CarPlay. This was after a 5+ hour IPC update to unlock the this APIM update.

I recognize this isn’t the latest Sync version available but FDRS is showing no additional updates to run. Fine by me since at least the truck should receive OTA updates going forward.

Thanks to everyone who helped along the way. Persistence pays off!

 

[rugedraw]

Not yet, been in the middle of moving the last couple of weeks, so haven't had the time to try again. Someone recommended trying to downgrade FDRS and trying again, so maybe try that? I will try again next week when I have more time.

If the IPC continues to struggle, you will need to try to CAN it in using the cable instad of the USB. It will take 5-6 hours to update it this way, but it will work.

 

[bigbearbruin]

If the IPC continues to struggle, you will need to try to CAN it in using the cable instad of the USB. It will take 5-6 hours to update it this way, but it will work.

I don't know what this means. CAN it in? Can you elaborate on this more please?

 

[rugedraw]

I don't know what this means. CAN it in? Can you elaborate on this more please?

When you update it with FDRS and FDRS asks if the update was successful, you select no and FDRS will give you the option to install the update via CAN (the cable) instead of USB.

 

[bigbearbruin]

When you update it with FDRS and FDRS asks if the update was successful, you select no and FDRS will give you the option to install the update via CAN (the cable) instead of USB.

Ahh, ok, yeah I never even get that far, as it immediately fails when it attempts to start to load onto the USB stick, the cluster goes blank, start button becomes unresponsive, and wont power back on until I remove the mongoose, and it just states it cannot communicate with the module. I will try again this week, and then try downgrading FDRS to see if that lets me get further along.

 

[rugedraw]

Ahh, ok, yeah I never even get that far, as it immediately fails when it attempts to start to load onto the USB stick, the cluster goes blank, start button becomes unresponsive, and wont power back on until I remove the mongoose, and it just states it cannot communicate with the module. I will try again this week, and then try downgrading FDRS to see if that lets me get further along.

Try the 20 minute battery disconnect too if you haven't already.

 

[joeco]

Ahh, ok, yeah I never even get that far, as it immediately fails when it attempts to start to load onto the USB stick, the cluster goes blank, start button becomes unresponsive, and wont power back on until I remove the mongoose, and it just states it cannot communicate with the module. I will try again this week, and then try downgrading FDRS to see if that lets me get further along.

I ended up having to CAN update to get it to go through. I used the current FDRS version, 46.5.6.

Sponsored