Compiler/TMS320C6713B: Can I force Compiler version 7.4 to generate a COFF1 file rather than a COFF2 file

Shaunak Shilimkan

Part Number: TMS320C6713B

Tool/software: TI C/C++ Compiler

Hi,

I am trying to upgrade to C6000 compiler v7.4, however, I noticed that the binary output by the linker is a COFF2 file. Our legacy code expects a COFF1 file. Is there a way I could force the compiler to generate a COFF1 file. I already tried the linker option -v1.

Thanks very much.

Regards,

Shaunak

over 8 years ago

George Mock over 8 years ago

TI__Guru**** 244470 points

Shaunak Shilimkan said:
Is there a way I could force the compiler to generate a COFF1 file.

Unfortunately, no.

Shaunak Shilimkan said:
Our legacy code expects a COFF1 file.

So, you have some tool that reads the output of the linker, and it expects COFF1?

Thanks and regards,

-George

Shaunak Shilimkan over 8 years ago in reply to George Mock

Intellectual 610 points

Hi George,

Yes we have a tool that copies .text, .data etc sections in the SDRAM. This runs before c_init00 and then branches control to c_init00. It is like a bootstraper.

Regards,

Shaunak

George Mock over 8 years ago in reply to Shaunak Shilimkan

TI__Guru**** 244470 points

COFF2 was introduced some 15-20 years ago. At this point, unfortunately, your choices are to keep using the old compiler, or update your bootstrap like tool.

Thanks and regards,

-George

Archaeologist over 8 years ago in reply to Shaunak Shilimkan

TI__Guru* 84225 points

You should consider switching to using copy tables, perhaps BINIT. Copy tables copy select text and data objects from their load address to their run address, and the linker does all of the bookkeeping for you.

Code Composer Studio™︎

Code Composer Studio forum

Compiler/TMS320C6713B: Can I force Compiler version 7.4 to generate a COFF1 file rather than a COFF2 file