MSS6x Flasher - Now released!

[cossie1]

terra is the bimmergeeks cable is the same as the one you helped me modify ?

Where I had to reprogram the Atmega chip ?

[terra]

Thanks terra, I'll review the FTDI properties and make sure I don't have any cable confusion. Further test will probably wait until next weekend (dealer appointment to get the silly OC3 weight mat issue warrantied before then).

To verify; a failure with the RSA bypass in normal (aka not-slow) mode will brick the DME beyond WinKFP's ability to recover, will it not?
That was my main motivation for slow mode, as I don't have a bench flash setup or non-factory tools (although this isn't my primary vehicle, I'm still trying to minimize headaches in case of problems).

2nd question: I didn't install a custom or manually-sourced FTDI chipset driver, just used the one Windows 10 pulls when connecting the cable. Does that pose a potential problem for these cables? I've never had an issue with coding/diagnostics, so never went beyond that.

It’s a fairly specific circumstance that will cause the failure in normal mode. Basically if bad bytes are written to the dme during that process and the authentication step is triggered, then yes, the dme will copy that bad data over the boot code and be hosed.

This only really happens when using a normal D-CAN cable on a D-CAN car since those cables have a bug that cause every 253rd byte to be written incorrectly when being used in D-CAN mode. But as far as my application knows, everything was written properly so it proceeds to trigger the authentication step. Normally I would try to mitigate this by reading back some data to make sure it’s valid, but Siemens in their infinite wisdom decided to make the dme unresponsive to read commands when programming is incomplete.

In a K-line car you’re not susceptible to that particular bug. And in the event of a flash failure like what you had, the authentication step isn’t actually triggered, so it shouldn’t try to copy incomplete boot code over.

Not sure about the driver. I think Windows installs the ftdi driver by default.

[Lucky]

I ordered the expert cable (not pro). I also will report whether it worked.

[CaptainPunPants]

Minor Update (Now Version 1.0.0.3)

Changes:

• The application will now default to using the D2XX Driver instead of the Virtual COM Port. This seems to be more stable for K-line mode communications, should not cause any regressions for other cars
  • In this mode, the settings you have in device manager (COM port, latency, etc) shouldn't matter.
  • If you wish to go back to the Virtual COM Mode, Edit the "MSS6x Flasher.exe.config" so that "Port" is set to the COM port you desire (default is now "FTDI0")
  • Note: This will probably not work properly if you have multiple FTDI devices connected at the same time. If you have multiple FTDI devices, you can try to select the specific device you want using the instructions under "FTDI D2XX Properties" here
• Eliminated the slow RSA bypass. Just seemed to create confusion.
• Made some changes so that if one of the stages during a flash process fails, the program doesn't try to perform the subsequent steps.

CaptainPunPants - Might be worth trying this version out with either of your cables.

Thanks terra, I'll review the FTDI properties and make sure I don't have any cable confusion. Further test will probably wait until next weekend (dealer appointment to get the silly OC3 weight mat issue warrantied before then).

To verify; a failure with the RSA bypass in normal (aka not-slow) mode will brick the DME beyond WinKFP's ability to recover, will it not?
That was my main motivation for slow mode, as I don't have a bench flash setup or non-factory tools (although this isn't my primary vehicle, I'm still trying to minimize headaches in case of problems).

2nd question: I didn't install a custom or manually-sourced FTDI chipset driver, just used the one Windows 10 pulls when connecting the cable. Does that pose a potential problem for these cables? I've never had an issue with coding/diagnostics, so never went beyond that.

[Martyn]

Yes you can

[Lucky]

one more question,

the binary modification tool only processes full file, no tune file.
So if i make changes in full file and load it back to MSS6x-flasher, can i nevertheless flash with Button "Flash Tune" ?

[Lucky]

ok, that seems to be all the same i can do with Binary Modification Tool ? Idle Speed, Rev Limit per Gear, all Checkboxes or throttle adjustments. This things all can be flashed with tune.

thanks !

i`ll try, but have do wait for cable

[terra]

does that mean, i have to load the full-file in Binary Modification Tool, then for example i set checkmark to "Vmax Limit Removal" - and then it`s enough to flash only the tune ?

Yep, that should be fine.

[Lucky]

If you're just making modifications to your tune (maps, error codes, etc), you only need to flash tune, and that will not require you do an RSA delete at all. If you're getting more into the code modification side of things, then you'll be messing with flash program, and that does require the RSA delete.

does that mean, i have only to load the original full-file (stock-file) in Binary Modification Tool, then for example i set checkmark to "Vmax Limit Removal" - and then it`s enough to flash only the tune ? no RSA-bypass requiered for this action ?

[terra]

To be able to save the ISN, yes, you have to flash the RSA bypass.

Now honestly, it's not as critical to back that up on an M5 for a few reasons.
1) A "virgin" DME can be synced with the CAS and get the ISN back that way
2) Even if your DME did brick, it's not BDM locked, so the ISN can always be recovered that way.

Extracting the ISN from the DME is more useful if you need to replace the CAS module for whatever reason.

Anyway -

You don't necessarily have to read the full flash again unless you want that backup to have the ISN within that full flash file. You could just copy the ISN to the correct location with a hex editor.

If you're just making modifications to your tune (maps, error codes, etc), you only need to flash tune, and that will not require you do an RSA delete at all. If you're getting more into the code modification side of things, then you'll be messing with flash program, and that does require the RSA delete.

[Lucky]

First thank`s for this wonderful app !

Question: Would it be also possible to use a ICOM instead of Bimmergeeks Interaface ?

and for Beginners another Question:

I have an original 2007 M5, not tuned.

So the first i made, was, to press button "Read full Flash" ,with standard-cable D-Can. The complete reading process took approx 60 minutes. Now there are two files saved, one "full" and one "tune".
After that, i successfuly loaded the "full-file" to Binary Modification Tool".

So that`s it, i`v done so far.

Now please give me help/correction:

1. First to be able to save ISN, I have to flash DME with "Flash RSA Bypass" (only with edibasLib - Cable)
2. Saving ISN

so far it is clear, but then...

3. After step 2, i`ll have to press button "Read full Flash" again ? The bypassed full-file will now be saved on pc. ?
4. Now i have to load this bypassed full-file to Binary Modification Tool, change values and load it back to MSS6x-Flasher. ?
5. So what is to do ? do i have to press Button "flash Tune" or "flash Program" ? I don`t know the difference between these functions. With Binary Modification Tool, it`s not possible to load the tune-file, only full.

sorry for asking, but i`m not familiar with tuning a DME , so please can anybody make step by step guide ?

[terra]

Minor Update (Now Version 1.0.0.3)

Changes:

• The application will now default to using the D2XX Driver instead of the Virtual COM Port. This seems to be more stable for K-line mode communications, should not cause any regressions for other cars
  • In this mode, the settings you have in device manager (COM port, latency, etc) shouldn't matter.
  • If you wish to go back to the Virtual COM Mode, Edit the "MSS6x Flasher.exe.config" so that "Port" is set to the COM port you desire (default is now "FTDI0")
  • Note: This will probably not work properly if you have multiple FTDI devices connected at the same time. If you have multiple FTDI devices, you can try to select the specific device you want using the instructions under "FTDI D2XX Properties" here
• Eliminated the slow RSA bypass. Just seemed to create confusion.
• Made some changes so that if one of the stages during a flash process fails, the program doesn't try to perform the subsequent steps.

CaptainPunPants - Might be worth trying this version out with either of your cables.

[CaptainPunPants]

Martin was instructing omhl, your problem is something else.

My apologies, Martyn. I'm a bit slow on the uptake today...

[terra]

It failed with that option checked AND unchecked. When it succeeded with the old KCAN cable, it was unchecked.

I'm starting to suspect the new cable might be spotty. But I'm also hesitant to try an unnecessary flash with the old cable to test that hypothesis.

Martin was instructing omhl, your problem is something else.

Playing around with K-line mode on my bench, it does seem like there might be an issue somewhere there, though tracking it down is proving to be tough. I think part of the issue might be that K-line mode seems to be straight up faster than D-CAN mode for this purpose. Will see if I can tweak some settings to get it to work a bit better.

Edit: So using the FTDI driver to access the cable instead of the virtual COM port seems to work better. Does suggest it's a speed / timing issue.

[Martyn]

You just need to tick 'force program programming in comfort mode' in WinKFP.