|
Title: MED9.1 EEPROM and FLASH matching workaround Post by: everydayparadise on February 02, 2016, 10:03:19 AM I have spent a while working with EEPROM and FLASH files on MED9.1 and have found what I believe is the cause of the P160A Internal Control Module Memory fault with mismatched files when files have already been checksum’d.
For an example I have two 1K0907115B 0040 Flash Files. For the most part they are the same (just a few maps that have some changes) except for the code that starts at 006C00 and ends with 5A5A5A5A. I load file A it loads fine and I get no P160A code, but if I load file B I will get the P160A checksum code. This is where the 006C00 code comes into play. When I copy the code from file A to file B and then load file B to the ecu the P160A goes away. I took this a step further and took a file from 1K0907115H 0030 and pasted the 006C00 code from file A and loaded it and there was no P160A code. Now I don’t know what this codes does to pair it to the EEPROM but it seems like this is the case. Does anyone out there have some information on what this code does? Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: ddillenger on February 02, 2016, 10:13:01 AM You can use nearly any 2.0 TFSI eeprom as long as it is accompanied by the flash portion starting at 6C00.
Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: littco on May 03, 2017, 09:29:18 AM I have spent a while working with EEPROM and FLASH files on MED9.1 and have found what I believe is the cause of the P160A Internal Control Module Memory fault with mismatched files when files have already been checksum’d. For an example I have two 1K0907115B 0040 Flash Files. For the most part they are the same (just a few maps that have some changes) except for the code that starts at 006C00 and ends with 5A5A5A5A. I load file A it loads fine and I get no P160A code, but if I load file B I will get the P160A checksum code. This is where the 006C00 code comes into play. When I copy the code from file A to file B and then load file B to the ecu the P160A goes away. I took this a step further and took a file from 1K0907115H 0030 and pasted the 006C00 code from file A and loaded it and there was no P160A code. Now I don’t know what this codes does to pair it to the EEPROM but it seems like this is the case. Does anyone out there have some information on what this code does? I wouldnt suggest using these files especially the eeprom as its been used with an iffy mpps so has time out issues when reading Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: birchbark506 on October 08, 2017, 06:38:41 AM I tried what your saying with file a being 7115B sw0040 over to file B 7115B sw0010 and I was still getting the same error P160A Internal Control Module Memory my car came with 7115B sw0010 but the immo ecu I bought was 7115B sw0040 and wanted to test my car with the file it came with from factory
Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: aef on March 07, 2018, 06:20:50 AM lets say i am trying to turn a used ecu back to stock.
i have a tuned ecu bmd readout (not able to post because of board rules). and i have another bdm of same version but stock file. which area is necessary to have in the ori file? is it enough to copy 6c00-6fff from tune to ori and thats it? NO! car wont start... i was under this impression because med9 is new to me and i couldnt find anything useful about structure of files online. Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: IamwhoIam on March 07, 2018, 02:40:45 PM The "ori" file needs to be pasted from 7000 to 1FFFFF. Leave 0-6FFF alone on the tuned ECU, and it'll start just fine
Title: Re: MED9.1 EEPROM and FLASH matching workaround Post by: aef on March 07, 2018, 02:46:04 PM hmm i can report in some hours
attached is my try, basically what you say and a file from a friend which will start tomorrow i hope so unfortunatelly i was not @ the car and i dont know the exact dtc |