John-
> I have some .h files that contain the dsp binary
code. These .h files are
> generated by COFF2C. And I want to get the assembly code from these .h file
> what should I do? Or anyone knows how COFF2C generated .h file with coff
> file so I can write a tool to make .h back coff.
coff2c does not generate source code from a COFF file and is not a step in
that
direction. It extracts COFF sections -- executable code (.text section),
.const,
.cinit, and any other other initialized sections -- and stores in a standard
.h
file. There is some C code that goes along with it that you can use to load
the
sections into a TI DSP at run-time; i.e. before releasing Reset.
It's basically a free version of TI's hex6x.exe and hex500.exe
programs -- they
functionally accomplish the same thing.
Here is a page with an example of using coff2c:
http://www.cadenux.com/bsp/CadenuxArmDriverGuide.html
The above page describes how to load a DSP executable from an ARM core for
dual-core
TI devices, for example C5471, various DM2x, DM2x, and DM6x, devices and OMAP
1510,
5910 and other OMAP devices.
-Jeff
Re: how to generate the assembly code from a .h file generated by COFF2C
Started by ●November 17, 2008
Reply by ●November 18, 20082008-11-18
Jeff,
Thanks for your reply. But what I want is not make .h file from coff file, I
want to make a .h file back coff file. So I want to know how COFF2C extract
the coff file to a .h file. Is there any detail document about that?
On 11/18/08, Jeff Brower wrote:
>
> John-
>
> > I have some .h files that contain the dsp binary code. These .h files are
> > generated by COFF2C. And I want to get the assembly code from these .h
> file
> > what should I do? Or anyone knows how COFF2C generated .h file with coff
> > file so I can write a tool to make .h back coff.
>
> coff2c does not generate source code from a COFF file and is not a step in
> that
> direction. It extracts COFF sections -- executable code (.text section),
> .const,
> .cinit, and any other other initialized sections -- and stores in a
> standard .h
> file. There is some C code that goes along with it that you can use to
> load the
> sections into a TI DSP at run-time; i.e. before releasing Reset.
>
> It's basically a free version of TI's hex6x.exe and hex500.exe programs --
> they
> functionally accomplish the same thing.
>
> Here is a page with an example of using coff2c:
>
> http://www.cadenux.com/bsp/CadenuxArmDriverGuide.html
>
> The above page describes how to load a DSP executable from an ARM core for
> dual-core
> TI devices, for example C5471, various DM2x, DM2x, and DM6x, devices and
> OMAP 1510,
> 5910 and other OMAP devices.
>
> -Jeff
>
Thanks for your reply. But what I want is not make .h file from coff file, I
want to make a .h file back coff file. So I want to know how COFF2C extract
the coff file to a .h file. Is there any detail document about that?
On 11/18/08, Jeff Brower wrote:
>
> John-
>
> > I have some .h files that contain the dsp binary code. These .h files are
> > generated by COFF2C. And I want to get the assembly code from these .h
> file
> > what should I do? Or anyone knows how COFF2C generated .h file with coff
> > file so I can write a tool to make .h back coff.
>
> coff2c does not generate source code from a COFF file and is not a step in
> that
> direction. It extracts COFF sections -- executable code (.text section),
> .const,
> .cinit, and any other other initialized sections -- and stores in a
> standard .h
> file. There is some C code that goes along with it that you can use to
> load the
> sections into a TI DSP at run-time; i.e. before releasing Reset.
>
> It's basically a free version of TI's hex6x.exe and hex500.exe programs --
> they
> functionally accomplish the same thing.
>
> Here is a page with an example of using coff2c:
>
> http://www.cadenux.com/bsp/CadenuxArmDriverGuide.html
>
> The above page describes how to load a DSP executable from an ARM core for
> dual-core
> TI devices, for example C5471, various DM2x, DM2x, and DM6x, devices and
> OMAP 1510,
> 5910 and other OMAP devices.
>
> -Jeff
>