|
Title: checksum issue, me7check (hope its in the correct section) Post by: 8951ben on May 02, 2021, 12:48:43 AM Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. All rights reserved. C:\Users\ben>me7check in.bin ============================================================================== me7check v1.12 (c) mki, 06/2004-05/2012 Checking file in.bin (size=1048576) Reading Version Strings... -> Bootrom Version = 05.12 -> EPK = 40/1/ME7.5/5/4018.10//24B/Dst03o/290702// -> Contents of ECUID data table: - '0261208053' (SSECUHN) - '1037366473' (SSECUSN) - '8N0906018CB ' (VAG part number) - '0003' (VAG sw number) - '1.8L R4/5VT ' (engine id) -> Contents of ECUID data table: - 'HW_MAN004' -> No errors found. File is OK. ********************* hi all i hope someone can help or point me in the rite direction. this is what i am coming up with once i check my file that has had a tune and launch control added. my issue is it works fine i can start it and drive short runs but as soon as i drive a long distance i get a checksum error and the car wont start Title: Re: checksum issue, me7check (hope its in the correct section) Post by: 8951ben on May 02, 2021, 12:55:59 AM Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. All rights reserved. C:\Users\ben>me7check in.bin ============================================================================== me7check v1.12 (c) mki, 06/2004-05/2012 Checking file in.bin (size=1048576) Reading Version Strings... -> Bootrom Version = 05.12 -> EPK = 40/1/ME7.5/5/4018.10//24B/Dst03o/290702// -> Contents of ECUID data table: - '0261208053' (SSECUHN) - '1037366473' (SSECUSN) - '8N0906018CB ' (VAG part number) - '0003' (VAG sw number) - '1.8L R4/5VT ' (engine id) -> Contents of ECUID data table: - 'HW_MAN004' -> No errors found. File is OK. ********************* C:\Users\ben>me7sum in.bin out.bin ME7Tool (v1.0.3) [Management tool for Bosch ME7.x firmwares] Inspiration from Andy Whittaker's tools and information. Written by 360trev and nyet [BSD License Open Source]. Attempting to open firmware file 'in.bin' Step #1: Reading ROM info .. Searching for EPK signature...OK Searching for ECUID table...OK EPK : '40/1/ME7.5/5/4018.10//24B/Dst03o/290702//' Part Number : '8N0906018CB ' Engine ID : '1.8L R4/5VT ' SW Version : '0003' HW Number : '0261208053' SW Number : '1037366473' Step #2: Reading ROMSYS .. Startup section: word[0x008000]+word[0x00FFFE] @008038 Add=0x00CD15 CalcAdd=0x00CD15 ADD OK Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF @00803c Add=0xA0B46E CalcAdd=0xA0B46E ADD OK All param page: word[0x010000]+word[0x01FFFE] @01bf7a Add=0x00971D CalcAdd=0x00971D ADD OK Step #3: Reading RSA signatures .. Searching for RSA offset #0...OK Searching for RSA offset #1...OK Signature: @8ec6a-8ecea Modulus: @167c2-16842 Exponent: @16842 = 3 Searching for MD5 ranges...OK MD5 Block Offset Table @1679e [32 bytes]: 1) 0x00010002-0x00013FFE 2) 0x00014252-0x00017F4E 3) 0x00018192-0x0001FBDC 4) 0x00026A00-0x0002FFFC EncrMD5: e8 42 27 24 bb 03 f2 50 b6 56 58 15 2a 27 fc cd CalcMD5: e8 42 27 24 bb 03 f2 50 b6 56 58 15 2a 27 fc cd OK Step #4: Finding CRC table(s) .. Searching for CRC table(s)...OK CRC table(s) OK Step #5: Reading Main Data Checksums .. Searching for main data CRC pre block...missing Searching for main data CRC/csum blocks...OK Searching for main data CRC offsets...missing Searching for main data checksum offsets...OK Main Checksums: 1) 0x010002-0x013FFE CalcCSM: 00135CC4 2) 0x014252-0x017F4E CalcCSM: 00289BB7 3) 0x018192-0x01FBDC CalcCSM: 0045C852 4) 0x026A00-0x02FFFC CalcCSM: 00C3DA07 @8f4b0 CSM: 00C3DA07 CalcCSM: 00C3DA07 Main data checksum OK Step #6: Reading Main Program Checksums .. Searching for main program checksum..OK ROM Checksum Block Offset Table @1fb92 [16 bytes]: 1) 0x000000-0x00FBFF CalcChk: 48D10B05 0x00FC00-0x01FFFF CalcChk: 21E156B3 CalcCRC: ACC5C876 SKIPPED 2) 0x020000-0x0FFFFF <fffe0> Chk: 42369035 CalcChk: 42369035 OK (i) Step #7: Reading Multipoint Checksum Blocks .. Searching for multipoint block descriptor #1...missing Searching for multipoint block descriptor #2...OK 1) <1fbde> 0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK 2) <1fbee> 0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK 3) <1fbfe> 0x000000-0x003FFF Chk: 0FA0F5CF CalcChk: 0FA0F5CF OK 4) <1fc0e> 0x004000-0x007FFF Chk: 0F4716B3 CalcChk: 0F4716B3 OK Multipoint #2: [66 blocks x <16> = 1056 bytes] *** Found 70 checksums in in.bin *** DONE! 0/0 error(s) in in.bin corrected in out.bin! *** C:\Users\ben> i also have this one that had the checksum already done but it does the same after a long journey i used me7sum but it will not create a corrected file and says that it is ok Title: Re: checksum issue, me7check (hope its in the correct section) Post by: Sandstorm3k on May 02, 2021, 02:38:35 AM How'd you acquire the tune? I'd say it's not worth your time. Go back to stock and DIY.
Title: Re: checksum issue, me7check (hope its in the correct section) Post by: 8951ben on May 02, 2021, 03:55:35 AM It was made by someone who owns a tuning company. he had redone it with checksums done but I still get the issue that's why I decided to check it using me7. I wouldn't know where to start with my own tune. I can flash easy enough and I have a stage 2 tune done by someone else who has lots of good feedback but the car isn't as quick and has no launch control
Title: Re: checksum issue, me7check (hope its in the correct section) Post by: fknbrkn on May 02, 2021, 04:31:41 AM I had tuis problem with that ecu once
All the same - ecu dies next morning when cold start The problem with the lc routine Tried to move routine, move ram variable offset - still the same Works fine with lc removed, dunno the reason cos investigation not worth it Better to flash it with BP or remove this 2step crap Title: Re: checksum issue, me7check (hope its in the correct section) Post by: 8951ben on May 02, 2021, 08:57:35 AM Oh so it's most likely the launch control causing the issue. I'll get that removed or maybe give it ago myself
|