Stumbling through... Flashing CSL bin file

[Keith_MN]

Car: 2004 SMG that got swapped to 6MT and CSL intake/Map sensor.

Attempting to flash to the CSL terra.bin file and running into issues. I've read the threads, was inspired by this one as it sounded easy enough.

I've used INPA in the past, so I opened that up as I knew what that would look like with a successful connection. Sure enough my COM ports had changed so had to get that straightened out. Verified connection.

Fired up MSS Flasher.
Clicked: Identify ECU
Normal results
Read tune, then saved that .bin file
Open FullBinary, opened the terra.bin file and it gives me the following:

File is for ECU id d77cb
Fullbinary ECU id d77cb not supported

Stuck. No history I can find with this error. Did I miss something?

[discoelk]

Did you verify that you have an MSS54HP ECU? Iirc that was a mid-2004 changeover.

[karter16]

Screenshot of MSSFlasher after the ECU ident and showing the error would be helpful OP. What was the file size (in kb) of the tune binary that you read off?

Also not directly related to your problem, but I would gently encourage you to check out MSS54HP CSL 0401 Community Patch Binaries (conflict of interest statement: this is my project) as the binaries contain several small improvements that have been figured out in the time since Terra built his binary.

[Keith_MN]

Did you verify that you have an MSS54HP ECU? Iirc that was a mid-2004 changeover.

Confirmed, pulled DME to double check. Part # 7835564, states "DME MSS54HP"

Screenshot of MSSFlasher after the ECU ident and showing the error would be helpful OP. What was the file size (in kb) of the tune binary that you read off?

Also not directly related to your problem, but I would gently encourage you to check out MSS54HP CSL 0401 Community Patch Binaries (conflict of interest statement: this is my project) as the binaries contain several small improvements that have been figured out in the time since Terra built his binary.

Saw that in my research, noted and may try one of those.

Will give it another shot later tonight and will post screenshots.

[discoelk]

You can also flash with other complete US binaries to rule out hardware issues.

[nextelbuddy]

Is the problem possibly that when you buy Ms flasher you buy one license that locks to a DME... And when you worked with your original file it locks it to that and then now you're trying to work with a different DME program and tune file which will require a separate license?

[Keith_MN]

Didn't have time last night but...

Let's back up. I understand that each person will have a somewhat unique experience based on their set up, but there is too much conflicting information for my brain to handle. A few examples...

How to flash the DME using MSS Flasher.
We have this video which is the main one shown on their download page

https://www.youtube.com/watch?v=XE93bSA_oLA&t=252s

They also have this video that is doing the same thing (flashing CSL), but...different steps, process. Neither have an actual explanation.

https://www.youtube.com/watch?v=odtFf9lEp0o

The tool has changed since these videos and there are some checkboxes that are not explained. Is there any "user manual" documentation of this tool? Didn't find much.

There's this post

https://nam3forum.com/forums/forum/special-interests/coding-tuning/182484-csl-airbox-diy-ecu-flash

Which lines up with the first video I linked above and is essentially what I attempted to do.

There's this post which is far more thorough.

https://nam3forum.com/forums/forum/special-interests/coding-tuning/32103-double-checking-csl-tune-conversion-flashing-process-for-mss54hp-non-csl

I understand the ecuworx step and the cam offsets that need to be updated, but steps 1 & 2 are confusing to me. It's the same full binary loaded twice? Then they read the partial and modify that rather than loading a partial as shown in the other example. (?)


Can anyone provide more context? It seems like the base level steps of the process should be consistent but I can't find a definitive DIY for that.


wrenches > keyboards

[karter16]

I understand the ecuworx step and the cam offsets that need to be updated, but steps 1 & 2 are confusing to me. It's the same full binary loaded twice?

The reason for this is that the flashing of the program binary and the flashing of the tune binary are separate "functions" within the DS2 interface that is used to program the ROM.

Full binaries contain the entire memory space from 0x0 to 0x7FFFF (for each processor), so 0x0 thru 0xFFFFF in total).

In step 1 you are programming the new program binary (the region of memory between 0x10000 and 0x7FFFF).

In step 2 you are programming the new tune binary (the region of memory between 0x8000 and 0xFFFF).


The way that the OP has done it in that link is to tell MSSFlasher that he wants it to use the Tune binary that is contained in Terra's full binary. Hence checking the "use fullbin" button. The alternative is to take the separate Terra tune file and use that, as your tune file, in which case you don't need to check the "use fullbin" checkbox when doing the 2nd flash.


Agree that a comprehensive guide would be useful here.