Hi all

I'm just getting started trying to understand what is in the 1Mb flash that was downloaded from my EDC16U1 controlled car.

I thought I'd mention a couple of utilities I've created to help me understand what is going on:

OLS parser: I was going to look at finding the maps in the ECU BIN directly, but then realised that as WinOLS already does that it might be easier to get the "Potential Maps" index data from the OLS file. So far I have a utility that will print out the WinOLS strings it recognises and their offsets+length, such as "00000AB1:09:Start". It may become a dead end, but more of the OLS format is understood it might help with my planned goal or other things.

hexpaint: A utility to print a colour coded hex dump using a "known data" list of offsets+lengths to apply to the file being dumped. So for example munging the output from the prior utility to "00000AB1:09:green" would make identified text items green in the hexdump, implying that anything not green is data that is not yet understood. I can imagine I'll also use this on the ECU BIN to show what parts are maps, code, etc.

Pointers to other tools that do same / similar or avoid the need for them are welcome ;) .

You looking to hardest way possible. To understand what map(s) means you still need a2l. If you recognize one map correctly there are still plenty of them in CAL. Use propper tool, a2l, SW documentation where awailable like "funktionsrahmen" then you will be able to understand what it means in whole SW.

Thanks, and after a bit more review I can see what you mean.

The "Potential Maps" of WinOLS don't seem to match what the online editing aid EDC Master is showing, while that latter set instantly appear useful to help me understand what is where. So trying to use WinOLS' looks like quite a dead end for me for now. Maybe it will be more useful once I understand more.

teşekkürler