disassemble a binary file ecu

[munro]

guys I always wondered, what is this operation, that is, dissasemblare a binary file to an ecu in order to understand exactly the operations provided by the program eprom in the operate via micro..
someone knows something? I understand that the thing is quite complex and more within the reach of a computer scientist/programmer....there is some good pious soul, that could also explain simplifying a lot, what is it?

[munro]

is there any programmer among us who are familiar with the C language/assembly, or the language to ASCII??

[tranky]

Ask and you shall receive!
I'm not really a programmer certificate, but I coddato a lot in various programming languages.
You have to realize?

[tranky]

Then to explain in the form of "drinking" the composition of a binary file is not readable we have a little step into what I am about to say..
We do realize that you and I (munro) there telefonassimo, between me and you, there is a "tunnel communication" in which transit through my voice messages and your.. if a third of all the contrasts between us 2 can listen quietly to the content of the "tunnel communication".
[I]----[te]
[I]---[and helpful]---[te]
these are the 2 examples as mentioned above.
now let's start with [I] that sending a message is encapsulated behind an algorithm definiamolo XYZ (just to stay in theme with the site, and ecm), which converts the sound into something not understandable to the receiving phase has 2 options:
1) if the sender has the same code as XYZ decrypts the signal and makes it original and "drinking"
2) if the sender or anyone intrude in the transmission does not have a way to listen to the content.
Let's say that this is worth more than the other for communications, but we say that the principle is the same, just the reverse with
[I] = original programming of the ecu
XYZ = the conversion of the file from human readable text (in any language it is expressed formerly always characters and languages must contain)
[tu] = interpreter as winols, ecm, etc, etc
At present I could not tell you with accuracy with which compiler has been created that file, but there are ways to decompile, but it takes time and effort to get the result because the file is in and of itself will be part of a suite alfa/bosch, which will certainly have the source interpreter.
Having that you have the world of tuning between the fingers
I hope I was of help, and especially the clear.. twisted, definitely, but I hope it's clear
Ask me another if you need it

[tranky]

doing a summary: to have XYZ is equivalent to having a driver/damos interpreter of the file only encodes that the damos/driver interprets the ID, the"XYZ" would play the entire composition of the file.ecu

[munro]

ok but if we do not have "xyz" how can we decipher the contents of a micro or eprom?
I seem to have read somewhere that you use the language ASCII...

[munro]

Ask and you shall receive!
I'm not really a programmer certificate, but I coddato a lot in various programming languages.
You have to realize?

the idea and implement in the micro and eprom new functions not provided by the manufacturer, see, for example, multimappa,launch control with als,system bang-bang,etc. this could be done in theory by changing the code strings in the eprom so that the micro in the reading of his routine program implements these functions.

[tranky]

It is the ASCII you see in fact, from the code on the hex dump.
Should I see some files of the EPROM and see the composition.
As soon as I have time I'll take a look.

[munro]

thank you...I like this do..des )

[munro]

dimeticavo if you need some file micro can I post it..