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.

CC2650: Errors when building simple_peripheral_cc2650lp_app

Part Number: CC2650
Other Parts Discussed in Thread: SYSBIOS, CC2640R2F

Hello all,

I am new to the the Bluetooth development platform, and currently trying to run the example project (shown in the title) on the CC2650 launchpad. I am able to build the stack without issues, but I get issues when attempting to build the app. I have been using the software developers guide to walk me through setting up CCS and installing TI-RTOS, along with the BLE stack.

Version of code composer studio: 7.4.0.00014

Ti-compiler: TI v16.9.4.LTS [TI v16.9.6.LTS]

When I build the app project I get the following errors:

From the console output, it appears that the program cannot find "xdc/std.h" and it is also having issues with the "app_ble.cfg" file. I have been trying to figure this out for more than 5 hours and I can not solve this issue. Any help from the experts is greatly appreciated. If any more relevant information is needed, please let me know.

  • It appears that my image got corrupted. Here is an build output from CCS:

    configuring app_ble.xem3 from package/cfg/app_ble_pem3.cfg ...
    generating custom ROM library makefile ...
    Starting build of library sources ...
    making C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650bp/simple_np/ccs/config/src/sysbios/rom_sysbios.aem3 ...
    make[1]: Entering directory 'C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650bp/simple_np/ccs/config/src/sysbios'
    clem3 C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c ...

    >> Compilation failure
    make[1]: Leaving directory 'C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650bp/simple_np/ccs/config/src/sysbios'
    Build of libraries failed.
    TOOLS/subdir_rules.mk:12: recipe for target 'build-697704673-inproc' failed
    "C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c", line 36: fatal error: cannot open source file "xdc/std.h"
    1 catastrophic error detected in the compilation of "C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c".
    Compilation terminated.
    make[1]: *** [makefile:59: rom_sysbios.obj] Error 1
    gmake: *** [C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650bp/simple_np/ccs/config/src/sysbios/rom_sysbios.aem3] Error 2
    error: xdc.cfg.SourceDir: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/cfg/SourceDir.xs", line 209: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:

    js: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!
    gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Error 1
    gmake.exe: *** Deleting file `package/cfg/app_ble_pem3.xdl'
    gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Deleting file `package/cfg/app_ble_pem3.h'
    gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Deleting file `package/cfg/app_ble_pem3.c'
    js: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake[1]: *** [build-697704673-inproc] Error 1
    gmake: *** [build-697704673] Error 2
    TOOLS/subdir_rules.mk:9: recipe for target 'build-697704673' failed
    gmake: Target 'all' not remade because of errors.

    **** Build Finished ****

  • Hi,

    I am also having issues building example programs from BLE Stack 2.2.5. Try BLE Stack version 2.2.1. You need ARM Compiler 5.2.6 installed.

    -kel

  • Hi,

    I take back what I just replied. I was able to build the simple peripheral from BLE Stack 2.2.5 and just got some ARM Compiler version warnings. I am using CCSv9.2.

    With your problem seems you need to install the required tirtos_cc13xx_cc26xx_2_21_01_08 and xdctools_3_32_00_06_core.

    -kel

  • Adan,

    I will assign a member of the team to help you.

    -Luis

  • Hi,

    Just like Markel, I can also build the CC2650 projects from SDK versino 2.2.5 on CCSv7.4.0.

    Adan Pantoja said:
    From the console output, it appears that the program cannot find "xdc/std.h" and it is also having issues with the "app_ble.cfg" file.

    The include file is indeed the root of the issues when trying to build the <app_ble.cfg>. This is usually caused by a bad path to an include directory or a missing dependency installed as Markel suggested.

    When you expand the includes project directory, do you see any missing paths (greyed out)? This is waht you should see:

    If there is a greyed out path, check the Project Include options and the Products installed:

    You can proceed to install and restart CCS to scan the installed products.

    Additional troubleshooting details can be found in sections 6.1.3 and 9 of the CCS User's Guide

    http://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    Hope this helps,

    Rafael

  • Hi Rafael,

    Thank you for getting back to me! I have checked the include files and none are greyed out (see screenshot).

    I have also checked my products and they happen to be the same as yours (see screenshot below)

    One thing I noticed is that when I downloaded BLE stack it installed tirtos_cc13xx_cc26xx_2_21_01_08 and xdctools_3_32_00_06_core in the TI directory. But when I loaded CCS it prompted me to install both of the things again, could that cause any issues?

    I am extremely confused as to why this is not working. The steps that I am doing are as follows:

    1. Installed Code Composer Studio version 7.4.0.00014

    2. Installed BLE stack, which the executable installs tirtos_cc13xx_cc26xx_2_21_01_08 and xdctools_3_32_00_06_core.

    4. Open CCS which prompted me to install tirtos_cc13xx_cc26xx_2_21_01_08 and xdctools_3_32_00_06_core.

    3. Load simple_peripheral_cc2650lp_app and stack into the workspace.

    4. Build simple_peripheral_cc2650lp_stack. (No issue when building this)

    5. Build simple_peripheral_cc2650lp_app.

    Step 5 is where I am stuck because of the issues mentioned above. 

    Is there anything else I can try? I am desperate at this point to get this project working.

    Thank you,

    Adan

  • Hi Adan,

    Make sure to import the simple peripheral with copy to workspace option. Also, rebuild all both stack and app.

    -kel

  • Adan,

    Adan Pantoja said:
    But when I loaded CCS it prompted me to install both of the things again, could that cause any issues?

    That is normal. When you open CCS 7.4, it automatically runs something called Product Discovery. This is necessary to use the dependencies of the BLE Stack, such as TI-RTOS and XDC. Additional information in section 6.1.3.10 of the CCS User's Guide I linked above.

    When the Product Discovery process finishes, you usually need to restart CCS.

    Since the file std.h is being reported as missing, can you be sure it exists in the Include tree by expanding the entry for the xdctools as shown below?

    I send attached the entire build output of my project here - perhaps you can spot something out of the ordinary. 

    simple_peripheral_cc2650lp_app_build_output.txt

    I will try to see if there are any other reports that can provide additional ideas to find the root cause of this issue and report back in case I find anything relevant. 

    Hope this helps,

    Rafael

  • Try to use CCS 10.2 to build and test simple_peripheral example in BEL Stack 2.2.5. Remember to install SDK in default c:/ti.

  • All,

    Rafael, unfortunately the image your provided did not show up on my end, but I assume you're talking about the checking under the include tree. The file "std.h" is located under the xdctools directory.

    I looked through your output text file and it seems that my program calls the same include files and flags as yours, but after the "C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/app_ble.cfg" is where it is different. 

    Your compiler goes on and calls:

    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

    Whereas mine calls:

    configuring app_ble.xem3 from package/cfg/app_ble_pem3.cfg ...
    generating custom ROM library makefile ...

    Here is the build output



    **** Build of configuration FlashROM for project simple_peripheral_cc2650lp_app ****

    "C:\\ti\\ccs1020\\ccs\\utils\\bin\\gmake" -k -j 4 all -O

    Building file: "C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/app_ble.cfg"
    Invoking: XDCtools
    "C:/ti/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/packages;C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/tidrivers_cc13xx_cc26xx_2_21_01_01/packages;C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages;C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/uia_2_01_00_01/packages;C:/ti/ccs1020/ccs/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2640F128 -r release -c "C:/ti/ccs1020/ccs/tools/compiler/ti-cgt-arm_16.9.4.LTS" --compileOptions "-mv7M3 --code_state=16 --abi=eabi -me -O4 --opt_for_speed=0 --include_path=\"C:/ti/ccs1020/ccs/tools/compiler/ti-cgt-arm_16.9.4.LTS/include\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/examples/simple_peripheral/cc26xx/app\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/icall/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/profiles/roles/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/profiles/roles\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/profiles/dev_info\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/profiles/simple_profile/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/profiles/simple_profile\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/heapmgr\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/controller/cc26xx/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/hal/src/target/_common\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/target\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/hal/src/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/hal/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/osal/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/services/src/sdata\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/services/src/saddr\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/components/icall/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/inc\" --include_path=\"C:/ti/simplelink/ble_sdk_2_02_05_02/src/rom\" --include_path=\"C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/cc26xxware_2_24_03_17272\" -g --c99 --gcc --define=BOARD_DISPLAY_EXCLUDE_LCD --define=BOARD_DISPLAY_EXCLUDE_UART --define=CC2650_LAUNCHXL --define=CC26XX --define=Display_DISABLE_ALL --define=GAPROLE_TASK_STACK_SIZE=540 --define=HEAPMGR_SIZE=0 --define=ICALL_MAX_NUM_ENTITIES=6 --define=ICALL_MAX_NUM_TASKS=3 --define=POWER_MEASURE --define=POWER_SAVING --define=USE_ICALL --define=xdc_runtime_Assert_DISABLE_ALL --define=xdc_runtime_Log_DISABLE_ALL --diag_warning=225 --diag_suppress=48 --diag_wrap=off --display_error_number --gen_func_subsections=on " "C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/app_ble.cfg"
    configuring app_ble.xem3 from package/cfg/app_ble_pem3.cfg ...
    generating custom ROM library makefile ...
    Starting build of library sources ...
    making C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/src/sysbios/rom_sysbios.aem3 ...
    make[1]: Entering directory 'C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/src/sysbios'
    clem3 C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c ...

    >> Compilation failure
    make[1]: Leaving directory 'C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/src/sysbios'
    Build of libraries failed.
    TOOLS/subdir_rules.mk:12: recipe for target 'build-1641678497-inproc' failed
    "C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c", line 36: fatal error: cannot open source file "xdc/std.h"
    1 catastrophic error detected in the compilation of "C:/ti/tirtos_cc13xx_cc26xx_2_21_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c".
    Compilation terminated.
    make[1]: *** [makefile:59: rom_sysbios.obj] Error 1
    gmake: *** [C:/ti/simplelink/ble_sdk_2_02_05_02/examples/cc2650lp/simple_peripheral/ccs/config/src/sysbios/rom_sysbios.aem3] Error 2
    error: xdc.cfg.SourceDir: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/cfg/SourceDir.xs", line 209: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:

    js: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!
    xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Error 1
    xdctools_3_32_00_06_core\gmake.exe: *** Deleting file `package/cfg/app_ble_pem3.xdl'
    xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Deleting file `package/cfg/app_ble_pem3.h'
    xdctools_3_32_00_06_core\gmake.exe: *** [package/cfg/app_ble_pem3.xdl] Deleting file `package/cfg/app_ble_pem3.c'
    js: "C:/ti/xdctools_3_32_00_06_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake[1]: *** [build-1641678497-inproc] Error 1
    gmake: *** [build-1641678497] Error 2
    TOOLS/subdir_rules.mk:9: recipe for target 'build-1641678497' failed
    gmake: Target 'all' not remade because of errors.


    I have also tried to build the program with CCS 10.2, but I still get the same error. I have also loaded the projects into my workspace with the "Copy into workspace" selected.

    One thing I did notice was that "C:\ti\xdctools_3_32_00_06_core\packages" was not within the Include Options window. I manually entered the path into the include window, but I still get the error.  

    - Adan

  • Hi Adan,

    I have a unusual suggestion. Try doing the same at another PC. I had this experience before where my CCS projects suddenly got build errors, later found out that my antivirus was removing some files including the CCS shortcut. I had to re-install everything and set c:\ti as exception from antivirus.

    -kel

  • Adan,

    The difference between my build and yours is that your log shows an error while trying to build a TI-RTOS file BIOS.c.

    I really don't know why this is failing, but there is a very long and convoluted thread that reports the error at the same point as you (while building the file BIOS.c) but it did not reach any conclusion as we were not able to reproduce this at TI. Many suggestions to track down the issue are shown there, but I really couldn't find an exact root cause for this locally as well.

    I also tested this project build on CCSv10.2 but could not find any issues with the build itself (I was using CCSv7 before).

    Please check the other thread and see if any suggestions there help you. In the meantime, I will try to track any additional discussions and report back in case I find anything relevant.

    Hope this helps,

    Rafael

  • Adan,

    I am still very intrigued by this issue, but in the meantime can you check one thing? In your filesystem do you have the directory below?

    C:\ti\ble_sdk_2_02_05_02\examples\cc2650lp\simple_peripheral\ccs\config\src\sysbios

    This directory should contain a few libraries that correspond to the SYSBIOS components used by the simple_peripheral project

    If this project does not exist or is empty, the SYSBIOS build step will be triggered.

    To help you move forward with your development, please check attached a copy of the files built in my system here. Simply unzip this to the directory above and see if your project finishes building fine.

    Hope this helps,

    Rafael

    sysbios.zip

  • Rafael,

    I have had an unusual experience with CCS. My project seems to now build and is working properly. I have no clue as to what caused it to fix itself.

    The steps I took before it magically worked are as follows:

    1. Uninstalled all files: BLE stack, TIRTOS, XDC, and CCS (Cleared my C:/ti folder).

    2. Installed CCS 10.2

    3. Installed BLE stack (which installs TIRTOS, and xdc)

    4. Imported the simple_peripheral_cc2650lp_app/stack and copied into workspace.

    5. Download tirtos and xdc into CCS.

    6. Select the correct version of tirtos and xdc in project properties under products.

    7. Built stack and then the app.

    Step 7 is where I still got the same issue as mentioned above.

    I then decided to install ccs 7.4, so ..

    8. Install CCS 7.4

    9. Imported the simple_peripheral_cc2650lp_app/stack and copied into workspace.

    10. Download tirtos and xdc into CCS.

    11. Select the correct version of tirtos and xdc in project properties under products.

    12. Built stack and then the app.

    And here is where it somehow decided to build properly.

    The thing that is most frustrating is that I have been doing the steps mentioned above multiple times and the project never compiled, but then it finally compiled. So .. to sum up my post: I do not know what I did to resolve this issue, but I am no longer having it with CCS7.4. When I build the project using CCS 10.2, I still get the same issue.

    It would be ideal to figure out exactly what is going on for other people who may be experiencing this, but for now I am moving forward with my development.

    Thank you all for your assistance! It was greatly appreciated.

    -Adan

  • Adan,

    I am really sorry about these issues. I can't pinpoint a reason as to why 10.2 is failing for you, since it works here for me.

    Due to the role of supporting multiple SDK versions, I also have installed CCSv7.4 (for CC2650 and CCSv9.1 (for CC2640R2F) SDKs and none of these versions failed for me.

    At any rate, I am glad that CCSv7.4 is working for you - at least you are not halted in your development.

    Without being able to reproduce anything here, I can only promise to keep an eye on additional reports in the hopes that any additional detail may surface to bring additional ideas as to what may be happening.

    I apologize for the inconvenience,

    Rafael