• State
  • +2 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 42 subscribers
  • Views 158 views
  • Users 0 members are here
Support feedback
Options
Options
Related

WL1831MOD: BT Coex Tuning Parameters?

x123x
Prodigy 180 points
Part Number: WL1831MOD
Other Parts Discussed in Thread: WL1831,

Tool/software:

Hello,

We are using the WL1831 on a Linux 6.12 system, with the latest TI driver and firmware. We are finding that BLE connections are taking a very long time, in certain environments, when Wi-Fi is active (not necessarily transferring data, but just doing passive scanning while connected to an AP in the background). When Wi-Fi is disconnected from a network, the BLE connection speed improves substantially. Does the TI firmware, NVRAM, or driver provide any options to tune coex priority? I would want to tell the WL1831MOD to prioritize BLE traffic at moments when we know we are trying to pair to a BLE device.

Thank you.

  • 0
    Prodigy 20 points

    Hi, as additional context, we are experiencing the lengthy connections due to excessive failure rates when initiating connections as Central to our bespoke BLE Peripheral. The symptom we see as the Host side of HCI is the 0x3e "Connection Failed to be Established" condition immediately following initial Link Layer attempt:

    Using an iOS stack with nRF Connect for our peripheral, we have nearly 100% successful link establishment (i.e. our first HCI command—LE Read Remote Features—succeeds).

    We observed a similar condition with our other Central role device that uses a different vendor's controller and we were able to resolve the issue by tuning its airtime prioritization parameter. That controller's firmware has separate flags for prioritizing each of BLE connection, initiation, scanning, and advertising over WLAN activities. The BLE initialization flag is the one that helped our application the most in curing this symptom.

    I notice from SWRU423A Sec 8.4.1 Table 24 there is testing for BLE activities' effect on WLAN throughput, which is important to our application (our BLE throughput is minimal). Our concern is getting the WL1831 firmware to dynamically prioritize receiving BLE PDUs in the first six connection intervals after we initiate a BLE link, in order to successfully connect.

    If TI has vendor commands or tools for adjusting this behavior, then we can explicitly request the prioritization ourselves when we want BLE connection prioritization. Please advise.

    Thanks

  • 0 in reply to mosdeffet
    TI__Genius 14601 points

    Hi,

    I am looking into this and will follow up once I have a bit more information.

    Best,

    Rogelio

  • 0 in reply to RogelioD
    Prodigy 20 points

    Thank you! One more detail that directed our investigation towards Wi-Fi/BLE coexistence: dis-associating our device (which is Wi-Fi STA + BLE Central) from AP significantly improves the success rate of getting the LE Remote Features response without a 0x3e disconnection.

  • 0 in reply to RogelioD
    Prodigy 180 points

    Hi  - were you able to get any more info about this?

  • 0 in reply to RogelioD
    Prodigy 180 points

       were you able to get more info?