womanwhe.blogg.se

I have got a project set up by previous developer (who left 5 years back) in Softune ide. I have got the binary file (.mhx) which is used to programme the specific IO cards. I will dig into the C drive of this PC to find out more info about the compiler and get back to you if any more info is found. It seems Fujitsu MCU have got their own proprietary compiler which comes as part of IDE. I don’t think the compiler is GCC/similar. Also I was told that this IDE/PC was used to compile the source code previously. Softune IDE installed on a Windows XP pc. If you have something like this look up the options and see what you can do with this it'll have a name where it has a prefix of the architecture it's built to work for, like "avr-objdump" or "tricore-objdump" (ending in. Now if it's gnu/gcc based, the thing you want to start with is "objdump". The best case scenario is that things are just getting linked in a different order, but there's so much more that could be going on do you have any way to know what compiler/linker/other options were used during the original build? map? linker input files (*.ld)? any documentation? any "make" files associated with the original release? (could just be called Makefile with no extension, or end in. What do you have? it sounds like you have source code and an old executable file.

is it gnu based? and before I throw out suggestions related to that. What are you compiling with? I can't seem to find what compilers are available for that particular product. I have seen in some blogs that ghidra might be a useful tool for the job? I have got no experience whatsoever in doing such Decompilation so please be as descriptive as possible ( if there is such a way). mhx file to create original header and source files? This would allow me to get my hands onto the source code. Is there a way to ‘de compile’ (or whatever the correct terminology is) the. This makes me think that most probably some of the external libraries (e.g Can open library which were written by a third party back in the day) may be of a different version to what was used for production executable. When I built the source code and compared the resultant ‘.mhx’ file with the executable (also ‘.mhx’) used in production systems, using a software application called ‘beyond compare’ (For those who are not aware, ‘Beyond compare’ compares the two files bit by bit), the comparison showed quite a difference. The software is written in ANSI-C and based on Fujitsu 16 but MCU. Seems like I have been thrown into the deep end though! I am asked to make some changes to a firmware owned by my company. Hi folks, I have recently managed to get myself in the embedded team in my office.