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/CC2642R: C/C++ Search Results Issues

Part Number: CC2642R

Tool/software: Code Composer Studio

I'm using CCS 9.0.1.00004.  Our custom project is based on the ti-rtos simple_peripheral example project from the simplelink_cc13x2_26x2_sdk_3_10_00_53 SDK.

We have a custom Bluetooth service that is added to the device profile via the CustomService_AddService() function, which is prototyped and defined in custom_service.h and custom_service.c respectively.  This function is called by custom_profile.c, which is a modified and renamed version of the simple_peripheral.c source file the example project started with.

I was trying to find where that CustomService_AddService() function was being called, so I used Ctrl-H to bring up the Search dialog and did a C/C++ Search for the function name.  It found the definition in its source file, and the function prototype in the header file; it did NOT find where the function was actually called, in custom_profile.c.  I found it manually, and even tried to search for it by copying the name from the file, which is definitely part of the project, as I was staring at it, and made sure it's not some issue of search scope or case sensitivity etc.  Does not find it.

If I use the File Search tab to search the project, however, it finds everything from before, plus the call to it that I'm staring at.  But the C/C++ Search doesn't find it, even though it has to be in the active code because I can build the project, load it onto the board, connect with a Bluetooth device, and interact with that very service.  So, what is with the C/C++ search?  Is it broken?  Should I not use it?  It's making me nervous that something in my project isn't set up properly, and parts of CCS are ignoring source files.

  • Hi Chris,
    I imported the simple peripheral example and I see the issue you describe. In my case, it is calls made from simple_peripheral.c that are not getting picked up by the C/C++ search. It is very old... it seems just that file. I'm investigating and will keep you posted of any updates.

    Thanks
    ki
  • After some analysis by the engineering team, it appears that there is a bug with the indexer where it is unable to properly index that file. That is the root cause of the issue. The indexer is developed and maintained by Eclipse and a bug has been opened against the indexer:
    bugs.eclipse.org/.../show_bug.cgi

    Thanks
    ki