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-CC2650: In 2021, what hardware/software combination does TI test for bluetooth development?

Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2650, CC2640, SYSCONFIG, CC2650STK, CC1352P, CC1352P7, CC2652R7, CC2652RB, CC2652RSIP, CC2652R

I am trying to develop with a TI CC2650 bluetooth part.  There are a ton of links to various versions and forum posts about different combinations of components.  Most questions regard trying to get the toolchain to work.

Right now, digikey/mouser and even jlcpcb offer parts for the CC2650 launchpad eval kit.  Despite it being available, no easy method exists for writing code for this platform.  I'm currently using CCS 7.4 and some docs which describe a project zero as a starting point.  However, after building the simple arm examples to toggle the eval board LEDs this mysterious example can not be found.  

So as of June 2021, what is the tested and approved method for software development of this eval board for the purposes of ble?

  • Hi,

    The tools versions to use are stated in the release note of the SDK you will chose.

    You will find the code examples inside the SDKs.

    Best regards,

  • That is not accurate.  There are many documents which say many things, but that does not mean its a true.

    I'm looking for an actual tested combination of software/hardware for a particular host os.

    So if you search for launchxl-cc2650 you will find many questions over the years on this forum.  I'm looking for the tested/supported method for the current year.

  • Hi,

    Based on the release notes of the BLE stack found here: http://software-dl.ti.com/simplelink/esd/ble_stack_2_x/2.02.06.07/exports/release_notes_BLE_Stack_2_2_6.html

    BLEStack 2.2.6

    CCS 7.4.0

    IAR Embedded Workbench for ARM: 7.80.4

    TIRTOS: 2.21.01.08

    Best regards,

  • I installed cc7.4.0 and ble 2.26.  The project zero is not available for the 2650.  I mentioned that earlier.

    I'm currently using CCS 7.4 and some docs which describe a project zero as a starting point.  However, after building the simple arm examples to toggle the eval board LEDs this mysterious example can not be found. 
  • Hi,

    We do not offer project_zero example for CC2650 devices.

    We usually recommend to start developing using simple_peripheral example.

    Best regards,

  • Simple_peripheral is not listed in the resource explorer for the cc2650 in the ccs 7.4 installation.

  • Hi,

    The BLE examples are stored in the BLE Stack, not inside the TIRTOS.

    Please download and install the BLE Stack for CC2640/CC2650 devices (https://www.ti.com/tool/BLE-STACK)

    Then, you can import one of the projects contained in the BLE stack into CCS.

    Regards,

  • Sigh.  I have installed that windows only product as you can see here.

    All my laptops are either linux or osx.  I'm using my sons gaming laptop for this endeavor.

    My understanding is that the first link on the downloads page, the windows installer for simplelink ble 2.x is the install which shows up in the add/remove programs applet.  The second link is the generic 7.4 ccs ide.  It is also shown as installed in the add/remove programs control panel applet.

  • Hi,

    I guess you have found what you need through your second thread.

    When "installed", the SDK / BLE Stack is available by default as a folder in C:\ti or C:\ti\simplelink.

    Then you can import the examples using CCS function "import CCS project".

    Best regards,

  • /facepalm

    Did you not read the directory listing that i posted?  Lets do it again.  Here is the contents of my c:/ti directory.as text instead of a screenshot for ease of reading.

    ```

    Directory of C:\ti

    06/23/2021 12:28 PM <DIR> .
    06/23/2021 12:28 PM <DIR> ..
    06/23/2021 12:28 PM <DIR> .tirex-temp
    06/23/2021 12:01 PM <DIR> ccs1031
    06/20/2021 02:27 PM <DIR> ccsv7
    06/20/2021 02:27 PM 1,773 Code Composer Studio 7.4.0.lnk
    06/22/2021 12:03 PM <DIR> gcc-arm-none-eabi_7_2_1
    06/23/2021 12:23 PM <DIR> gcc_arm_none_eabi_9_2_1
    06/22/2021 12:22 PM <DIR> sail_1_20_00_02
    06/22/2021 02:17 PM <DIR> simplelink
    06/22/2021 02:20 PM <DIR> simplelink_academy_01_11_00_0000
    06/22/2021 12:22 PM <DIR> simplelink_academy_bleplugin_3_10_02_00
    06/23/2021 12:21 PM <DIR> simplelink_academy_cc13x2_26x2sdk_5_10_00_00
    06/22/2021 12:04 PM <DIR> simplelink_academy_cc2640r2sdk_5_10_02_00
    06/23/2021 12:27 PM <DIR> simplelink_cc13x2_26x2_sdk_5_10_00_48
    06/22/2021 11:57 AM <DIR> simplelink_cc2640r2_sdk_5_10_00_02
    06/22/2021 12:21 PM <DIR> simplelink_msp432e4_sdk_3_20_00_10
    06/22/2021 12:17 PM <DIR> simplelink_msp432p4_sdk_3_20_00_06
    06/22/2021 12:12 PM <DIR> simplelink_sdk_ble_plugin_3_20_00_24
    06/23/2021 12:15 PM <DIR> sysconfig_1_8_0
    06/22/2021 12:02 PM <DIR> ti-cgt-arm_18.12.5.LTS
    06/23/2021 12:23 PM <DIR> ti-cgt-arm_20.2.4.LTS
    06/23/2021 12:06 PM <DIR> tirex-product-tree
    06/20/2021 02:33 PM <DIR> tirtos_cc13xx_cc26xx_2_21_00_06
    06/20/2021 01:38 PM <DIR> tirtos_cc13xx_cc26xx_2_21_01_08
    06/23/2021 12:21 PM <DIR> ti_cgt_tiarmclang_1.2.1.STS
    06/20/2021 02:35 PM <DIR> xdctools_3_32_00_06_core
    06/20/2021 02:11 PM <DIR> xdctools_3_32_02_25_core
    06/20/2021 02:14 PM <DIR> xdctools_3_50_04_43_core
    06/22/2021 12:01 PM <DIR> xdctools_3_51_03_28_core
    06/20/2021 02:20 PM <DIR> zips
    1 File(s) 1,773 bytes
    30 Dir(s) 34,057,134,080 bytes free

    ```

    If I do a search, I get numerous hits, but as I have learned the suffix matters and is not a package variant only. ie 2640r something is not the same as 2640.  Consquently I'm not certain which to use.  Also none of these show up in the resource explorer for import into the project workspace.  Isn't that the prescribed method to load the example into the workspace?

    ```

    Volume in drive C is OS
    Volume Serial Number is 1241-D0D0

    Directory of C:\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650em

    06/20/2021 01:24 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650lp

    06/20/2021 01:24 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650stk

    06/20/2021 01:24 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\ble_sdk_2_02_06_07\src\examples

    06/20/2021 01:24 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650em

    06/22/2021 02:01 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650lp

    06/22/2021 02:01 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650stk

    06/22/2021 02:01 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory\C\ti\simplelink\ble_sdk_2_02_06_07\src\examples

    06/22/2021 02:01 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory1\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650em

    06/22/2021 02:16 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory1\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650lp

    06/22/2021 02:16 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory1\C\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650stk

    06/22/2021 02:16 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink\rollbackBackupDirectory1\C\ti\simplelink\ble_sdk_2_02_06_07\src\examples

    06/22/2021 02:16 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC1352P1_LAUNCHXL\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC1352P_2_LAUNCHXL\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC1352P_4_LAUNCHXL\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC1352R1_LAUNCHXL\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\LP_CC1352P7_1\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\LP_CC1352P7_4\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\LP_CC2652R7\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\LP_CC2652RB\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\LP_CC2652RSIP\ble5stack

    06/23/2021 12:28 PM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc2640r2_sdk_5_10_00_02\examples\rtos\CC2640R2_LAUNCHXL\ble5stack

    06/22/2021 11:57 AM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Directory of C:\ti\simplelink_cc2640r2_sdk_5_10_00_02\examples\rtos\CC2640R2_LAUNCHXL\blestack

    06/22/2021 11:57 AM <DIR> simple_peripheral
    0 File(s) 0 bytes

    Total Files Listed:
    0 File(s) 0 bytes
    24 Dir(s) 34,043,801,600 bytes free

    ````

  • Proceeding on without a documented procedure, I used ccs 7.4 and attempted to import into workspace using this path, 

    ```

    C:\ti\simplelink\ble_sdk_2_02_06_07\src\examples\simple_peripheral\cc26xx

    ```

    I also enabled the "automatically import referenced projects found in same search directory" and "copy projects into workspace".  As you can see in the dialog, the "Finish" button is not highlighted to continue process.

    Likewise, descending a level deeper in the browse selection, it also does not enable the finish button.  See both screenshots.

  • Hi,

    If you are using CC2650 / CC2640, use the examples in C:\ti\simplelink\ble_sdk_2_02_06_07\. Assuming you have a launchpad, the examples to use are more specifically in C:\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650lp
    Use CCS 7.4.

    If you are using CC2640r2, use the examples in C:\ti\simplelink_cc2640r2_sdk_5_10_00_02\examples\rtos\CC2640R2_LAUNCHX\blestack
    Use CCS 9.2

    If you are using CC26x2 launchpad, use the examples in C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack
    Use CCS 10.3

    I hope this is clearer

    Regards,

  • Using this directory choice

    C:\ti\simplelink\ble_sdk_2_02_06_07\examples\cc2650lp\simple_peripheral\ccs 

    for the project import works.. The two projects showed up in the dialog, the finish button was enabled and I was able to import the two projects.  I'm building them now.  Not sure why I have to specify the LP suffix, not sure why the examples appear in the src directory without the project metadata.  Whatever.  Its an older release and not supported.

    With that said, we are going to change direction for this project.  Since the tools and support for the back level 2650 is poor we intend to choose a 2652 eval board.  We discussed other vendors.  I, yes me, I proposed we stick with TI.  I'm reasoning that we have  success with TI hardware.  TI does not seem to support LoRa which is something important to us, but TI hardware and supporting ecosystem is far above the competitors.

    I also made the claim that the 2652 was simple to import the project zero ble  example.  It was a simple process to import the code, and it has some associated documentation which I think will be good for us as we move into bluetooth.  I also realize that TI software support for their hardware will most likely drop off as it has obviously done with the cc2650.  However, that problem might be mitigated if the 2652 software is more mature making it more easily maintained in the future.  If we find the software and support is subpar, we take what we learned and move to a new vendor. 

    Now to figure out which eval board for the 2652 is available and who has it in stock.

  • Hmm.  Running the code above at least enables the pause/resume option so it seems to be running.  However using the mobile phone apps does not show the 2650 device  There is a third directory in that folder named config.  I wonder if it needs to be included in the workspace somehow?  It did not show when the parent directory was chosen for the import procedure in the IDE.  The config directory was not mentioned in the project zero docs I am using for a different processor.  Neither the  app, stack or config directory has a readme or other documentation so I have to guess what its for.  Some professional level software development technique I suppose.  No need to keep a document up to date if you dont have a document. 

  • John,

    The documentation is here: CC2640/CC2650 Bluetooth low energy Software Developer’s Guide (Rev. E) . For CC2650 you need to build and download the stack project first, then build and download the app project. This has been changed for new devices. It is stated in the documentation I am linking to though. 

    Moving to CC2652R sounds like a good choice. 

    For other people who may stumble across this thread, I made a step-by-step guide on getting CC2650 running here: https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1012009/what-is-ti-tested-hardware-software-solution-for-bluetooth-le-in-2021/3741875#3741875

    /F