Posted on May 17, 2011 at 11:33There is an ELF / IEEE-695 converter, but with limitations.
1/ In a MS-DOS window :
objcopy9 --output-target=ieee filename.u filename.iee
where filename.u is the project executable file.
2/ Creating a command in STVD9 V6 : Tools -> cutomize :
Command : $(ToolChainPath)\objcopy9.exe
Argumenst : --output-target=ieee $(ExeName) $(ExeShortName).iee
Initial Directory : $(ExePath)
3/ Limitations
--
The converstion works for small test files we use. But:
a) it miss a lot of information (all debug information)
b) we have convention for register address which is not standard and must be interpreted.
You have to know that :
a) in ELF format you have 2 kinds of descriptors :
- standard symbol descriptors
- specific symbol descriptors to pass user specific information.
This descriptor is used to pass ''near'' and ''far'' function and data qualifiers.
b) in STABS format you have only standard symbol descriptors. So it is why we add extension to this format to pass ''near'' and ''far'' function and data qualifiers.
So, producing only ELF data from ELF/STABS format to IEEE-695 format produces no error but the IEEE-695 reader must intepret the specific symbol descriptor to understand the address (address on 16 bit or on 24 bit).
Of course, for ELF/STABS data from ELF/STABS format to IEEE-695 format does not work because extension are unknown by translator software. We have to add this information to this translator software.
So, for both (ELF alone and ELF/STABS) translation tool must be modified.
The ST9V6 toolchain must be modified only for ELF/STABS conversion.
-------
We are still waiting for feeback from customers before doing any toolchain modification and documentation on it.
[ This message was edited by: Romain on 03-03-2003 11:44 ]
