-
Notifications
You must be signed in to change notification settings - Fork 51
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
GATT CONN FAIL ESTABILISH on esp32 C3 #73
Comments
Hi @adlemx , Error code 3E, implies connection failed due to sync issues. CONNECTION FAILED TO BE ESTABLISHED / So, this can be due to environment reasons . However, you can try to enable BT_NIMBLE_ENABLE_CONN_REATTEMPT in menuconfig, which basically will attempt to re-connect if disconnection is due to reason 0x3E. Also the value BT_NIMBLE_MAX_CONN_REATTEMPT can be changed to decide how many times this re-attempt for connection is to be done, which can be increased as per user's need. So please give this a try. |
@rahult-github thanks for the answer. I already had BT_NIMBLE_ENABLE_CONN_REATTEMPT enabled. I tried setting BT_NIMBLE_MAX_CONN_REATTEMPT to 255, but there was no change. I also tried from another phone, and there was a different error (Error 133 (0x85): GATT ERROR), or is it the same thing? |
Hello @adlemx , So you tried for 255 times for same result ? May i request you to please share esp device side console logs ? |
@rahult-github, Yes, of course, here are the logs from the ESP, but it seems to me that there is nothing useful in it because during connection attempts nothing new appears in the logs
|
Hello @adlemx , My apologies as i misread the initiate statement
Here nrf is initiator, not esp. So on esp side there will be no connection event received. The reattempt connection feature works if connection is initiated from esp side and connection fails with reason 0x3E. Here, central device has to initiate connection again, server side doesn't have any control . In logs also, esp side is advertising continuously. |
@rahult-github I tried sketches from examples\bluetooth\bluedroid\ble_50\ble50_security_server and from examples\bluetooth\bluedroid\ble\gatt_security_server. The example with ble 5.0 works, but just ble gives the same error. Is it possible to make nimble work only with ble 5.0? Enable BLE 5 feature is enabled in the config menu, but apparently it still uses bluetooth 4.2 |
@adlemx , they are different stacks and hence different examples. For equivalent example, you can refer to examples/bluetooth/nimble/bleprph ? |
@rahult-github This example also does not work, could it be a problem with the quartz on the board? And is it possible to switch the ESP to internal clocking? |
I run the standard example from esp-idf-v5.3\examples\bluetooth\nimble\bleh when I try to connect to esp from the nRF connect, it immediately after the connection starts disconnects with the Error 62 (0x3e): GATT CONN FAIL ESTABLISH
I use ESP32 C3 super mini and esp-idf 5.3
Logs from nrf connect:
The text was updated successfully, but these errors were encountered: