• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 644 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/CC2640: Android -- connection stays open at 7.5ms interval after disconnect

Andy Lamping
Intellectual 270 points
Part Number: CC2640
Other Parts Discussed in Thread: , CC2650, CC2541

Tool/software: TI-RTOS

OK not a ton of information at this point (will update). CC2640. Simple Peripheral based. Desired connection interval of 50ms on peripheral.

On Android, on rare occasions, we disconnect a peripheral...yet we notice some odd behavior. One time (using scope), it looked like the the peripheral remained connected at a 7.5ms interval (the min in peripheral.c) despite our usual disconnect protocol. Nothing showed up in the sniffer on the respective advertising channel so we have to assume it was connected. We then also turned off the Android phone, and the peripheral then no longer transmitted anything -- flat pulse on the transmitter on the peripheral. We had to power cycle the sensor to get back to normal operation/advertising.

Another time, we disconnected and the peripheral went straight to a flat transmitter pulse again. We never seem to see this on iOS, and it's rare on Android. Well aware of the hurdles with Android...but just getting this out there in case anyone quickly has any pointers.

Have to imagine some sort of connection is re-opened after the disconnect...or the disconnect fails. In either case, perhaps the connection opens, Android switches interval to 7.5ms, and then the peripheral's desired rate is never processed?

  • 0
    TI__Mastermind 39800 points
    Andy,

    Are you using the CC2640 or the CC2640R2F?

    Also, if you are using the latter, can you please inform me of what version of the SDK you are using along with providing any sniffer captures? I'd be interested to see what GAP_TerminateLinkpackets specifically and their reason codes.

    May be good to reference Task 6 of this lab:
    dev.ti.com/.../ble_connections.html

    I would be curious to see if this happens with another LaunchPad running hosttest with BTool as well.
  • 0 in reply to Evan W
    Intellectual 270 points

    CC2640. Stack 2.2.2

    Will provide sniffers when I can -- limited to TI CC2650 dongle sniffer and very difficult to replicate.

    My thinly layered theory is some connect is re-issued, services are called to be discovered from Android (triggering the 7.5ms interval), and then I'm not sure -- some irregular workflow in the code since it can't recover.

    Interestingly, if I call a disconnect in the Android app immediately after the services are discovered, the sensor's transmission flatlines and nothing works until reboot...only doing this to see if that scenario is somehow related.

  • 0 in reply to Andy Lamping
    TI__Mastermind 39800 points
    Andy,

    If you use the CC2541 USB BLE Sniffer with Packet Sniffer v1 you should be able to see a lot more information.

    processors.wiki.ti.com/.../BLE_sniffer_guide

    I'm not aware of the CC2650 dongle sniffer. Are you meaning host_test running on a CC2650?
  • 0 in reply to Evan W
    Intellectual 270 points

    Yes, I'm sorry -- CC2540Dongle Rev 1.1.2. Will be trying to replicate (did earlier but unfortunately sniffer had crashed). Thank you

  • 0 in reply to Andy Lamping
    TI__Mastermind 39800 points
    Andy,

    Due to inactivity, I'm going to close this post and mark as TI Thinks Resolved. If you have any updates, feel free to reopen the post by just posting a follow up question. After 30-days of inactivity, this post will lock.