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/LAUNCHXL-CC2650: Can I run blink LED example from the TI-RTOS workshop on CC2650 Launchpad?

Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2650, CC3200, SYSBIOS

Tool/software: Code Composer Studio

Hi there,

I am trying to run some exampe projects on the CC2650 Launchpad. I have been following the TI_RTOS tutorials/workshop : 

that deals with the following architectures - C28X, C6000, MSP430 nad TM4C. Can I load, say, a blink_TM4C.out file onto the CC2650 Launchpad??

Best,

AM

  • Not easily. There is a lot of hardware configuration that goes on behind the curtain.
  • Azim Malik Abdul Aziz said:
    Can I load, say, a blink_TM4C.out file onto the CC2650 Launchpad??

    The workshop page does say the following, so I would expect it to work, however I personally haven't tried it myself.

    For CC3200, CC26xx/CC13xx devices, users can run their labs on the Cortex M4 platform (Tiva-C) - and again, everything covered in the workshop is 100% applicable to these devices because almost all material/labs focus on TI-RTOS, not architecture.

    I understand that you're probably looking to follow along with the tutorial, but there are also several other examples included with TI-RTOS for CC13xx/CC26xx that you could try to run through.

  • I did try building the "hello" from the ti_rtos for cc13xx/cc26xx,; I am unable to build it (the hammer icon is faded out). Does it have to do with the example being in a different workspace or not in the current workspace?

  • How did you import the "hello" example? I imported it into CCSv8 using Resource Explorer Classic and it built just fine.

  • Hi Aarti,
    I just did the same as well. I am getting the following errors.


    **** Build of configuration Debug for project hello_CC2650_LAUNCHXL_TI_CC2650F128 ****

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

    Building file: "../hello.cfg"
    Invoking: XDCtools
    "C:/ti/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/packages;C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/tidrivers_cc13xx_cc26xx_2_20_01_10/packages;C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/bios_6_46_01_38/packages;C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/uia_2_00_06_52/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2650F128 -r release -c "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS" --compileOptions "-mv7M3 --code_state=16 --float_support=vfplib -me --include_path=\"C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128\" --include_path=\"C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128\" --include_path=\"C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/cc26xxware_2_24_02_17393\" --include_path=\"C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include\" --define=ccs -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../hello.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring hello.xem3 from package/cfg/hello_pem3.cfg ...
    generating custom ROM library makefile ...
    Starting build of library sources ...
    making C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128/src/sysbios/rom_sysbios.aem3 ...
    gmake[1]: Entering directory `C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128/src/sysbios'
    clem3 C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/bios_6_46_01_38/packages/ti/sysbios/BIOS.c ...
    gmake[1]: Leaving directory `C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128/src/sysbios'
    Build of libraries failed.
    subdir_rules.mk:33: recipe for target 'build-705771103-inproc' failed
    0 [main] sh 12920 sync_with_child: child 7316(0x1C8) died before initialization with status code 0xC0000142
    38 [main] sh 12920 sync_with_child: *** child state waiting for longjmp
    C:/Users/azim/AppData/Local/Temp/make7652-1.sh: fork: Resource temporarily unavailable
    gmake[1]: *** [rom_sysbios.obj] Error 128
    gmake: *** [C:/ti/workspace_peeva/hello_CC2650_LAUNCHXL_TI_CC2650F128/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/hello_pem3.xdl] Error 1
    gmake.exe: *** Deleting file `package/cfg/hello_pem3.xdl'
    gmake.exe: *** [package/cfg/hello_pem3.xdl] Deleting file `package/cfg/hello_pem3.h'
    gmake.exe: *** [package/cfg/hello_pem3.xdl] Deleting file `package/cfg/hello_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-705771103-inproc] Error 1
    gmake: *** No rule to make target 'build-705771103', needed by 'configPkg/compiler.opt'.
    gmake: *** No rule to make target 'build-705771103', needed by 'configPkg/compiler.opt'.
    gmake: *** No rule to make target 'build-705771103', needed by 'configPkg/compiler.opt'.
    gmake: Target 'all' not remade because of errors.

    **** Build Finished ****



    I have WinAVR and Atmel Studio installed on my PC. Do you think they could be causing any conflicts with the RTOS?

    Best,
    Azim
  • Azim Malik Abdul Aziz said:
    I have WinAVR and Atmel Studio installed on my PC. Do you think they could be causing any conflicts with the RTOS?

    Yes that could cause a conflict. Please see the first diagnostic at this link that also has suggested workarounds.