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

What can cause BLE_HIDS_EVT_NOTIF_ENABLED not to be sent by Host(Xiaomi TV).

I have a simple HID BLE device which send left/right/return/home keys to a Android device.it works well when i test it on my android phone(Lenovo S5).but when i test it on my Xiaomi TV :it works well when if it is first time to pair with the TV, but if I turn off and then turn on the TV again,it can be connected successfully,but  the keys no longer working.i find the difference in the log:when BLE_HIDS_EVT_NOTIF_ENABLED event not to be sent,it fails.

<info> app: Fast advertising.

<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Bonding data, action: Update
<info> app: New Bond, add the peer to the whitelist if possible
<info> app: m_whitelist_peer_cnt 2, MAX_PEERS_WLIST 8
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Central address resolution, action: Update
<info> app: BLE_HIDS_EVT_NOTIF_ENABLED
<info> app: BLE_HIDS_EVT_NOTIF_ENABLED

<info> app: on_disconnected
<info> app: High Duty Directed advertising.
<info> app: Disconnected
<info> app: Fast advertising with whitelist.
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change

SDK version is nRF5 Software Development Kit v16.0.0、s132_nrf52_7.0.1_softdevice,the demo i am learning is ble_app_hids_keyboard.

Parents
  • Hi

    I have looked closer at your sniffer traces, and I have some questions to the failing one. The working one seems to connect and pair as expected, but in the "reconnection error" one I can't see a reconnection or pairing at all. I can see an encryption request/response and an ATT_MTU update before the packets start reporting unexpected SN or Next SN continuously for the remainder of the trace. So it doesn't seem that the reconnection trace contains the reconnection and pairing process at all.

    If you have decided on using the cc2640R2 board instead, I guess there's not much more I can do for you. If you'd like, you can contact the Regional Sales Manager of your area by filling out our Sales Related Questions form, and we will see what we can do to help you.

    Best regards,

    Simon

Reply
  • Hi

    I have looked closer at your sniffer traces, and I have some questions to the failing one. The working one seems to connect and pair as expected, but in the "reconnection error" one I can't see a reconnection or pairing at all. I can see an encryption request/response and an ATT_MTU update before the packets start reporting unexpected SN or Next SN continuously for the remainder of the trace. So it doesn't seem that the reconnection trace contains the reconnection and pairing process at all.

    If you have decided on using the cc2640R2 board instead, I guess there's not much more I can do for you. If you'd like, you can contact the Regional Sales Manager of your area by filling out our Sales Related Questions form, and we will see what we can do to help you.

    Best regards,

    Simon

Children
No Data
Related