Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Problem when connecting BLE 4.x device and BLE 5.0 device at same time

Need support.

 

I am using lierda S98B module together with Nordic S140 SoftDevice as master. So far everything works fine. I can connect up to 4 devices with BLE 4.2. Also I can connect up to 4 devices with BLE 5.0.

 

But after connecting a BLE 4.x device once no more devices with BLE 5.0 can be connected. If configure BLE_BAS_CONFIG_LOG_LEVEL 4 following debug message can be found:

 

00> <info> app: Start Service Discovery

00> <debug> nrf_ble_gq: Purging request queue with id: 1

00> <debug> nrf_ble_gq: Registering connection handle: 0x0001

00> <debug> ble_db_disc: Starting discovery of service with UUID 0xFFF0 on connection handle 0x1.

00> <debug> nrf_ble_gq: Adding item to the request queue

00> <debug> nrf_ble_gq: GATTC Primary Services Discovery Request

00> <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                       again later.

00> <debug> nrf_ble_gq: Processing the request queue...

00> <debug> nrf_ble_gq: GATTC Primary Service Discovery Request

00> <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                           again later.

00> <debug> nrf_sdh_ble: BLE event: 0x11.

 

Anyone can help ?

Parents
  • Hi Oliver71,

    This is a very strange issue. I don't think anything like this has been reported before.

    BLE_BAS_CONFIG_LOG_LEVEL only increases the log level for the BAS module. Could you please increase NRF_LOG_DEFAULT_LEVEL to 4, and also any modules involved in the process of scan, connect, and service discovery?

    If you are not sure what modules we should log from, please give me an overview of what modules you are using and how the connection process is setup in your code.

    Finally, could you please give an overview of what peripheral devices you are using?

    Hieu

Reply
  • Hi Oliver71,

    This is a very strange issue. I don't think anything like this has been reported before.

    BLE_BAS_CONFIG_LOG_LEVEL only increases the log level for the BAS module. Could you please increase NRF_LOG_DEFAULT_LEVEL to 4, and also any modules involved in the process of scan, connect, and service discovery?

    If you are not sure what modules we should log from, please give me an overview of what modules you are using and how the connection process is setup in your code.

    Finally, could you please give an overview of what peripheral devices you are using?

    Hieu

Children
Related