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/TIDC-CC2650STK-SENSORTAG: Loading hex files gives red light

Part Number: TIDC-CC2650STK-SENSORTAG
Other Parts Discussed in Thread: CC2650, CC2650STK, CC2640, BLE-STACK

Tool/software: Code Composer Studio

I have been struggling with the device for the last few days and wanted to ask a question regarding it.

I need to increase the data transmission rate to preferably around 100Hz (if possible then faster) in order to get the accelerometer/movement data. I have tried to load an example onto the device but now it isn't detectable anymore and the red light is on. My steps were as follows:

- Downloaded BLE SDK, code composer studio, Flash programmer 2. Installed/saved all of them to their default path with admin privileges.

- Opened CCS and got the recommended compiler (ARM Compiler Tools 5.2.6) 

- Connected CC2650 with debugger and computer. 

- Imported the Sampletag example into CCS. Built first the stack then the app project.

- tried to first load the stack then the app onto the device by clicking debug. Since that didn't work I opened up flash programmer 2 and put in both hex files. Then clicked on the blue/white arrow to start the process. Now my device has the red light on and I can't even connect to it. 

I did install the firmware Flash programmer 2 wanted me to install, since it got angry at me and told me it couldn't identify the device.

Could anyone help me a bit or give me some advice? Just getting to this point has been a pain. Also, I would need some progress soon...

Furthermore, how fast can I get the transmission rate just for the movement data, specifically acceleration data. I don't really need all the other sensors if disabling would make the recording of data faster. 

  • You also have to download BIM into your CC2650STK.
  • Hello,

    In addition, please see the SensorTag User's Guide on the TI BLE Wiki which has the firmware build instructions, including programming the BIM as suggested by YiKai.

    Best wishes
  • Thank you both for the replies. I think this should solve the problem, I will test it now.
    However, I want to voice my frustration with this device and especially its documentation (hopefully it will be heard). I have been working with the SDK for several days now and the documentation has not been helpful at all. Small crucial details are scattered all over the place and you have to read 10 manuals to see what is going on. I followed the SDK developers guide and it never mentioned that I needed the BIM. I remember somewhere reading that the C2640 needed the BIM for OAD and that was also a user guide to the CC2650 in which it stated that the CC2650 didn't need the BIM. It is hard to know which documentation is relevant and it is even less useful that the documentation is not up to date. If TI wants to push their products they should make it easier for developers to follow what exactly has to be done to make everything woks.
    The fact that I have to read the section "Building the SensorTag Firmware" to understand how to load a project onto the device is in my eyes very poor placement of important information.

  • Actually, you can read SensorTag user guide at processors.wiki.ti.com/.../CC2650_SensorTag_User's_Guide which gives you thorough guide.
  • I have simply given constructive critizism to improve the documentation. While that specific guide gives the correct thorough information the other also relevant documentations do not. Moreover, the BIM project is listed under CC2640 and not under CC2650 in the SDK, while it can be used for both, which just adds more confusion, albeit not too much. Updating the documentation to make it more coherent would help a lot.

    If you don't mind. Could you tell me the highest rate at which I can transfer acceleration data? I asked in my original post but didn't get an answer. Furthermore, I can not really find concrete up-to-date information elsewhere.
  • Glad you have it programmed. On the CC2640/CC2650, we do have the following in the BLE-Stack v2.2.1 SW Developer's Guide (SWRU393):

    NOTE: This kit supports development of Bluetooth low energy applications on the following
    SimpleLink wireless MCUs: CC2640 and CC2650. The multi-standard CC2650 wireless MCU
    supports Bluetooth low energy as well as other wireless protocols, such as ZigBee® and
    6LoWPAN. The CC2640 supports Bluetooth low energy only. All code generated from the
    BLE-Stack v2.x SDK is binary compatible and exchangeable with both the CC2650 and
    CC2640 wireless MCUs. Throughout this document, CC2640 and CC2650 may be used
    interchangeably

    We are always open to feedback in order to make it easier to use.

    Regarding movement sensor reporting, as the SensorTag guide states under the Movement Service, the configured reporting range (Period): Resolution 10 ms. Range 100 ms (0x0A) to 2.55 sec (0xFF). Default 1 second (0x64).

    It may be possible to modify the sample source code to enable faster reporting periods although we do not provide examples of this.

    Best wishes