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.

LP-AM243: Why Declarations search to get 0 match and References search to get only 1 match (itself)?

Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Dear Experts,

My CCS 12.8.0 seemed to be working strangely:

Both "References" search in Workspace and "Declarations" search in Workspace were unable to get more information?

It seemed that my installed CCS was not functioning well.

Do I need to re-install? Or I can change some settings to correct these problems?

Please help.

Thank you very much.

Best Regards, JasonC.

  • Hello,

    Did you build the project first? Some of the functions and header files referenced need to be generated by sysconfig first. If you try to search for System_init() before ti_drivers_config.h and ti_drivers_config.c is generated in the <build config>/syscfg folder by SysConfig then you will not be able to find the declaration.

    Thanks

    ki

  • Hello Ki,

    Thank you very much for reminded me about to do "Build".

    I noticed that I got error during the build-process on the example-code, and that was the reason I couldn't use "Declarations search in workspace" function. 

    I tried to click debug and then the "build all" error disappeared, and then inside no-error debug perspective, I could see the search result for "Declarations in workspace" now.

    Conclusion: The "Declarations search in workspace" could only function if there is no "build" error.

    Why not provide the "Declarations search in workspace" function even if the "build" has error?

    I think even if the "build" has error, that "Declarations search in workspace" function could still be very helpful for designers to use CCS to improve/debug the code.

    Thank you.

    Best Regards, JasonC.

    ps. I have another thread to asked the problem of that strange error only to appear by clicking "build-all", but that error disappear by clicking "Debug".

  • Conclusion: The "Declarations search in workspace" could only function if there is no "build" error.

    Actually, the dependency is not on a successful project build. It is that the file it is dependent on must exist. That particular file is generated when the sysconfig file is built. So it looks like the build issue you had earlier was with sysconfig.

    Why not provide the "Declarations search in workspace" function even if the "build" has error?

    As mentioned above, it is not that the build had an error. It is that the file in question did not exist. You will not have issues with other files that already exist, even if the project build failed.

    Hope that clears things up.

    Thanks

    ki

  • Hello Ki,

    Thank you very much.

    You helped me again by clarify my wrong impressions. 

    Best Regards,  JasonC.