• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 5050 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS v5.5 fatal error #16000: object files have incompatible formats

MikeH
Guru 15580 points
Other Parts Discussed in Thread: MSP430F5515, MSP430WARE

I am attempting to build a MSP430F5515 project using the MSPware V1.40 library. I have successfully cleaned & built the MSPware library in the ELF format. I have included the library in my F5515 project  and attempt to build using the ELF format, but keep getting the following error:

-l"C:\ti\ccsv5\ccs_base\msp430\MSP430ware_1_40_00_24\driverlib\5xx_6xx\CCS\driverlib.lib" -l"libmath.a" -l"libc.a"
fatal error #16000: object files have incompatible formats
<Linking>

>> Compilation failure
("C:\ti\ccsv5\ccs_base\msp430\MSP430ware_1_40_00_24\driverlib\5xx_6xx\CCS\dr
iverlib.lib<ucs.o>" = TI-COFF, "./F5xx_F6xx_Core_Lib/HAL_UCS.obj" = ELF)
gmake: *** [ARL100_MSP.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

What could be causing the library file (ucs.o) to be considered COFF?

  • 0
    TI__Guru* 84225 points

    You may not have cleaned the old MSPware library thoroughly enough.  From the command line, try running the command

    ofd430 C:\ti\ccsv5\ccs_base\msp430\MSP430ware_1_40_00_24\driverlib\5xx_6xx\CCS\driverlib.lib

    For each member of the library, it will print a file header which will tell you whether the file is COFF or ELF.  Check to make sure that there isn't a duplicate ucs.o in the library.

  • 0 in reply to Archaeologist
    Guru 15580 points

    Arch,

    Would you mind taking a look at the file. I'm not quite sure what I am looking for.

    5305.coff_parse.txt

    Thanks!

  • 0 in reply to MikeH
    TI__Guru**** 244710 points

    For each file, look at the first few lines of the dump.  For example ...

    OBJECT FILE: uart.o

    Object File Information

    File Name: uart.o
    Format: TI-COFF Version 2

    That's COFF.  There is also this ...

    OBJECT FILE: uart.obj

    Object File Information

    File Name: uart.obj
    Format: ELF Version 1

    That's ELF.  I picked these two on purpose.  The only difference in the file names is the extension.  One is COFF, the other is ELF.  I'm not really sure how this happened.  But it is not going to work.

    One suggestion that may help ... When rebuilding the libraries, start by completely deleting the existing ones.

    Thanks and regards,

    -George

  • 0
    Guru 92251 points

    MikeH said:
    I am attempting to build a MSP430F5515 project using the MSPware V1.40 library. I have successfully cleaned & built the MSPware library in the ELF format. I have included the library in my F5515 project  and attempt to build using the ELF format, but keep getting the following error

    When msp430ware_1_40_00_26/driverlib/5xx_6xx/CCS project is imported into a CCS 5.5 workspace .o object files created in COFF format are placed in the top level directory of the project. When the project is re-built in CCS .obj object files are built in the debug sub-directory of the project.

    Both the .o and debug/.obj files get added by the librarian to the driverlib.lib library. If the driverlib project is changed to from COFF to ELF then the driverlib.lib ends up containing:
    - .o object files in the original COFF format
    - debug/*.obj object files in ELF format

    The "solution" is after importing the driverlib project into the CCS workspace, is to delete the .o and .nfo files from the top level directory of the project, before re-building the project.

  • 0 in reply to Chester Gillon
    Guru 15580 points

    Chester,

    Bingo! That's exactly what happened! Thanks for the answer!