You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2020/12/17 17:25:16 UTC

[GitHub] [mynewt-nimble] btsimonh commented on issue #890: ble_gap_terminate timeout?

btsimonh commented on issue #890:
URL: https://github.com/apache/mynewt-nimble/issues/890#issuecomment-747582547


   yep, much logging later.
   The controller acknowledges the disconnect command, but we hear nothing after that.
   I'm told by @h2zero that the controller should be responsible for the supervision timeout, and so if the dev does not send anything back, we should still see some action some time after asking for disconnect.
   So..  the question is should NimBLE try to deal with such 'bad behaviour'?  It does have timeouts for some things, but this is not one of them currently.  I did try a mod implementing a timeout; but did not know how to correctly kill everything regarding the connection.  For the moment, I'm timing out on the outside and simply resetting the whole of BLE.
   br,
   simon
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org