• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 777 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.

Original question:

CC2640R2F: Iphone X connection Issues

CC2640R2F: Iphone 8 / X pairing problem

user5335699
Prodigy 50 points
Part Number: CC2640R2F

Hello!

We have a iOS app already live at customers which connects to our BT Dongle with CC2640R2F on board.
The pairing is tested and working on different iDevices except the latest iPhones, like the 8 and X until recently, which has BT5 (using a Broadcom BCM4361 wireless combo chip). 

The issue we have on the iPhones 8 and X are that the pairing dialog comes up, but gets dismissed instantly, like the connection attempt is closed directly after it is been made.

I have tried nRF Connect, Bluesee and LightBlue, which all behaves the same.

Still it is not 100% failing all the time, since sometimes the pairing dialog stays after a reconnect but then fails afterwards.
Also I had out of 3 dongles, one connecting properly for a few times, but failed to work after that as well.

We received word that from our external testers, that they had a few iPhones X's which actually worked.
I tested an iPhone X out of the box with that current software version and the newest afterwards with no difference.

Also one thing to note is that we had access to 1 android device with BT5 and that one did not have any connection issues.

Our embedded systems engineer is momentarily not at the office, but I wanted to open this issue already for this is an urgent issue.

Thank you for your time!

Best regards,

Henk-Martijn Leidelmeijer

  • 0
    TI__Mastermind 39610 points
    Henk-Martijn,

    Do you by chance have any sniffer captures of the failing conditions?

    To confirm you are running iOS 11.3.1 on iPhone 8 and iPhone x and seeing occasional connection failures?

    What version of the CC2640R2F SDK are you using?
  • 0 in reply to Evan W
    Prodigy 50 points

    Hi Evan,

    Thank you for you reply.

    The interface is configured as a BLE4.2 device that uses SDK 1.50 with patch ll_enc_swiguard_patch_73b86afd6 applied on top of it. The patch was supplied by TI to fix this issue: https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/630915

    According to our embedded developer, we do have a sniffer, but it is not that good.

    Also there is a iPhone7 added to the list, running iOS 11.3.1, and has the same behaviour, altough it did not have that behaviour prior updating to the latest iOS (previous version unknown). 
    So that is a bit strange, since this iPhone 7 does not have BL5, and other devices we own running the latest iOS don't share this issue like iPhone SE and iPhone 6 and a few tablets.

    I want to add that we are sometimes 100% aböe to connect to the dongle with all the devices which have problems. Not sure if it is session related, certain circomstances are met. like placing on the desk, up time so anything which can influence the device from operating differently. So it is like it is running on some edge case, but this does not explain why older iPhones do work properly.

  • 0 in reply to user5335699
    TI__Mastermind 39610 points
    Henk-Martijn,

    I can ask our RnD team to understand what they've tested on and if they've seen any issues, and in the mean time, if you can try and provide a sniffer capture, that would be helpful. What sniffer are you using?
  • 0 in reply to Evan W
    Prodigy 50 points
    Hi Evan,

    I really have to wait for our embedded developer to return end this week, so we can provide more details and sniffer captures.
    I's sorry I cannot provide the required details now..

    Regards,

    Henk-Martijn
  • 0 in reply to user5335699
    TI__Mastermind 39610 points
    Henk-Martijn,

    No worries. As a note for when your developer comes back, previously we've seen issues with the DLE requests either colliding with other LL control procedures (e.g., encryption start or PHY_UPDATE) or the default DLE RX size of 251 exhausing the ICall heap. A sniffer capture would confirm these accusations or disabling these features could help isolate the symptoms.

    We plan to introduce more collision mitigation in the upcoming SDK for Q2.
  • 0 in reply to Evan W
    TI__Mastermind 39610 points
    Henk-Martijn,

    Closing this post for now since it has moved to emails.
  • 0 in reply to Evan W
    Prodigy 50 points

    Hi Evan!

    Sure, thank you for the help so far!

    Best regards,

    Henk-Martijn