mynewt-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Collins (JIRA)" <>
Subject [jira] [Updated] (MYNEWT-857) BLE Controller - incompatibility with iOS 11
Date Wed, 18 Oct 2017 17:36:00 GMT


Christopher Collins updated MYNEWT-857:
    Attachment: ios2nimble-no-feat.pcap

Hmm, that's interesting.  Maybe the problem isn't the type of PDU that gets sent, but how
early it gets sent.  I have attached a pcap file showing the successful connect (with the
feature exchange commented out).

> BLE Controller - incompatibility with iOS 11
> --------------------------------------------
>                 Key: MYNEWT-857
>                 URL:
>             Project: Mynewt
>          Issue Type: Task
>      Security Level: Public(Viewable by anyone) 
>          Components: Nimble
>            Reporter: Christopher Collins
>             Fix For: v1.3
>         Attachments: ios2nimble-no-feat.pcap, ios2nimble.pcap, nimble_ios_1033.btt, nimble_ios_1103.btt
> Master: iPhone running iOS 11
> Slave: NimBLE device
> The iPhone successfully establishes a connection to the NimBLE device, but the CoreBluetooth
{{didConnect()}} callback does not get called.  A packet trace (see attached) shows that the
iPhone never initiates service discovery.
> The problem seems to occur when the NimBLE controller initiates the Feature Exchange
Procedure immediately after connection establishment. The {{LL_SLAVE_FEATURE_REQ}} PDU appears
to cause a problem for the iOS device.  When I comment out the call to {{ble_ll_ctrl_proc_start()}}
at the bottom of {{ble_ll_conn_created()}}, the iOS device is able to connect and perform
service discovery, resulting in the CoreBluetooth callback being executed.
> In the attached pcap file, the CONNECT_REQ is at packet #6211.

This message was sent by Atlassian JIRA

View raw message