Title: 1.8t checksum is bad?? Post by: TomekBK2 on January 02, 2023, 05:56:56 AM I programmed my ECU today. I modified it because I wanted pops&bangs.
The car did not start after uploading. The entire program has been loaded. Luckily, I was able to upload the ori file. Does anyone know what the problem is. I use mps. Audi tt 1.8t 98. Title: Re: 1.8t checksum is bad?? Post by: JeanAwt on January 02, 2023, 08:20:42 AM if it can help...
ME7Sum (v1.1.2) [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 'POPS8N0906018AB.bin' Step #1: Reading ROM info .. Searching for EPK signature...OK Searching for ECUID table...OK EPK : '36/1/ME7.5/5/4019.00//F19u3/Dst02o///' Part Number : '8N0906018AB ' Engine ID : '1.8L R4/5VT ' SW Version : '0002' HW Number : '0261207027' SW Number : '1037354503' Step #2: Reading ROMSYS .. Startup section: word[0x008000]+word[0x00FFFE] @08038 Add=0x0000E5B3 CalcAdd=0x0000E5B3 ADD OK All param page: word[0x010000]+word[0x01FFFE] @01a896 Add=0x00971D CalcAdd=0x00971D ADD OK Step #3: Finding CRC table(s) .. Searching for CRC table(s)...OK CRC table(s) OK Step #4: Reading RSA signatures .. Searching for RSA offset #0...missing Searching for RSA offset #1...missing Step #5: Reading Main Data CRC/Checksums .. Searching for main data CRC pre block...missing Searching for main data CRC/csum blocks...missing Falling back to default 512k CRC blocks...OK Searching for main data CRC offsets...OK Searching for main data checksum offsets...missing Main CRCs: 1) 0x010000-0x013FFF @6693c CRC: 03AA9D3E CalcCRC: 03AA9D3E CRC 2) 0x014300-0x017F67 @66942 CRC: 9FBCA63F CalcCRC: 9FBCA63F CRC 3) 0x018191-0x01FBFF @66948 CRC: 42380CD2 CalcCRC: 42380CD2 CRC Step #6: ROMSYS Program Pages Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0x7 @00803c Add=0x41CD80 CalcAdd=0x41CD80 ADD OK Step #7: Reading Main Program Checksums .. Searching for main program checksum..OK ROM Checksum Block Offset Table @1bfcc [16 bytes]: 1) 0x000000-0x00FBFF CalcChk: 499CCE49 0x00FC00-0x01FFFF CalcChk: 3D3CD6F6 CalcCRC: DCEE4698 SKIPPED 2) 0x020000-0x07FFFF CalcChk: F9DF09E3 @7ffe0 Chk: F9DF09E3 CalcChk: F9DF09E3 OK (i) Step #8: Reading Multipoint Checksum Blocks .. Searching for multipoint block descriptor #1...OK 1) <14224> 0x024000-0x026567 Chk: 0AE61FD2 CalcChk: 0AE61FD2 OK 2) <14234> 0x014000-0x014243 Chk: 005FB53E CalcChk: 005FB53E OK ( 3) <14244> 0xFFFFFFFF-0xFFFFFFFF END Multipoint #1: [2 blocks x <16> = 32 bytes] Searching for multipoint block descriptor #2...OK 1) <1fc00> 0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK 2) <1fc10> 0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK 3) <1fc20> 0x000000-0x003FFF Chk: 0FA0F5CF CalcChk: 0FA0F5CF OK .......... Multipoint #2: [34 blocks x <16> = 544 bytes] Step #9: Looking for rechecks .. *** Found 41 checksums in POPS8N0906018AB.bin *** DONE! 0 error(s) in POPS8N0906018AB.bin! *** Title: Re: 1.8t checksum is bad?? Post by: TomekBK2 on January 02, 2023, 09:11:43 AM Thanks for the help.
The error was in mpps. Pops work but too hard for me. |