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.

  • Resolved

Compiler/TMS320F2808: couldn't generate hex file

Mastermind 23600 points

Replies: 13

Views: 249

Part Number: TMS320F2808

Tool/software: TI C/C++ Compiler

Hello,
customer couldn't generate hex file with hex2000 tool. It generates failures and linking couldn't complete. It can link normal when not using the hex2000 tooI. attached the screenfile with the error message.

Regards, Holger

screenshots.docx

  • Guru 166770 points

    In reply to HS WG-FAE:

    Holger,

    To make progress on this, we would need a test case to reproduce the issue and figure out what is going on. Please check if the customer is able to share their project, or at least a cut-down version of it that demonstrates the problem. Thanks.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Explore Code Composer Studio documentation and resources using online Resource Explorer
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • Guru 166770 points

    In reply to AartiG:

    Holger,

    Is there any update from the customer? Unfortunately there isn't much more we can do without a reproducible test case.

    If the customer still needs time to put together a test case, I will close the thread temporarily and we can always reopen it or create a new thread when we have a test case.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Explore Code Composer Studio documentation and resources using online Resource Explorer
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • Guru 166770 points

    In reply to AartiG:

    Holger,

    Thank you for obtaining and sending over the customer project offline. It seems that this project was converted from CCS 3.3 and the conversion may not have been completely error-free because turning on the Hex Utility uncovered some build errors.

    Here are the steps to get an error-free build:

    1) Go to the Project Properties->Build->Linker, click on Edit Flags and delete the --hex2000 option. This is an invalid linker option and will result in a warning if it is not deleted.

    2) Enable C2000 Hex Utility. Also set the Command-line pattern field as shown below. This is automatically populated for new projects, but for this migrated project the command field was blank for some reason.

    3) Add the --romwidth 16 option.


    4) Building the project at this point generated linker errors that indicate that library files (*.lib) and linker command files (*.cmd) are incorrectly being treated as input files, while the expected object files were not getting passed to the linker. 

    5) To fix this, in the Project Explorer view, select all the .lib files in the lib directory, right-click and go to Resource Configurations->Reset to Default.

    6) Select all build configurations.

    7) Do the same for both .cmd files in the cmd directory.

    8) Rebuild the project. It should complete without errors.


    Let us know if this helps resolve the errors.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Explore Code Composer Studio documentation and resources using online Resource Explorer
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

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.