• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 1422 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.

RTOS/LAUNCHXL-CC2650: Simple Peripheral Example Not Executing - Aborting After BIOS_start()

Bharathi Saravanabhavan
Intellectual 525 points

Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: BLE-STACK, CC2650

Tool/software: TI-RTOS

I am trying to run the simple peripheral example from the BLE-STACK 2.2.2 on my CC2650 LaunchPad. However, once I debug up to BIOS_start(), the debugger jumps to exit.c and aborts (due to abnormal program termination). What is going on here? Considering I haven't touched the example, I feel like this shouldn't be happening.

  • 0
    TI__Mastermind 41650 points
    Hi Bharathi,

    Did you compile and flash the stack project first before flashing the application project?
  • 0 in reply to Evan W
    Intellectual 525 points
    No I haven't. I was under the assumption that compiling and flashing the app would take care of compiling/flashing the stack. Let me try what you mentioned and see where that goes.
  • 0 in reply to Evan W
    Intellectual 525 points
    I tried compiling the stack as you suggested. I think this may have helped since I'm not running into exit.c. However once the bios is started, I don't see that the BLE is working (no results on PuTTy or on SensorTag app on phone). I tried to debug the issue by placing a breakpoint within the SimpleBLEPeripheral task fxn, but it looks like that is not being executed.
  • 0 in reply to Bharathi Saravanabhavan
    TI__Mastermind 41650 points
    Bharathi,

    Unfortunately for the CC2650, the projects are not linked together automatically like they are on the newer CC2640R2 and CC26x2. Therefore, be absolutely sure that you've followed these steps:

    1) Import the app and stack project
    2) Compile and flash the stack project. Make sure you flash it to the chip.
    3) Compile and flash the app project.

    After following these steps they should be fine. the way you've described your second post sounds like you've not followed these steps. I can confirm that they work on my end.
  • 0 in reply to Evan W
    Intellectual 525 points
    Got it. I see the SimpleBLEPeripheral on the SensorTag app on my iPhone. However, PuTTy is not showing any logs. And also, the SimpleBLEPeripheral device on SensorTag has 4 services: Device Information, Project Zero LED, Project Zero Button, and Project Zero Data. This seems strange considering SimpleBLEPeripheral doesn't have any of these services - only Project Zero does.

    What exactly should I be able to do with SimpleBLEPeripheral? How many services should I have, and what characteristics do I have access to?
  • 0 in reply to Bharathi Saravanabhavan
    TI__Mastermind 41650 points
    Bharathi,

    Project Zero and simple_peripheral are meant to be different projects with differing functionality. Project Zero shows some capabilities of the chip while simple_peripheral serves as a project to use as the foundation for your actual application.

    I do not believe that simple peripheral prints out to PuTTy like the project zero.
  • 0 in reply to Evan W
    Intellectual 525 points
    Okay great. But why am I seeing Prjecect Zero BLE services when looking at the services on my phone? I should be seeing a different set of services related to simple_peripheral right?
  • 0 in reply to Bharathi Saravanabhavan
    TI__Mastermind 41650 points
    Smartphones tend to cache the GATT table and other device information like name and what not upon the first connection and service discovery and bond.

    Go to your smartphone bluetooth settings and forget the device and reconnect and it will retrigger service and name discovery and you will see the simple peripheral services.

    If the settings don't work, then restart your phone.
  • 0 in reply to Evan W
    Intellectual 525 points
    Perfect! That resolved it. Thanks so much!