woj
|
|
« Reply #5 on: February 26, 2018, 12:16:47 PM »
|
|
|
This seems to be a bit old, nevertheless... I guess fixing the checksum for you for one bin will not help you? I have my own checksum procedure for this that fixes everything (or so I think), but I won't share it. I can fix a bin for you though.
If you only update the calibration data, then most tools should be able to deal with it, MPPS for example. However, a user here reported to me that CMD bricked the ECU after the _UM maps have been changed, these maps are under a separate calculation block. Or so was my interpretation of the information I got from him. I did not get a chance to see if MPPS fixes this one though.
(There are also rare instances of the ME7.9.10 bins that have the calibration block included in one other global checksum, which makes the flashing in data only mode problematic, but solvable. The posted bin is not one of these.).
If you do code changes and need to fix the complete file, then there are one or two (depending on what exactly was changed) more check sums that need attention. In particular, the first flashing block 0-0x1FFF IIRC has one at the end, if that one is not right, the ECU will stop mid flash procedure.
Also, why boot? These ECUs (at least for the calibration data block) flash beautifully over OBD...? Then, on the other hand, if in boot mode, why not try it with your tool, if you brick it, you revive it in boot mode.
|