This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

CC2541 can't update S120 connection parameters

Hi Guys,

I'm doing a test between CC2541 and Nordic NRF51822. The CC2541 work as a peripheral role. NRF51822 as central role. But CC2541 can update another CC2541 that work as central role.

I didn't see any packet LL_CONNECTION_UPDATE_REQ on sinffer's capture message. Does this problem is a known problem? And any body have a solution?

Thanks!

Parents
  • @bihu: It's correct that the scanning period will drop any connection packet inside that period. However, this only happens when the scan window is large and conflict with connection event. You would need to adjust the scan windows so that it won't block all the connection event.

    No, the TI device when working as peripheral can't send LL_CONNECTION_UPDATE_REQUEST, what it can send is Conection parameter update request on L2CAP layer (Logical link controla and Adaption protocol). The LL_CONNECTION_UPDATE_REQUEST is on link layer and it should be from the master.

Reply
  • @bihu: It's correct that the scanning period will drop any connection packet inside that period. However, this only happens when the scan window is large and conflict with connection event. You would need to adjust the scan windows so that it won't block all the connection event.

    No, the TI device when working as peripheral can't send LL_CONNECTION_UPDATE_REQUEST, what it can send is Conection parameter update request on L2CAP layer (Logical link controla and Adaption protocol). The LL_CONNECTION_UPDATE_REQUEST is on link layer and it should be from the master.

Children
No Data
Related