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

nrf52840 - BLE devices scanning working but pairing and connect are not working

Hello Nordic DevZone team,
Please find the following setup details which we are using.
- Host side(I.mx6ull): Linux has all the kernel configurations that are enabled and on top of that, we have installed Bluez stack and its utility for testing of our nrf application (zephyr HCI_UART).
- Controller side(nrf52840): We are using nrf52840 BLE chip which is connected with I.mx6ull over Full UART. Apart from that "HCI_UART" application is running on the nrf module having all the changes related to tx/rx/rts/cts pin in the board file. we are using zephyr version 2.1.0.
Please find the following steps that we are using in verification.
- After booting, we are using  "btattach -B <serial port number> -S 1000000" command to enable the HCI interface on i.mx6ull.
- Once we have HCI interface up and running, then we are using "bluetoothctl" command to verify "HCI_UART" application", in "bluetoothctl" scanning is working fine but when we are trying to pair or connect with any BLE device it is showing errors.
After some experiment, we have removed the on-chip BLE module from the UART and hooked up "nrf82540" DK on the same UART, And verified our firmware stack(Bluez stack, Linux kernel configuration and HCI_UART app from zephyr). In this case, all things are working fine. So we are assuming from the host side all things are working fine, we have the following doubts please guide us to resolve this issue.
1. We didn't change anything in HCI_UART application except "tx/rx/rts/cts/" pin value, is it sufficient or we need to change other parameters in the board file?
2. As we are using the nrf52840 chip which is connected with i.MX6ull over UART, How we can see the logs from it. We are using Segger Jlink for flashing.
Parents
  • Hi,

     

    Linux has all the kernel configurations that are enabled and on top of that, we have installed Bluez stack and its utility for testing of our nrf application (zephyr HCI_UART).

    Which kernel version, and which version of BlueZ is used? 

     

    - Once we have HCI interface up and running, then we are using "bluetoothctl" command to verify "HCI_UART" application", in "bluetoothctl" scanning is working fine but when we are trying to pair or connect with any BLE device it is showing errors.

     could you share a log of the issue?

     

    After some experiment, we have removed the on-chip BLE module from the UART and hooked up "nrf82540" DK on the same UART, And verified our firmware stack(Bluez stack, Linux kernel configuration and HCI_UART app from zephyr). In this case, all things are working fine. So we are assuming from the host side all things are working fine, we have the following doubts please guide us to resolve this issue.

     And this is running the same firmware as on your custom device? Or do you have pin configuration that is different? If different, can you please share the .overlay file that you're using?

     

    Kind regards,

    Håkon

Reply
  • Hi,

     

    Linux has all the kernel configurations that are enabled and on top of that, we have installed Bluez stack and its utility for testing of our nrf application (zephyr HCI_UART).

    Which kernel version, and which version of BlueZ is used? 

     

    - Once we have HCI interface up and running, then we are using "bluetoothctl" command to verify "HCI_UART" application", in "bluetoothctl" scanning is working fine but when we are trying to pair or connect with any BLE device it is showing errors.

     could you share a log of the issue?

     

    After some experiment, we have removed the on-chip BLE module from the UART and hooked up "nrf82540" DK on the same UART, And verified our firmware stack(Bluez stack, Linux kernel configuration and HCI_UART app from zephyr). In this case, all things are working fine. So we are assuming from the host side all things are working fine, we have the following doubts please guide us to resolve this issue.

     And this is running the same firmware as on your custom device? Or do you have pin configuration that is different? If different, can you please share the .overlay file that you're using?

     

    Kind regards,

    Håkon

Children
No Data
Related