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.

OTA synchronization?

Other Parts Discussed in Thread: CC2540

What options (other than hard wired ;) ) do I have to synchronize two (or more ) remote working cc2540s time wise? I mean I want curtain process/event  to start at cc2540 #1 and want other process to start at cc2540 #2 at the same time or at predefined time offset; and from time to time want to perform again some sort of a marker to  resync  all the network/cc2540s that  participate in this algorithm?

Thanks

  • The BLE stack currently does not have any capabilities to perform synchronization like this.

  •  Hi Willis,

    Could I use some events , callbacks, "hooks" or whatever is available  from the connection phase process: CONNECT_REQ PDU sent from master, and accepted from the slave(see the illustration in BLUETOOTH Spec v4.0 page 2235 from the pdf.file or page 71 from Vol.6):

    So from this point and further they both have synchronization - they both know next  anchor points etc. So if get some notification for any of these steps from both master and slave sides I could achieve what I need .

    I see from BT specs this is part of LL (link layer specs), but in TI source code cant find any event that is associate with, so the closest event that I found was GAP_LINK_ESTABLISHED_EVENT. Is there somewhere detail explanation when this event exactly is generated, is it generated in both sides (master and slave)  etc. or something similar where I could get time markers?

    Thanks

  • Our API does not have any way to get the exact time until the next event.

    Information on the GAP_LINK_ESTABLISHED_EVENT and other events can be found in the HTML-based BLE Stack API Guide, which is installed in the "C:\Texas Instruments\BLE-CC2540\Documents" directory.

  • "#define  GAP_LINK_ESTABLISHED_EVENT   0x05
      Sent when the Establish Link Request is complete. This event is sent as an OSAL message defined as gapEstLinkReqEvent_t. "

    Thats all I found before from the same place you said > BLE GAP:GAP Message IDs:..

    Is this all or should be more that I didn't found yet?

    Thanks