• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 843 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.

CC2640R2F: Can't connect to part of iphone7

Kane Tian
Intellectual 320 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640,

I used CC2640R2F on my smart lock broad instead of CC2640. But when I tested my broad with iphone7 by LightBlue and SensorTag APP, I found a strange qusetion.

My iPhone7 version is A1778(same as AT&T、Tmobile version, can't support CDMA) , My colleague's iphone version is A1660(same as Sprint、verizon version,  support CDMA). And our used the same verison system.

My iphone7 could connect to our newest broad, but my colleague's iphone could only scan the broadcast and couldn't connect to our broad.

I have tested the SimpleBLEPeripheral example and the smart lock software, the result is the same.

My colleague's iphone could connect to our broad with CC2640(not CC2640R2F).

Our newest broad can connect all other smartphone, such as iphone6, iphone6s,and all andriod phone.

Can you give me any suggest？

Thanks~

  • 0
    TI__Guru** 105180 points
    Hello Kane,

    This seem strange. Are both iPhones running the same iOS version? Can you run the simple_peripheral application on your board with all GPIOs disabled?

    Also, a sniffer capture would be helpful for the analysis.

    Best wishes
  • 0 in reply to JXS
    Intellectual 320 points
    Hello JXS
    Thank you for your reply.
    Year, all iPhone7 were running the same iOS version, the iOS version is 10.2.1 . And I used simple_peripheral example on my broad.
    I'm preparing to test the RF paramete with my broad, and want to find the different about my broad used CC2640 or CC2640R2.But the test need some time to make an appointment to ues the network analyzer.
    I have no CC2640R2 demo broad now. if you could find a AT&T or TMobile version iphone7, could you test the CC2640R2 launchpad with it?
    Thanks~
  • 0 in reply to Kane Tian
    TI__Guru** 105180 points

    Hi Kane,

    We have the AT&T variant of the iPhone 7 and do not have any issues with establishing connections with CC2640 or CC2640R2F on the respective LaunchPads.

    I think checking the RF is a good next step.

    Best wishes

  • 0 in reply to JXS
    Intellectual 320 points
    Hi JXS,
    Through a series of testing, I found another strange issus about CC2640R2F connect with smartphone. For most of Andriod platform smartphone, when I used more than forty UUIDs(incloud SIG define UUID) , the CC2640R2F couldn't connected to the andriod smart phone. It seems that the most of andriod platform smartphone doesn't support so many UUIDs.
    But when I tested my CC2640R2 code in iOS platform(also more than forty UUIDs), it could be connected with the iphone6/6s,but it couldn't connected with all iphone7/7p. Could you give me any suggest about it? Such as the iOS platform support how much UUIDs or other iOS platform limit for BLE function.
    Our smart lock is ready to mass production and sell, but we found this problem in the final test. And we cannot solve this problem now.
    Sincere thanks for your help~
  • 0 in reply to Kane Tian
    TI__Mastermind 34660 points

    It is very difficult to comment much without a sniffer capture.

    I'm assuming that the CC2640 is a GATT server here?  From the CC2640 perspective, the only limit on the amount of UUID's (i.e. characteristics / attributes) is RAM. However, these are statically allocated at compile-time so this likely isn't your problem. In any case, it wouldn't hurt to check your RAM for issues. See the debugging section of the SDG: http://software-dl.ti.com/lprf/sdg-latest/html/cc2640/index.html

    You'd need to check an iOS / Android forum to see if there is any inherent limit for the relevant OS.

    Regarding your first issue...can you try disabling features with HCI_EXT_SetLocalSupportedFeaturesCmd() to see if the problem goes away?