• State Verified Answer
  • Replies 5 replies
  • Subscribers 68 subscribers
  • Views 1230 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 272335
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Disconnect after connect parameters update

Gavin

Hi, 

===========================

Chip: nRF52832

SDK: nRF5_SDK_17.0.2_d674dde

Role: Central /Peripheral

Project: BLE gateway

===========================

We currently encouter a connect issue with our nrf52832 gateway device, we have no idea about it now...

The ble gateway want to connect the heart rate device, which running the ble_app_hrs example in SDK 17,  for test, but it is disconnected after conn parameters update, the reason is 0x8. From the wireshark, the master has send LL_CONNECTION_UPDATE_IND to slave, but the slave no response any more and enters to adv mode.

I require some support in this. I will appreciate the help given.

Thank you.

Parents
  • 0
    The ble gateway want to connect the heart rate device, which running the ble_app_hrs example in SDK 17,  for test, but it is disconnected after conn parameters update, the reason is 0x8. From the wireshark, the master has send LL_CONNECTION_UPDATE_IND to slave, but the slave no response any more and enters to adv mode.

     It is not clear what is happening on the peripheral side since the timestamps are visible in your snapshot. Could it that there is a restart on the peripheral side (mostly APP_ERROR_CHECK)? or could it be a super vision timeout? 

    Could it be that your peripheral has some other logic in handling the BLE_GAP_EVT_CONN_PARAM_UPDATE: event and that logic asserted or caused your peripheral to restart?

Reply
  • 0
    The ble gateway want to connect the heart rate device, which running the ble_app_hrs example in SDK 17,  for test, but it is disconnected after conn parameters update, the reason is 0x8. From the wireshark, the master has send LL_CONNECTION_UPDATE_IND to slave, but the slave no response any more and enters to adv mode.

     It is not clear what is happening on the peripheral side since the timestamps are visible in your snapshot. Could it that there is a restart on the peripheral side (mostly APP_ERROR_CHECK)? or could it be a super vision timeout? 

    Could it be that your peripheral has some other logic in handling the BLE_GAP_EVT_CONN_PARAM_UPDATE: event and that logic asserted or caused your peripheral to restart?

Children
Related