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.

LAUNCHXL-CC1352P: Issue in linking ''icall_user_config.h" file under the build settings of simple_peripheral project in CCS IDE.

Part Number: LAUNCHXL-CC1352P

Tool/software:

Hi, I have been building my BLE application using "simple_peripheral" project available in CCS IDE. I am making modifications to Extended advertisements to include information of interest for my company to run localization algorithms using BLE extended advertisement's CTE. As such while building the project in CCS v20.1.1 I am encountering the following error:
{
    "resource": "file:///c%3A/ti/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/source/ti/ble5stack/icall/inc/ble_user_config.h",
    "owner": "ccs-client",
    "severity": 1,
    "message": "'icall_user_config.h' file not found",
    "startLineNumber": 121,
    "startColumn": 0,
    "endLineNumber": 121,
    "endColumn": 1000
}

To fix this issue I looked at the directory in which the Simple link cc13xx_cc25xx_SDK is installed on my system and I found out that the "icall_user_config.h" header file is not present in the same folder as "ble_user_config.h". I found out that it is located at the following path - C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack_flash\icall\inc so, I manually included the path by right clicking on simple_peripheral project in my CCS workspace and navigating through the following path: Properties->Build->Arm Compiler->Include options and manually added the path as seen in the screenshot titled "Arm_compiler-path inclusion_ss_8th May.png" (1st screenshot) and also defined the symbol "ICALL_JT" under Predefined Symbols section as seen in the screenshot titled "Predefined symbols definition ss 8th May.png"(2nd screenshot). I want to know if I am following the right procedure for linking the missing file in the Compiler? If not what is the correct way to include a missing file in the Build settings of the project? This issue was not happening before I started making modifications to the code files and it disappeared for two weeks when I was conducting some testing with the modified simple_peripheral.c and simple_peripheral.syscfg files. I have also verified my simple_peripheral.c and simple_peripheral.syscfg files to make sure that the modifications I have made to the code are not resulting in any issues with BLE advertisements and my logic for modifying the advertisements seems correct. I just need to figure out how to properly include the missing folder path in Build settings of the CCS IDE. Any help with the issue would be of immense help to me and help me take the project to the next stage.

Thanks for reading.

  • Hi !

    When importing the simple peripheral project from the F2 SDK, I can see the file in the iCall folder. Can you confirm to me that you see this file in the iCall folder too ?
    (I am using an older version of CCS in my screenshot, but the path should be the same)

    Kind regards,
    Maxence

  • Hi Maxence,

    Thanks for reading my post and getting back to me. I can see the file under iCall folder in my CCS IDE. That's why I am confused why the error is occurring in the first place.

  • Hi,

    Could you show me your entire include settings ? Your screenshot only shows the last lines. Could you also tell me if you modified your ble_user_config.h or the source SDK files ?

    I only just noticed that you included C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack_flash\icall\inc, while you should probably have included C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack\icall\inc

    Kind regards,
    Maxence

  • Hi,

    I have included the path "C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack\icall\inc" in the Include options section under Arm compiler as you mentioned in your response. But when I rebuild the project the path vanishes from the Include options. I don't understand what's happening with the compiler. On close observation I saw that the path is already included under Include options as "${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/source/ti/ble5stack/icall/inc". Can this cause a conflict with my path declaration? Here are the screenshots showing all the paths that are listed under Include options of Build settings -

  • Now the path is visible under Include options of the Arm Compiler section but the error hasn't disappeared. I still think the compiler is not able to locate the missing file even after I have added the path manually. On close observation I found out that the "icall_user_config.h" file is not present in the folder "C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack\icall\inc". In my system the file can be found at the following path - "C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\source\ti\ble5stack_flash\icall\inc". How can I resolve the issue? This is the third time I have formatted the SDK and reinstalled it on my system.

  • Hi !

    Could you try opening a new workspace by opening CCS, and choosing a unique path (like for example C:\Users\<your-username>\t-1511393, and replace <your-username> by your windows username). You can then click the Launch button, and you should be in a completely new workspace with no projects.

    Once you're in a new workspace, import the simple_peripheral for your board by clicking Project > Import CCS projects ... and selecting the path for the simple_peripheral project for your board.

    Once this is done, and the project is successfully imported, can you tell me if you're able to build it ? If you're not able to build it, it's likely that your SDK is broken and that you need to re-install it because you deleted/changed some files in some way.

    Kind regards,
    Maxence

  • Hi,

    I think the SDK is broken. I tried following the approach you mentioned in your previous response and alas it did not work. Also, what should be the procedure to properly install the SDK? If you could share your perspective on it that would be great as my way of installation of the SDK doesn't seem to be working. I deleted the workspace folder manually from my system but for some reason CCS v20.1.1/20.0.2 never shows a new workspace selection window on startup even after enabling workspace selection window under General settings of the Preferences section. Whenever I open up CCS the same workspace folder reappears and I need to import a new instance of the simple_peripheral project in the same workspace folder. Can you share links to any online resources available from TI to help navigate the new version of CCS v20.1.1? Earlier versions of CCS used to provide me an option to select a workspace on startup but the current version 20.0.2 and 20.1.1 are a little difficult to navigate. 

  • Hi !

    You can find the user guide on CCS v20.1.1 here (link).

    To create a new workspace on CCS v20, you can select "File" > "Open Folder", create a new folder where you want to create your new workspace, and select this folder. Once your folder is open in CCS, you can select "File" > "Save workspace as ....", choose a name for your workspace (it can be anything), and save it in the folder you previously created.

    Once you have created your workspace, you can navigate to different workspaces by either selecting "File" > "Open Workspace from File ..." or "File" > "Open Recent Workspace ...".

    To properly re-install the SDK, I would first run the uninstaller located at C:\ti\simplelink_cc13xx_cc26xx_sdk_8_30_01_01\uninstall.exe, download the windows installer for the most recent version (8.30.01.01) of your SDK from here (link) and install it.

    Once all of this is done, could you create a new workspace, and see if building basic_peripheral works ?

    Kind regards,
    Maxence

  • Hi,

    Thanks for sharing a detailed guide on how to create a new workspace in CCS v20.1.1. I will follow the steps mentioned in your response and update you with how things go in a day or two.

    Regards,

    Aditya

  • Hi,

    The fix that you suggested seems to be working well on my system! I am not getting any file inclusion errors which were appearing earlier when I was modifying the 'simple_peripheral' project files. You can see that there are no problems being listed under Problems now. I just need to update the code and verify if I am able to send out extended advertisements from the board. One last thing, Can you provide me a list of resources I can refer for making modifications to Extended advertisement payload? I am following the steps recommended in the following guide for CC1352P-2 board -
    1. https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/developing-with-sdk-index-cc13xx_cc26xx.html#creating-custom-ble-app
    2. https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/gap-cc13xx_cc26xx.html#gap-roles
    3. https://dev.ti.com/tirex/explore/node?devtools=LAUNCHXL-CC1352P-2&node=ABYtVgMNsxxPecvdZK6N3g
    (I am following the guides listed under Training->SimpleLink Academy for CC13xx CC26xx - 8.30.00.00->Bluetooth LE 5)


    Should I refer any other guides to modify advertisement sets and enable or disable Legacy advertisements from the CC1352P-2 board?

    Let me know.

    Thanks,
    Aditya

  • Hi,

    Great to hear ! If switching workspaces worked for you, it's likely that the issue was that you mistakenly deleted the file in your project. You can add the icall_user_config.h file from to the iCall folder from this new working project to your old project and it should work as new.

    As for ressources to make modifications to extended advertisement payload, the main ones you can follow are this SLA (link) on advertisements, and the user guide's chapter on GAP advertisement (link). I also like to have the API (link, but more specifically the advertisement API : link) to have a concrete idea on how to code the things I see in the user guide.

    Kind regards,
    Maxence

  • I will apply the suggested fix in my old workspace and see if it solves the problem that I encountered initially. For now I will start working in the new workspace by following the steps mentioned in the guides you shared with me in your response. Thanks for helping me out Maxence!

    Hope you have a wonderful day.

    Best,
    Aditya