• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 399 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/CC2640R2F: Simple_Central.c BLE Functions

Joshua Hess
Intellectual 490 points
Part Number: CC2640R2F

Tool/software: TI-RTOS

Hello,

I am currently developing a custom application around the simple_central example. I have a custom PCB with the SABLE-X-R2 module on it with several buttons, sensors, and a display. I am trying to get the simple central application merged with another application that I have for reading sensors, talking over SPI with the display, and other things.

I am having trouble making sense of the flow of the functions in the simple_central.c file. I have two buttons on my board that I would like to use to navigate the menu for the example, but I don't want to have them as interrupts like defined in the board_key.c file. I tried calling just the SimpleCentral_startGapDiscovery(); and then the SimpleCentral_connectToFirstDevice(); in my own application thread, but it goes into an aport spin loop.

What is the proper way to go about merging the functionality from the simple_central example into a custom application? I have been unable to find documentation that goes over the specifics of the simple central example and the structure of the program. 

Thanks,

Josh

  • 0
    TI__Genius 11535 points
    Hi Josh,

    Are you using BLE4.2 or BLE5? The examples are slightly different depending on which version of BLE you are using. I would recommend focusing more on merging your custom application into the simple_central application and then removing the parts you don't want instead of the other way around.
  • 0 in reply to Jessica H.
    TI__Genius 11535 points
    Hi Josh,

    I'm going to close this post due to inactivity. To reopen this thread, just post a follow up question. Otherwise, after 30-days of inactivity from this post, this thread will lock. If you reject that this post has been potentially resolved, please indicate why you are rejecting it so we may better assist you.