Hi everyone,

I disassembled a .bin file and I use EASy68K to try to understand this assembled code but do you know if it is possible to decompile this code to an higher level like C++ ?

If it is not possible I will continue to try to understand this assembled code. Here below a piece of the subroutine "subroutine_1BBE0". I have two questions about it :
- I don't understand the use of "arg_2 = 6" and "arg_7 = $B" in the code. And I don't succeed in testing this code in EASy68K. Can someone explain the use of them and what "move.w arg_2(sp),d0" does ?
- EASy68K doesn't seem to recognize "tbls" instruction. Is it possible to simulate this instruction with EASy68K ?



Thanks for all,
Vincent

arg_2 = 6 is probably how the assembler used for this code defined a constant. EASy68K uses EQU:



tbls is an instruction used by the 68331 and 68332 microcontrollers:
https://www.nxp.com/products/processors-and-microcontrollers/additional-processors-and-mcus/coldfire-plus-coldfire/coldfire-microcontrollers-legacy/m683xx/32-bit-microcontroller:MC68331
It is not supported by EASy68K.

_________________
Prof. Kelly

Ok thank you. I have another instruction that EASy68K doesn't know and I don't understand with what d0 is added :

The address modified is A0 + (D1.W * 4).
D0 is added to the data at that address.

_________________
Prof. Kelly

Ok thank you but what does "*4" mean in this instruction because EASy68k understands this instruction but without the "*4"

Multiply by 4. That syntax is not supported by the 68000. It was added to later versions of the 68K family.

_________________
Prof. Kelly

Thank you

Alternately, I suspect that the 'arg_x' was placed by the disassembler instead of simply leaving the displacement in the assembly notation.

I don't think that variable or data declarations are typically left in binary files. (are they)? What disassembler are you using?

Is the binary that you're analyzing from the car in your username? if so, would you like to talk more about disassembly? I've spent an unfortunate amount of time looking at the assembly code from my (british) car, but have not really found anyone to talk to about it.

edit: nevermind- i found you over on the M3 forum.. this is a rabbit hole that I should probably not go down...

I don't think that this is easily done. I could conceive a path to do so if you knew what compiler was used to generate the code, but it's still a tremendous amount of work.



move the 16-bit word 'arg_2' bytes past the stack pointer onto data register D0

Multiply by 4 is now compatible in newer versions. updated your applications