Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lld_pdu_get_tx_flush_nb HCI packet count mismatch (10, 11) #359

Open
Blue186 opened this issue Apr 5, 2024 · 0 comments
Open

lld_pdu_get_tx_flush_nb HCI packet count mismatch (10, 11) #359

Blue186 opened this issue Apr 5, 2024 · 0 comments

Comments

@Blue186
Copy link

Blue186 commented Apr 5, 2024

    pClient  = BLEDevice::createClient();
    pClient->setClientCallbacks(new MyClientCallback());
    // 断链时间有点长
    if(!pClient->connect(*bleMacAddress,BLE_ADDR_TYPE_PUBLIC)){
      Serial.println("connect ERR");
      pClient->disconnect();
      return false;
    }

During the process of scanning from the ble client to the server and establishing a connection, if the Bluetooth signal is unstable, or if I power off the server, it will generate an lld_pdu_get_tx_flush-nb HCI packet count mismatch (10,11) error, and it will take a long time (about 30 seconds) to exit the pClient ->connect() function.

At this point, my customer service end is in a completely stuck state. Only when pClient ->connect() is completed can I exit from the stuck state. How can I quickly exit this invalid connection stuck state?

@per1234 per1234 changed the title lld_pdu_get_tx_flush_nb HCI packet count mismatch (10, 11) lld_pdu_get_tx_flush_nb HCI packet count mismatch (10, 11) Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant