NefMoto

Pulled this file of an audi A4 1.8tq -01.

been using MTX ME7 plugins for a ton of different ecus, allways worked 100%, and even this one says it is compatible, and the plugin "fixes" the checksums.. 
..only when i run me7check on the file it tells me "1 data area checksum failures found".. hmm! =/

all i did was up 1 point in the LDRXN map, and this happens.. now, i dont dare to flash it untill ive worked this out, WHY it cant correct this file.
i ran it thru me7fix, and it couldnt identify this as a me7.5 algoritm.. the mtx plugin said it should be compatible tho..
i read it using the 29f800 mem template, and the original files states NO errors.. i also tried reading it with 29f800bb, and this also states no errors.

what to do, is there something wrong with the file? someone else who could test with the MTX?

the chk is correct

huh?

in the "_mod" file? me7check sais it is not, why is that?  ???



ME7Check v1.11 (c) mki, 06/2004-07/2011
Checking file d:\Motronic 7.5\!tuning\Gson\8E0906018B_A4_01_1.8TQ_mod.bin (size
1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4016.32//24e/Dst04o/190101//
-> Contents of ECUID data table:
   - '0261206868'         (SSECUHN)
   - '1037360990'         (SSECUSN)
   - '8E0906018B  '       (VAG part number)
   - '0004'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


Data area checksum failure(s) found
-> Found 1 error!!!   *******************************

Well the original and 800bb files are identical, so no problems there, but comparing the changes between the original and modified files, i cant immediately see what differences between the files could be in an ldrxn map... What address are you changing for ldrxn?

I have differences at:

1f68e (2)
1fc76 (6)
1fe46 (6)
93000 (4)
939f8 (1)
fffe0 (32)

i have the ldrxn map located at 1F682, so ill bet the 1F68E is the only part that i have changed.. i just raised a value and saved to see if it would correct the checksum, but me7check gives me errors no matter what i do.. =/

Yep, so it is :)

Here's one that checks out ok, with the 1f68e modification, made from the original file. Would be intresting to see if MTX corrects any further changes ok though...

Cheers

hmm.. nope.. the MTX still seem to screw things up.. =S

Hmm indeed... Guess you've found a bug in the MTX checksum routine then. Email their support & see where you get to, but in the mean time if you need a checksum done, just post up the un-mtx'd file with the mods & i'll sort it for you.

ive sent mr.Salvatore a mail about this.

ugh, thats so typical for my ecus.. my 032HN ecu was also the first one to encounter a bug in the MTX me7-2002 plugin, but that is corrected now in the new plugin-version..  ;D


thanks for the offer, thats great  :)
..but i need the ability to tune things right away while im in the car.. and i wouldnt want to post my "top secret tuning techniques" for anyone to look at here.. someone might blow an engine..! hehe  ;D

(there is also some custom code going into this ecu.. which is why i need to be able to alter things right away.. lets hope MTX will look at it asap)

Lol, no worries & hope it gets fixed soon. Offer still stands in the mean time - i have an honest face & won't tell a soul :D

so.. reply back from MTX saying there shouldnt be anything wrong with the file, but instead the me7check app..
which i doubt, since sweegies corrected file shows NO errors and the MTX plugin corrected one shows 1 error in data area.
MTX also tried using winOLS and made the same mod and saved and got the same result as with the MTX-plugin, that is 1 error in data area.

so, question is, what differs in these two files checksum tables, the same mod is made to both, only one point in the LDRXN map is raised, but one file has a bad checksum and the other seems ok.

i dont know if i dare to flash it untill i know for certain that the checksum plugin are working and the sums are 100% correct.. anyone who could compare the checksums of the 2 files and perhaps find out what the MTX plugin(and apparently winOLS) is missing?

..any help with this is much appreciated!  :)

For yucks, can you try ME7Sum (see my sig)?

There still some CRC things its missing, but it would be interesting to see..

thanks nyet, both files checks out ALL OK, but still differs, i dont know how two completely different checksums can still be OK.. note the checksum below..


                                                                       MTX           Corrected
1) <1fbfe>  Adr: 0x000000-0x003FFF Chk:   0x0FA0F5CF   0x0FA0F5CF
2) <1fc0e>  Adr: 0x004000-0x007FFF Chk:   0x0F4716B3   0x0F4716B3
3) <1fc1e>  Adr: 0x008000-0x00BFFF Chk:   0x10DAEBD7   0x10DAEBD7
4) <1fc2e>  Adr: 0x00C000-0x00FBFF Chk:   0x190D4B82   0x190D4B82
5) <1fc3e>  Adr: 0x010000-0x013FFF Chk:   0x08B54495   0x08B54495
6) <1fc4e>  Adr: 0x014000-0x017F4F Chk:   0x0C5A2B96   0x0C5A2B96
7) <1fc5e>  Adr: 0x018190-0x01BFFF Chk:   0x06B18872   0x06B18872
8) <1fc6e>  Adr: 0x01C000-0x01FFFF Chk:   0x0613AD21   0x0613AD21
9) <1fc7e>  Adr: 0x020000-0x023FFF Chk:   0x1578F4EA   0x1578F4EA
0) <1fc8e>  Adr: 0x024000-0x027FFF Chk:   0x0C445F93   0x0C445F93
1) <1fc9e>  Adr: 0x028000-0x02BFFF Chk:   0x17BC2562   0x17BC2562
2) <1fcae>  Adr: 0x02C000-0x02FFFF Chk:   0x1FFFE000   0x1FFFE000
3) <1fcbe>  Adr: 0x030000-0x033FFF Chk:   0x14738621   0x14738621
4) <1fcce>  Adr: 0x034000-0x037FFF Chk:   0x0E781AAE   0x0E781AAE
5) <1fcde>  Adr: 0x038000-0x03BFFF Chk:   0x0FBBCE3A   0x0FBBCE3A
6) <1fcee>  Adr: 0x03C000-0x03FFFF Chk:   0x0F53FF23   0x0F53FF23
7) <1fcfe>  Adr: 0x040000-0x043FFF Chk:   0x0FC852E6   0x0FC852E6
8) <1fd0e>  Adr: 0x044000-0x047FFF Chk:   0x0E7FE5A2   0x0E7FE5A2
9) <1fd1e>  Adr: 0x048000-0x04BFFF Chk:   0x0EDBD4C9   0x0EDBD4C9
0) <1fd2e>  Adr: 0x04C000-0x04FFFF Chk:   0x1036C729   0x1036C729
1) <1fd3e>  Adr: 0x050000-0x053FFF Chk:   0x0E541C1E   0x0E541C1E
2) <1fd4e>  Adr: 0x054000-0x057FFF Chk:   0x0FD2570D   0x0FD2570D
3) <1fd5e>  Adr: 0x058000-0x05BFFF Chk:   0x102AD17D   0x102AD17D
4) <1fd6e>  Adr: 0x05C000-0x05FFFF Chk:   0x11282797   0x11282797
5) <1fd7e>  Adr: 0x060000-0x063FFF Chk:   0x0F2D0F06   0x0F2D0F06
6) <1fd8e>  Adr: 0x064000-0x067FFF Chk:   0x102FD519   0x102FD519
7) <1fd9e>  Adr: 0x068000-0x06BFFF Chk:   0x0ED245BD   0x0ED245BD
8) <1fdae>  Adr: 0x06C000-0x06FFFF Chk:   0x0D8BB012   0x0D8BB012
9) <1fdbe>  Adr: 0x070000-0x073FFF Chk:   0x0F33C4DA   0x0F33C4DA
0) <1fdce>  Adr: 0x074000-0x077FFF Chk:   0x106A3D6C   0x106A3D6C
1) <1fdde>  Adr: 0x078000-0x07BFFF Chk:   0x1096BECE   0x1096BECE
2) <1fdee>  Adr: 0x07C000-0x07FFFF Chk:   0x0EC0068B   0x0EC0068B
3) <1fdfe>  Adr: 0x080000-0x083FFF Chk:   0x0DE9F75C   0x0DE9F75C
4) <1fe0e>  Adr: 0x084000-0x087FFF Chk:   0x0D7E71A9   0x0D7E71A9
5) <1fe1e>  Adr: 0x088000-0x08BFFF Chk:   0x0F126159   0x0F126159
6) <1fe2e>  Adr: 0x08C000-0x08FBFF Chk:   0x0F18BCE4   0x0F18BCE4
7) <1fe3e>  Adr: 0x090000-0x093FFF Chk:   0x10C9A3F9   0x10C9A445     <----THIS!
8) <1fe4e>  Adr: 0x094000-0x097FFF Chk:   0x1168F78A   0x1168F78A
9) <1fe5e>  Adr: 0x098190-0x09BFFF Chk:   0x0E444F23   0x0E444F23
0) <1fe6e>  Adr: 0x09C000-0x09FFFF Chk:   0x0E17232A   0x0E17232A
1) <1fe7e>  Adr: 0x0A0000-0x0A3FFF Chk:   0x0EABD6A6   0x0EABD6A6
2) <1fe8e>  Adr: 0x0A4000-0x0A7FFF Chk:   0x0E4F92D0   0x0E4F92D0
3) <1fe9e>  Adr: 0x0A8000-0x0ABFFF Chk:   0x12823329   0x12823329
4) <1feae>  Adr: 0x0AC000-0x0AFFFF Chk:   0x1FFFE000   0x1FFFE000
5) <1febe>  Adr: 0x0B0000-0x0B3FFF Chk:   0x1FFFE000   0x1FFFE000
6) <1fece>  Adr: 0x0B4000-0x0B7FFF Chk:   0x1FFFE000   0x1FFFE000
7) <1fede>  Adr: 0x0B8000-0x0BBFFF Chk:   0x1FFFE000   0x1FFFE000
8) <1feee>  Adr: 0x0BC000-0x0BFFFF Chk:   0x1FFFE000   0x1FFFE000
9) <1fefe>  Adr: 0x0C0000-0x0C3FFF Chk:   0x1FFFE000   0x1FFFE000
0) <1ff0e>  Adr: 0x0C4000-0x0C7FFF Chk:   0x1FFFE000   0x1FFFE000
1) <1ff1e>  Adr: 0x0C8000-0x0CBFFF Chk:   0x1FFFE000   0x1FFFE000
2) <1ff2e>  Adr: 0x0CC000-0x0CFFFF Chk:   0x1FFFE000   0x1FFFE000
3) <1ff3e>  Adr: 0x0D0000-0x0D3FFF Chk:   0x1FFFE000   0x1FFFE000
4) <1ff4e>  Adr: 0x0D4000-0x0D7FFF Chk:   0x1FFFE000   0x1FFFE000
5) <1ff5e>  Adr: 0x0D8000-0x0DBFFF Chk:   0x1FFFE000   0x1FFFE000
6) <1ff6e>  Adr: 0x0DC000-0x0DFFFF Chk:   0x1FFFE000   0x1FFFE000
7) <1ff7e>  Adr: 0x0E0000-0x0E3FFF Chk:   0x1FFFE000   0x1FFFE000
8) <1ff8e>  Adr: 0x0E4000-0x0E7FFF Chk:   0x1FFFE000   0x1FFFE000
9) <1ff9e>  Adr: 0x0E8000-0x0EBFFF Chk:   0x1FFFE000   0x1FFFE000
0) <1ffae>  Adr: 0x0EC000-0x0EFFFF Chk:   0x1FFFE000   0x1FFFE000
1) <1ffbe>  Adr: 0x0F0000-0x0F3FFF Chk:   0x1FFFE000   0x1FFFE000
2) <1ffce>  Adr: 0x0F4000-0x0F7FFF Chk:   0x1FFFE000   0x1FFFE000
3) <1ffde>  Adr: 0x0F8000-0x0FBFFF Chk:   0x1FFFE000   0x1FFFE000
4) <1ffee>  Adr: 0x0FC000-0x0FFFFF Chk:   0x1FFDE002   0x1FFDE002

If you bin diff the two files, they probably have differences in that region; as i said, i think there are definitely gaps in ME7Sum's coverage... it could be that MTX is correcting something in 0x090000-0x093FFF that ME7Sum doesn't know how to correct :(

Bummer. Doesn't surprise me... I hope someday somebody can help me fix ME7Sum.

nyet: there are NO differences in that region, that i can find, and the "corrected" file is NOT corrected using me7sum.. also, the corrected file is verified to be 100% working.

from what i can tell the MTX plugin is calculating this sum wrong, and even me7sum flags it as OK, which seems strange.. two different checksums cannot be OK, then they arent checksums.. forwarded this to MTX, but no reply as of yet.

If you'd like I can run it through winols (2.36) and let you know what I see.

have at it..!  ;D

the only thing modified in both files are one point in LDRXN at 0x1F68E

Winols reports both files are good to go with no checksum errors. Have you tried any other versions of me7check?

tried all available versions, all report the same error.

OBVIOUSLY the checksum is different in the two files, i can tell by comparing the files, question is why.. and IF the ECU will complain when flashing the file.

checksums are checksums and not random numbers, you wouldnt end up with two different sums for the same identical data area unless something is wrong in the algoritm..

If there are differences between the files the checksums would be different-it's not like you have two IDENTICAL files with different checksums is it? Personally, I'd flash the file. Winols says it's good, no warnings, errors, or patches required.

but the files are supposed to be identical.. only change made is the LDRXN point, identical in both files, and then saved..
one checks out OK and the other dont using me7check.

19 bytes different when I compared them.

yes, i can see that.. but that is the plugins doing.. found differences at:

1FE46
1FE47
1FE4A
1FE4B

939FC

FFFE0
FFFE4

so, mostly checksums.. but that 939FC seem to be the thing me7check dont like.. is that a checksum too, or why did it get altered.. any ideas?  :)

If you post the modded file BEFORE you correct the sums, and the original, that would be good. I'll correct it with winols and compare it to the one mtx corrected (I assume that's the "mod" correct?)

ah, thats one approach.. ive prepared the file, took the oem file and only did the ldrxn point change while the mtx plugin was disabled, lets see which sum you end up with using OLS..  ;D

"mod" is indeed the MTX corrected file.

I just corrected it with winols...


==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\Documents and Settings\User1\My Documents\Downloads\Try.bin (si
ze=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4016.32//24e/Dst04o/190101//
-> Contents of ECUID data table:
   - '0261206868'         (SSECUHN)
   - '1037360990'         (SSECUSN)
   - '8E0906018B  '       (VAG part number)
   - '0004'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


-> No errors found. File is OK.   *********************

And these are the differences between my corrected file, and yours. Doesn't make much sense assuming the change between them was the same.

(http://i50.tinypic.com/2po351h.jpg)

When you have a file changed to your liking, send it to me BEFORE checksumming it. Let me correct it for you.

well.. im glad we got the same result, 100%.. not so glad the MTX corrected file seem to have errors in the checksums  :(
..and no more replies from MTX after he said he got the same result with winOLS.. which apparently is not the case if you correct the "not corrected" file.

i do wonder why winOLS sais the file is correct AFTER the mtx plugin has corrected it, when it infact isnt.. somethings gotto be flawed in the checksum algoritm.


just to verify, i opened a new oem file in tunerpro, made the same change and saved, ended up with 100% identical file, with error  :-\

thanks for the offer, but as i stated early in the thread, i need to have this sorted so i can tune the car while im in it..  :)

That file you JUST posted, that says MTX corrected is 7 bytes different than my winols corrected file.

Just to get this straight-

The file you made 1 change to and uploaded uncorrected is the same one you JUST uploaded but corrected by MTX?

This makes very little sense to me. I'll have a me7.5 ecu later this week, I'll flash your file to it and cycle the power a few times, see if it throws a checksum error.

You can try ME7Sum... it should work even with the limitations i know of unless you modify stuff outside of maps.

8165c8165
< 001fe40: 8900 ff3f 8900 f9a3 c910 065c 36ef 0040  ...?.......\6..@
---
> 001fe40: 8900 ff3f 8900 45a4 c910 ba5b 36ef 0040  ...?..E....[6..@
37792c37792
< 00939f0: 9870 9880 9890 db00 331f c000 80e0 3fff  .p......3.....?.
---
> 00939f0: 9870 9880 9890 db00 331f c000 cce0 3fff  .p......3.....?.
65535c65535
< 00fffe0: 9a3b 9324 65c4 6cdb ffff ffff ffff ffff  .;.$e.l.........
---
> 00fffe0: e63b 9324 19c4 6cdb ffff ffff ffff ffff  .;.$..l.........