• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 51 subscribers
  • Views 1762 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2650STK: Latest Firmware Source Code Problem

Fazlay Rabbi
Prodigy 190 points
Other Parts Discussed in Thread: CC2650, CC2640, BLE-STACK

Hello Everyone,

I am trying to modify the firmware source code of CC2650 sensortag. When I flash the original firmware (without any modification) to my CC2650 using DEV-PACK and I got only 11 services out of 13 services on the TI's official android app (latest version, update on 2nd July) and I also got the following error on android app:

GATT error code: GATT invalide offiset 

I am not getting motion sensor data which I need badly. Is there anyone also facing same problem? I appreciate any help on this issue.

I got the firmware source code using BLE_STACK-2 VERSION 2.0.0 ( http://www.ti.com/tool/ble-stack ) . Is it the correct firmware source code?

I appreciate any help. 

Thanks,

Fazlay

  • 0
    TI__Mastermind 33460 points

    Hi Fazlay,

    I am using the Sensor Tag project found in our BLE Stack version 2.0.0, and code composer studio. The default install location of this project is C:\ti\simplelink\ble_cc26xx_2_00_00_42893\Projects\ble\SensorTag\CC26xx. I am connecting using the sensor tag iphone app v4.2.

    Using the service explorer, I find 9 different services.

    I do not find any GATT error codes. Are you able to use the project described above?

  • 0 in reply to Sean2
    Prodigy 190 points

    Hi Sean,

    Yes I am using the source code from C:\ti\simplelink\ble_cc26xx_2_00_00_42893\Projects\ble\SensorTag\CC26xx folder. Even If I have flashed the CC2640_SmartRF_SensorTag.hex  file located in C:\ti\simplelink\ble_cc26xx_2_00_00_42893\Accessories\HexFiles onto my CC2650. But this pre-compiled firmware is also not showing motion data in TI's official andorid app as well as iOS app.

    Thanks,

    Fazlay 

  • 0 in reply to Fazlay Rabbi
    TI__Mastermind 33460 points

    Fazlay,

    This is an issue that is known in the SensorTag firmware shipped with the SDK. You can upgrade the firmware OTA or wait until our BLE stack V2.1 which is about to be released on the web. I have tested using V2.1 and the motion service is fixed. 

  • 0 in reply to Sean2
    TI__Mastermind 33460 points
    FYI BLE Stack v2.1 is available on our website.
  • 0 in reply to Sean2
    Prodigy 190 points
    Hi Sean,

    I was testing BLE STACK v2.1. When I built the firmware source code, the sensortag was advertising. After connecting the sensortag to android app, the app was not showing any sensor data even it was not showing the device information. Then i disconnected the sensortag and now it is not advertising anymore. Seems like It is bricked. I am wondering, am I missing something?

    Thanks,
    Fazlay
  • 0 in reply to Fazlay Rabbi
    TI__Mastermind 33460 points

    Fazlay,

    I believe there is a configuration issue somewhere. I just pulled the most recent version of the stack from the web, imported the sensor tag stack and sensor tag app projects into CCS (using Version: 6.1.0.00104) compiled and loaded the stack project and then compiled and loaded the app project.

    After the image was successfully loaded I connected using the Sensortag app on iOS and it worked as expected.
     
    Try to flash using Flash Programmer 2 and the prebuilt .hex file at <$BLE_INSTALL>\Accessories\HexFiles. Is your .ccxml file configured for using the XDS110? Any information related to your setup could help me replicate this issue.

  • 0 in reply to Sean2
    Prodigy 190 points

    Hi Sean,

    I have followed the following steps to compile and build the source code:

    1. I installed the BLE-STACK v2.1 and imported the firmware sourc code from location  C:\ti\simplelink\ble_cc26xx_2_01_00_44423\Projects\ble\SensorTag\CC26xx into CCS V6.1. There are two project named SensorTag and SensorTagStack.

    2. Then I right clicked on the SensorTag project and selected Properties. Then I changed the Connection to Texas Instruments XDS110 USB Debug Probe in General tab.

    3. Then I opened the windows command prompt as Administrator and Change the Directory (CD) to C:\ti\ccsv6\ccs_base\common\uscif\xds110 and run the following 2 commands:

    xdsdfu -m

    xdsdfu -f firmware.bin -r

    4. Then I select SensorTag project on CCS and press F11 (Debug). Then I stepped over some functions call in the main.c file until it reached  BIOS_start();Then I stopped the debugging.

    5. Then I connected the sensortag with android phone. It was not showing any sensor data. Then I disconnected the sensortag from devPack debugger and inserted a new battery. But It was not advertising or blinking at all. And still it is not advertising or blinking.

    Am I missing something? Should I build the SensorTagStack first then SensorTag project? I tired it but SensorTagStack has no main program.

  • 0 in reply to Fazlay Rabbi
    TI__Mastermind 33460 points

    No problem, happy to help.

    Yes, the build order is your problem. You should first build and load in the sensortagstack project. You will see a message in the console saying that there is no main found. It is safe to ignore this, hit the red stop button, and then change the active project to the SensorTag project (aka the App). Compile and load that project and press the green play button. At this point the chip should be initialized and you can connect with your phone.

    Our Bluetooth solutions use two projects. One that contains code and libraries related to our Bluetooth Stack which handles implementing the BLE protocol developed by the Bluetooth Special Interest Group (SIG). The second is the application layer, this is where the end application of the device is coded, ie SensorTag or your custom app. You will be heavily modifying this code.

  • 0 in reply to Sean2
    TI__Mastermind 33460 points
    It should also be noted that step 3 isn't needed as it is updating the firmware on your debugger, not the CC26xx device.