Anonymous
Not applicable
Feb 05, 2014
09:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 05, 2014
09:35 AM
Is there a list of the errors generated by emconinfo_getDiscReason()?
Central attempted connection (connUP) to peripheral,
but instead of connUP callback, central got connDown callback, in which emconinfo_getDiscReason() reported disconnect reason was "08".
Solved! Go to Solution.
1 Solution
Feb 10, 2014
11:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 10, 2014
11:43 AM
That's a good question. You can check connection parameters as soon as connection is established. Slave can request master to change parameters anytime. So you can also register to process slave request for parameters update by overwriting lel2cap_handleConnParamUpdateReq. Check blecen code how it is done.
8 Replies