Quote:
Originally Posted by M140iGuy
Quote:
Originally Posted by Crypto2k3
Thanks for the reply. I already have carplay so it's just a matter of fullscreen. I started getting curious how this works when I saw the ECU binary file I exported was around 98k and the .evo file I got back from fscmaps.com after sending them my ECU was about 1.3M. They have a custom application that is used to connect to the car and load the binary back called FemTOEVO. I also noticed that it had my VIN number and serial number in a header file which I assume is used either as a crypto key or some kind of checksum. I'd like to know what changes are being made to my car over just blindly loading another binary file (probably slightly too paranoid). Fscmaps does provide very good service and they seem really knowledgable. When I asked about updates they said it was completely fine to update but I'm not sure if it would persist the update.
When the update happens from BMW what is actually happening? Does it replace all of the firmware and operating system container with a new one? Where are the FSC codes stored if they persist an update?
How many people here have used fscmaps.com? Just curious.
|
The software update flashes the ECU completely. I can't remember now if the FSC codes are kept in a different area that isn't impacted by the update or if the FSC codes are first backed up by Esys/ISTA and then reinjected during the update process. Either way, the FSCs that were there before will still be there after the update. |
Thanks. So loading the .evo file for my case sounds like I will have no problems with updates because it's not adding any FSC codes and the whole ECU would be replaced, right? I would likely lose carplay fullscreen if this happened I suspect and would need to get another update.