• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 211 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.

TMS320F280040-Q1: a compiling issue of unsolved symbol under CCS that is not understood

Crane Shao
Intellectual 910 points
Part Number: TMS320F280040-Q1


Hello,

I am having this issue that is beyond my knowledge. Can anyone help with this?

Here is the compiling issue: unsolved symbol f_mkfs. 

This function is declared and defined together with f_mount() and f_open(). So it should have no problem searching for this file.

When I copy the declaration and definition to the same file as where fsTest() is defined. There will be no this issue. So it should have no problem in calling this function f_mkfs().

When I click "open declaration" on the function in the head file, it indeed doesn't open the function in the source file.

Is it possible that the file is too large for the compiler to find the function in the file?

Here is how the function is called and the compiling error information. 

Thanks!

Crane

  • 0
    TI__Guru 50611 points

    Crane,

    Looks it is linker error. Please review console log. The log will have more information.

    When f_mkfs() is in the same file with f_mount() and f_open(), please make sure it is not controlled in some build configuration (inside #ifdef #endif).

    If that is not the case, can you rebuild the index of the project. Right-click the project and select index as shown in the image below.

    Regards, Santosh

  • 0 in reply to Santosh Jha
    Intellectual 910 points

    Thanks Santosh for your reply.

    The console log doesn't provide any addition information.

    And it doesn't work to rebuild the index.

    Then I check if it is in #ifdef, I found it in a place that is a little far from this function. I didn't think of that this function could possibly in control of build configuration.

    Now it is addressed. 

    Thanks!

    Crane