|
Title: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: tbm on July 01, 2014, 01:06:09 PM Hi everyone!
Recently I got very uncomfortable error DTC-16985 several times but my bin file has a correct checksum. At first I thought that ECU broke but when I uploaded previous version of my bin file and everything was OK. Maybe someone faced with the similar issue? me7check v1.12 (c) mki, 06/2004-05/2012 Checking file nls.bin (size=1048576) Reading Version Strings... -> Bootrom Version = 05.12 -> EPK = 40/1/ME7.5/5/4019.02//24C/Dst02o/220202// -> Contents of ECUID data table: - '0261207440' (SSECUHN) - '1037363908' (SSECUSN) - '06A906032HN ' (VAG part number) - '0002' (VAG sw number) - '1.8L R4/5VT ' (engine id) -> Contents of ECUID data table: - 'HW_MAN004' -> No errors found. File is OK. ********************* Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on July 01, 2014, 02:38:09 PM You have antilag or other custom code?
Title: Re: DTC-16985 with checksumed bin file Post by: k0mpresd on July 01, 2014, 03:14:12 PM You have antilag or other custom code? his file name is nls.bin. Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on July 01, 2014, 04:12:29 PM his file name is nls.bin. lol. To the OP, that there's your problem. Get ecufix if you want to run custom code on that binary. Title: Re: DTC-16985 with checksumed bin file Post by: tbm on July 02, 2014, 01:29:35 AM Yes, I have custom code in bin file. I've implemented NLS there.
Today I've downloaded trial version of ecufix from here http://blog.ecufix.com/2014/06/ecufix-has-had-few-extra-binaries-added.html But ecufix also didn't find any CRC errors. Please see attached screenshot. Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on July 02, 2014, 01:33:59 AM Post your file...
Title: Re: DTC-16985 with checksumed bin file Post by: tbm on July 02, 2014, 02:12:55 AM File is attached
Title: Re: DTC-16985 with checksumed bin file Post by: k0mpresd on July 02, 2014, 02:21:08 AM chks ok.
Title: Re: DTC-16985 with checksumed bin file Post by: tbm on July 02, 2014, 02:42:30 AM k0mpresd, thanks a lot!
Trial version shows only compatibility of files. So after CRC were corrected can I now edit bin file in WinOLS without any negative consequences or every time I will have to recalculate CRC again? Title: Re: DTC-16985 with checksumed bin file Post by: tbm on July 02, 2014, 05:47:26 AM I've done some checks and as far as I understood WinOLS only can calculate checksum based on original file.
So if some custom block was inserted this block just skipped WinOLS. I even imported bin file with correct CRC from k0mpresd in WinOLS but WinOLS recalculated CRC to wrong. Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on July 02, 2014, 07:48:55 AM I've done some checks and as far as I understood WinOLS only can calculate checksum based on original file. So if some custom block was inserted this block just skipped WinOLS. I even imported bin file with correct CRC from k0mpresd in WinOLS but WinOLS recalculated CRC to wrong. If you modify the ecufix'd file, you'll have to sum it all over again. Title: Re: DTC-16985 with checksumed bin file Post by: tbm on July 02, 2014, 11:22:30 AM If you modify the ecufix'd file, you'll have to sum it all over again. So if I want to implement custom code to my file I have only one solution - buy ecufix. Am I right?Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on July 02, 2014, 12:59:01 PM So if I want to implement custom code to my file I have only one solution - buy ecufix. Am I right? Or, post here. I have it, K0mpressd has it, as well as many others. If it's a work in progress, best bet is to buy ecufix, or use a different software version. Title: Re: DTC-16985 with checksumed bin file Post by: garry on December 29, 2014, 03:12:15 PM Hello. I have the same problem, that's why I've decided to dig out this topic. I've added an LC procedure to my modified map file, and I have the 16985 - Internal Control Module: Memory Check Sum Error P0601. My ECU part number is 06A 906 032 MJ, and my engine is AUQ ('03 Golf MK4 GTI). I have already flash the 95040, and now I don't have this error any more, but when I flash the LC file into my car, after a few engine starts, this error comes again. I will paste my file here, could some one please check it, if there are some CRC errors and correct it? I've opened my file in ECUFix, but I have only the test version, and he didn't find any CRC errors...
Title: Re: DTC-16985 with checksumed bin file Post by: ddillenger on December 30, 2014, 12:56:45 AM Neither ME7Check nor ME7Sum see any errors in that file.. (http://i.imgur.com/tDwJorGl.jpg) Title: Re: Post by: garry on December 30, 2014, 04:12:59 PM Thank You very much ddillenger! You are my life saver :-)
Title: Re: DTC-16985 with checksumed bin file Post by: nyet on December 30, 2014, 05:09:49 PM Looks like two places are no-opped out by ecufix.
Code: 38289c38289 I'm assuming those are the RSA functions: question is, what is wrong with my RSA correction? Is there actually a separate public key stored somewhere in the ECU that I am unaware of, that is paired with a private key that only Audi has? ME7Sum generates its own key pair (self sign)... perhaps that is not sufficient. Title: Re: DTC-16985 with checksumed bin file Post by: nyet on January 07, 2015, 10:20:49 AM According to my sources, the custom NLS code is interfering with the RSA checking done by the ECU because it disturbs ram location 384FF0
Changing it to an unused (for real) location (e.g. 386000) should fix the problem, and should not require the RSA checking to be disabled entirely. Title: Re: DTC-16985 with checksumed bin file Post by: maZer.GTi on January 13, 2015, 02:22:45 PM According to my sources, the custom NLS code is interfering with the RSA checking done by the ECU because it disturbs ram location 384FF0 Changing it to an unused (for real) location (e.g. 386000) should fix the problem, and should not require the RSA checking to be disabled entirely. We can fix it :D HOWEVER! Trying to find unused RAM without disassembling the files will be difficult. The solution implemented starting with version 0.4 is that you can change the counter variable by specifying the address to use in your argument. example: launch.exe ecu.bin ecu.ecu offset_code offset_variable 0x384FF0 Please don't forget, you need to specify the offsets for locations manualy if you want to use it! :) Title: Re: DTC-16985 with checksumed bin file Post by: nyet on January 13, 2015, 05:24:09 PM We can fix it :D GREAT work, thanks dude! Quote Trying to find unused RAM without disassembling the files will be difficult. Not just difficult, i can't think of a good way to know for sure... other than using ME7L to log values in various RAM location candidates and see if they change throughout a long drive. Title: Re: DTC-16985 with checksumed bin file Post by: maZer.GTi on January 14, 2015, 04:55:38 PM GREAT work, thanks dude! Not just difficult, i can't think of a good way to know for sure... other than using ME7L to log values in various RAM location candidates and see if they change throughout a long drive. Thanks :D But i think the easiest way is if we create a list of addresses that are known working, and in which software. Title: Re: DTC-16985 with checksumed bin file Post by: nyet on January 14, 2015, 05:11:10 PM Thanks :D But i think the easiest way is if we create a list of addresses that are known working, and in which software. Agreed, but there is no way of knowing for sure whether the address is ok... Title: Re: DTC-16985 with checksumed bin file Post by: KmosK04 on February 07, 2015, 10:32:41 AM According to my sources, the custom NLS code is interfering with the RSA checking done by the ECU because it disturbs ram location 384FF0 Changing it to an unused (for real) location (e.g. 386000) should fix the problem, and should not require the RSA checking to be disabled entirely. How can I be sure that the script won't cause any errors? Everytime I start my car I have in my mind this.. :/ Title: Re: DTC-16985 with checksumed bin file Post by: gt-innovation on March 23, 2015, 09:20:10 AM If there was a problem you would have seen it in the first 2 3 days of driving or after 70 80+ km. I assume you did more then that so there will not be such a problem.I am trying to find out at the moment what is wrongon some version with rsa.
Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: focalpoint519 on September 08, 2017, 06:23:32 AM this seems to be a quick solution, CW_NOROMCHKRESET, that thread should be bumped a lot so people struggling with 16985/P0601/001537 and otherwise working code.
http://nefariousmotorsports.com/forum/index.php?topic=274.msg1470#msg1470 Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: focalpoint519 on September 08, 2017, 06:40:58 AM this seems to be a quick solution, CW_NOROMCHKRESET, that thread should be bumped a lot so people struggling with 16985/P0601/001537 and otherwise working code. :o Look how nice they play with eachother http://nefariousmotorsports.com/forum/index.php?topic=274.msg1470#msg1470 Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: nyet on September 08, 2017, 11:35:34 AM this seems to be a quick solution, CW_NOROMCHKRESET, that thread should be bumped a lot so people struggling with 16985/P0601/001537 and otherwise working code. http://nefariousmotorsports.com/forum/index.php?topic=274.msg1470#msg1470 I don't think this is a good idea. Look, there is absolutely no reason NLS is a must have. If you can't get NLS working correctly, and it causes problems, don't use it. You can easily use ME7Logger to log ram areas and see if various address contents change over time. Try a different ram location. Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: kaross on May 16, 2018, 02:55:59 PM I am getting this error 16985 on one car with NLS/LC.
Can anyobdy confirm if ME7Sum works in this case? I have double checked, but always says: No errors found. But after 30-50km again this error. Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: nyet on May 16, 2018, 03:19:24 PM I am getting this error 16985 on one car with NLS/LC. Can anyobdy confirm if ME7Sum works in this case? I have double checked, but always says: No errors found. But after 30-50km again this error. ME7Sum (nor any other utility) will not help if you screwed up your ASM patch. Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: ottosan on July 01, 2018, 04:53:55 AM Hello,
Today I have used auto add script found here:http://nefariousmotorsports.com/forum/index.php?topic=3349.0 patched my ECU .bin and corrected checksums using me7sum. 9 checksums where corrected Before correction I have checked the file with me7check and 9 errors where found however after me7sum no error could be found. I have not tried the file yet.. It is a 1.8t HS file Could somebody owning ecufix check my file and correct if still not OK? Thank you in Advance, Regard OK It looks like my file does not have RSA so I'm removing the attachment. Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: miigotu on October 06, 2018, 10:52:06 PM Can someone confirm that this means I don't need to worry about RSA on my bin? It is 032CL
Code: Step #3: Reading RSA signatures .. Is there anything else I need to worry about to check before I flash? Title: Re: DTC-16985 with checksummed bin file - NLS interfering with RSA checksum Post by: Denis292 on October 04, 2020, 12:20:04 PM Please help me fix RSA using the ecufix license. Thank you, sorry for the English language, the translator helps me. I'm from Russia) a4 b6, ecu 518f, Turbo td05hr-16g6c-10.5t.
|