[jira] [Resolved] (MYNEWT-822) newtmgr - Native BLE - reconnect on immediate supervision timeout

["Christopher Collins (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MYNEWT-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Collins resolved MYNEWT-822.
----------------------------------------
    Resolution: Fixed

> newtmgr - Native BLE - reconnect on immediate supervision timeout
> -----------------------------------------------------------------
>
>                 Key: MYNEWT-822
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-822
>             Project: Mynewt
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: Newtmgr
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
>             Fix For: v1_2_0_rel
>
>
> (Pull request: https://github.com/apache/mynewt-newtmgr/pull/16)
> The first data packet to be exchanged over a BLE connection has a high probability of triggering a disconnect.  The sending controller uses this packet to determine if the connection attempt was successful in the first place, and it does not get retried if it gets dropped.
> In the case of newtmgr, the first data packet gets sent during ATT MTU negotiation.  The bhd (blehostd) transports recover from a disconnect during ATT MTU negotiation by reopening the session.
> The ble transports (native BLE) do not recover from such a disconnect.  We should add the same recovery logic for the ble transports that has already been implemented for bhd.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)