Skip to content

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

Closed
wants to merge 4 commits into from

Conversation

sgbihu
Copy link
Contributor

@sgbihu sgbihu commented Jan 6, 2017

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.

@ndgbuilder
Copy link

Hello, and thanks for your contribution! Unfortunately, your commit message does not follow our guidelines for considerate commit messages.
Specifically:

  • Lines in description exceed 80 characters

Please fix these issues by amending the commit (git commit --amend).

(This message is automatically generated)

@sgbihu sgbihu changed the title Fix Bugs Fix Firmata crash issue and periferal discover profile failed issue Jan 6, 2017
@eriknyquist
Copy link
Contributor

eriknyquist commented Jan 6, 2017

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!

Guidelines for considerate commit messages

@eriknyquist
Copy link
Contributor

eriknyquist commented Jan 10, 2017

Hi @sgbihu, when you are re-building libarc32drv_arduino101.a to fix the conflict, please use "make strip" instead of "make" (also, always use "make strip" from now on). See the discussion on Pull Request #381 for details.

@sgbihu sgbihu force-pushed the master branch 4 times, most recently from ba4ace3 to 2c2decd Compare January 11, 2017 01:30
@SidLeung SidLeung changed the title Fix Firmata crash issue and periferal discover profile failed issue Fix Firmata crash, J-791. Peripheral discover profile failure, J-788 Jan 11, 2017

void BLEStream::begin(...)
Copy link
Contributor

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).

@sgbihu sgbihu force-pushed the master branch 2 times, most recently from c19f231 to e08f1a7 Compare January 13, 2017 01:06
@noelpaz
Copy link
Contributor

noelpaz commented Jan 24, 2017

I tested using the firmata library in this pull request firmata/arduino#335

Not the one in community sketches.

Passed

@SidLeung
Copy link
Contributor

This PR is going to be closed. It has been replaced by the following PRs,
#410
#411

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.
@kitsunami
Copy link

The above PR have been merged. Closing.

@kitsunami kitsunami closed this Feb 21, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CurieBLE: discovering attributes of connect central fails
7 participants