• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 51 subscribers
  • Views 446 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.

CC2642R: CC2642 cannot update connection parameters

wangrenli
Intellectual 690 points
Part Number: CC2642R
Other Parts Discussed in Thread: SYSCONFIG

Hi,

When I change multi_role's project and connect to a peripheral or connect to a cell phone, it initiates a connection parameter update after 10 seconds.

If you connect the peripheral first and then update the parameters, and then connect the IOS phone, you can't initiate the parameter update for IOS, and the GAP_UpdateLinkParamReq interface will always return 0x11. If you connect the Android phone, you can update the parameters normally.

sdk:simplelink_cc13xx_cc26xx_sdk_7_10_01_24

Cell Phone Model：IPhone 13(IOS15.2.1)

  • 0
    TI__Expert 3800 points

    Hi Wangrenli,

    Thanks for reaching out! We will get back to you as soon as possible.

    What do you receive as the return status when connecting to the Android phone when it is updating the parameters normally? I want to ensure that it is not a problem with the project itself and is due to the connection with the iPhone device itself.

    Best regards,

    Luke

  • 0 in reply to Luke
    Intellectual 690 points

    Hi,

    The interface GAP_UpdateLinkParamReq on Android phones returns success and triggers the GAP_LINK_PARAM_UPDATE_EVENT event, while the interface GAP_UpdateLinkParamReq on IOS phones returns 0x11.

  • 0 in reply to wangrenli
    TI__Expert 3800 points

    Wangrenli,

    This sounds like it may be an issue with way the iOS phones are making the connection because the 0x11 corresponds to the bleAlreadyInRequestedMode . The GAP_UpdateLinkParamReq() function should only return this code if a link parameter update is already in progress. For some reason, it seems the CC2642 device thinks that an update is already underway.

    Have you attempted to make this connection with other iPhones on different iOS versions?

    Thanks,

    Luke

  • 0 in reply to Luke
    Intellectual 690 points

    Hi,

    I've tried the following phones and they all have the same problem, iPhone 13 (IOS 15.2.1), iPhone 14 Pro (IOS 16.5), iPhone 7 (IOS 15.7.8)

  • 0 in reply to wangrenli
    TI__Expert 3800 points

    Wangrenli,

    Seeing that the issue is occurring across all of these devices and iOS versions but working properly for Android devices, it is likely that there is something wrong in the communication with the Apple device service. My recommendation would be to take a look at the Apple Notification Center Service documentation and see if there is anything necessary to fix this connection issue. 

    Best regards, 

    Luke

  • 0 in reply to Luke
    Intellectual 690 points

    Hi，

    I think it's a protocol stack issue, I don't see any data from Sniffer that the CC2642 is sending any connection parameter requests, the parameters I'm requesting are (Connection Interval 200ms, Connection Timeout 3000ms, and Latent is 0), and this fully satisfies the IOS requirements.

  • 0 in reply to wangrenli
    TI__Expert 3800 points

    Wangrenli,

    Thanks for sharing your parameters, they do appear to satisfy the IOS requirements properly! Have you made any additional changes to the multi_role project or the sysconfig file?

    Best regards,

    Luke 

  • 0 in reply to Luke
    Intellectual 690 points

    Hi,

    Only the following two changes were made, I often try to change other parameters and the result is the same. The second modification is to also initiate a connection parameter request when doing a central device.

  • 0 in reply to wangrenli
    TI__Expert 3800 points

    Wangrenli,

    If no changes were made to the project other than the ones shown, I am unsure what may be causing the issue at the time. I will reach out to our internal team and see what tests have been done with iOS devices to ensure there is nothing else missing to configure to make this work properly. 

    Thanks,

    Luke