MSS6x Flasher - Now released!

[Martyn]

I suspect you have an issue with the tach, rather than an issue with the DME software. Personally, if you're happy with the tune, then I'd leave it alone.

Perhaps try a tach/kombi cluster test with INPA and see if it behaves.

[BigRussia]

I suspect you have an issue with the tach, rather than an issue with the DME software. Personally, if you're happy with the tune, then I'd leave it alone.

Perhaps try a tach/kombi cluster test with INPA and see if it behaves.

Cool thanks for that insight, I have INPA so I'll try to see if it can do a KOMBI test of the warmup dial, I didnt even think of doing that so worth a shot!

Yeah no issues with the AA tune, car is a daily with just the AA Signature xpipe and mufflers. The two features of the MSS60 Binary Modification Tool I wanted to use were Engine Temp Rev Limit (and hoping as extra benefit it might also resolve that weird warmup dial issue) and tuning the throttle mappings, since I find Comfort too soggy and dead down low and Sport to be too touchy and stabby in that same initial pedal tip-in, so was looking to tune those closer together like I did on the E46 using the MSS54 Tool (and has been fantastic btw!). Was thinking to make Comfort fully linear if possible.

BTW if anyone is interested I made a thread on M3post about the warmup dial issue, and here's a couple of the most extreme instances lol (usually it gets stuck around 6.5-7.2k RPM ranges when it does mess up, but then will usually sorts itself next drive or overnight):

[terra]

So for whatever it's worth, this application seems to work fine on Windows for ARM, except you need to change the port from FTDI0 to COM1 (or whatever COM port you have the cable assigned to). It appears the ARM version of the FTDI driver doesn't support D2XX mode.

From what I recall, I had used D2XX mode in the first place because I found it to be more stable, but so far it seems stable enough here.

For completeness, this is using an M1 Macbook Pro with Windows 11 for ARM running in VMWare

[terra]

So while I doubt most people will run into this (seems like no one else reported anything similar in the last 6 years) - for future reference if you have an RSA bypass'd DME and later on use WinKFPs expert mode to do some flashing and accidentally pick the wrong DME (i.e MSS60 file on MSS65 or vice versa), the DME will happily overwrite its bootloader with the new one. And this breaks a bunch of things... the DME doesn't actually want to run due to the hardware string not matching, and the RSA keys will no longer match what they should be, so security access is broken and the correct binaries will no longer have a valid signature as far as the DME is concerned. I was able to ultimately recover without BDM with a bunch of hacky changes to my app, but something to keep in mind. Unfortunately I don't think there's a fantastic way for me to protect against that sort of issues. From what I recall, other BMW DMEs would normally not copy the new bootloader if the hardware string doesn't match rather than complaining after the fact.

Good news is that might mean it's possible to crossflash MSS60 code to the MSS65 without BDM using a similar trick to what we do to get the CSL flash to work on non-CSL DMEs. I'll have to dig into the non-writeable code a little deeper to see if there's any major compatibility issues there.

[hobbit382]

interesting, being able to flash the boot section without BDM would be nice.

[terra]

interesting, being able to flash the boot section without BDM would be nice.

So I did try just straight up changing the hardware reference and flashing (and also changing security access keys to the MSS65 ones). While it does accept the flash and respond to some INPA commands, it doesn't seem to boot completely as a lot of commands just don't work. Flashing back to MSS65 code from there worked fine, it wasn't bricked or anything.

That boot section does have a number of differences so I'm not sure replacing it is avoidable, though would have to study the differences closer.

I'm sure mpower32 would have the means to overwrite the boot sector given the other things his software can do (i.e clear censorship mode and restore the flash). I'm not skilled enough to write code to do that reliably myself.