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

Intel Dual Band Wireless-AC 7260 BLE issue

Dear all, 

I'm using an nRF51822 chip for implementing a BLE HID device (mouse) (SDK ver. 12.3.0, SD ver. s130_2.0.1)

I have problems when connecting via BLE with laptops that have Intel 7260 adapter onboard.

Under Windows 10:

It initially pairs and reconnects ok, but after several hours, when switching nRF device power ON-OFF, it stops reconnection.

Sometimes, while working, the driver error appears, and the Intel device disappears from system.

And to recover, it only helps to restart it under Linux.

Under Linux (Ubuntu 16.04, kernel 4.15.0-62):

7260 adapter doesn't finish pairing with nRF device correctly, until I do the following cmd:

sudo hciconfig hci0 noauth

After this, it pairs and reconnects ok - but worked with big lags, mouse motion is very slow.

Any suggestions how to deal with that issue?

Regards, Eugene

Parents
  • Hello Eugene,

    Sorry for the late reply. 

    You say that it works when you use the command "sudo hciconfig hci0 noauth". Do you use MITM protection in your ble_app_hids_mouse project?

    Is it possible to provide a sniffer trace?

    I asked a colleague to check if he had any ideas. He also said that it could help to update the blueZ drivers on the computer, if you use that.

    Best regards,

    Edvin

  • Edvin,

    Yes, either the device is not pairing, or it's not functional.

    Haven't debugged this issue with gdb yet, however I have uart logging and see some of device behaviour.

    I can confirm that no error handler has been caught.

    And - my project is inherited from ble_app_hids_keyboard example, with no big changes with respect to pairing.

    Meanwhile I'll try to provide more information you requested.

  • I don't think the SDKs for nRF51 will print app_errors in the log. So try to debug and set a breakpoint in the error handler (inside APP_ERROR_CHECK). Try to define DEBUG in your preprocessor defines (let me know if you are unsure how to do this), and set a breakpoint on line 76 in app_error_handler() in app_error.c. Does it stop there?

    Just a shot in the dark. May it be that you have stored the bonding information on one side, and deleted it on the other side?

Reply
  • I don't think the SDKs for nRF51 will print app_errors in the log. So try to debug and set a breakpoint in the error handler (inside APP_ERROR_CHECK). Try to define DEBUG in your preprocessor defines (let me know if you are unsure how to do this), and set a breakpoint on line 76 in app_error_handler() in app_error.c. Does it stop there?

    Just a shot in the dark. May it be that you have stored the bonding information on one side, and deleted it on the other side?

Children
No Data
Related