[MYNEWT-822] newtmgr - Native BLE - reconnect on immediate supervision timeout

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: v1_2_0_rel
• Component/s: Newtmgr
• Security Level: Public (Viewable by anyone)
• Assignee: Christopher Collins
• Reporter: Christopher Collins
• Created: 31/Jul/17 19:57
• Updated: 30/Aug/17 13:23
• Resolved: 29/Aug/17 17:53

Description

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

Issue Links

• mentioned in: Page Loading...
• mentioned in: Page Loading...