-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Fixed incorrect usage of xEventGroupWaitBits #3446
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
Conversation
You may get note on bool vs. wait bitwise value. Originally, those changes resulted in logic errors by mistake. It may fail equal operator logic: (true == bit), as true most likely defined as 1, so 1 != 2, or 4 or 8 & etc. It would only work with bit = 1. It does not affect the existing code though. |
please bring back the braces and check if it's different than 0. While non-null value is technically TRUE, I would like the code to show that properly :) |
I've added the |
surely :D excuse my "English". braces, brackets, parentheses... it's a bit confusing |
I know how it can be, English is not my native language either :) |
to me:
|
I'm having some trouble connecting my ESP32-WROOM-32 to any other device via bluetooth. I'm using the SerialtoSerialBTM example with the address and name modified only. The log I'm getting from the debug is the following:
I've seen that it sets the address right, and when doing the connect() function it returns false when doing waitForConnect(SCAN_TIMEOUT) I've tried to connect to multiple deviced and it always returns false, any way to fix this? Update: I've tried the same program using another ESP32-WROOM-32 that I had and the problem is the same |
@Shunyavic open an issue for your issue rather than hijack a merged PR. |
While this code fixes the bug that it was erroneously telling you it worked, it doesn't fix anything else. I haven't been able to get the master mode working well either |
Related discussion in #3219