-
-
Notifications
You must be signed in to change notification settings - Fork 284
Fix Firmata crash, J-791. Peripheral discover profile failure, J-788 #391
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Hello, and thanks for your contribution! Unfortunately, your commit message does not follow our guidelines for considerate commit messages.
Please fix these issues by amending the commit ( (This message is automatically generated) |
Hi @sgbihu, the bot is actually asking you to shorten the lines in your commit messages. I've re-written the guide here to be a little bit clearer. Please read it! |
ba4ace3
to
2c2decd
Compare
|
||
void BLEStream::begin(...) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sgbihu @SidLeung please see my comments in #377 (comment).
c19f231
to
e08f1a7
Compare
I tested using the firmata library in this pull request firmata/arduino#335 Not the one in community sketches. Passed |
c1ba714
to
11108f7
Compare
1. Add example sketch libraries/CurieBLE/examples/peripheral/broadcast
…ice Git#384 1. The root cause is Nordic stack can't return long UUID when discover - Change the discover process. - Add read operation after discover returned invalid UUID.
…t triggered 1. Root casue: The callback regiter before the begin and the begin reset the callback. 2. Solution: Remove it from the init method and init it when create.
1. Root casue: the stack need use connected device to get the state. The current code used local address to get the link and get an error. 2. Solution: Use central's address to get connection state.
The above PR have been merged. Closing. |
38e6a29 and 1af2c57 are for bug fix. The other's are new developed feature.
The 38e6a29 try to resolve gitHub issue #377 and Jira 791
The 1af2c57 try to resolve #382 and Jira 788.