• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 406 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler/TMS320F28379D: Unresolved symbols while compiling

Aditya Ghule
Intellectual 260 points
Part Number: TMS320F28379D


Tool/software: TI C/C++ Compiler

Hi,

I am trying to build a project which includes a few symbols from a header file. I keep getting errors #10010 (errors encountered during linking) and #10234-D unresolved symbols.  I have included the .cmd file in the linked file search path and the header file locations in the compiler path.  I can even see the correct header file in the includes under the project folder.  Not sure what is not working properly.

Any help would be much appreciated.

Thank you,

Aditya

  • 0
    TI__Guru**** 250620 points

    I'm not sure what is going on.  The first suggestion which comes to mind ... Please make sure you organize your functions and global variables as recommended in this FAQ (not from TI).

    Please let me know whether this resolves the problem.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 260 points

    Thanks for the suggestion.  The variables declarations seem to be consistent. The interesting part is I can right click on the particular variables in the actual file and clock open declaration to open the actual header file which I think means that the header file is properly added.  However, building the project still gives the unresolved symbol in the .obj file.

    Thank you,

    Aditya

  • 0 in reply to Aditya Ghule
    TI__Guru**** 250620 points

    I presume you build with Code Composer Studio.  Please conduct the problem build again.  Then save the contents of the Console (not Problems) view to a text file.  Use the icon Copy Build Log.  When you name the text file, be sure to use the file extension .txt.  Attach the text file to your next post.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 260 points

    Hi George, 

    Thank you for the help.  I was able to resolve the issue.   I think there was some problem with the source file linking and adding the files again cleared up the issue.