Posts

Post not yet marked as solved
0 Replies
268 Views
Hello,I have an existiing BLE peripheral (SWD debug probe) that somehow requires high throughput to give a decent user experience. I'm well aware that we have access to the L2CAP layer on iOS and macOS to archive highest throughputs. For compatibility reasons, I would like to stick with GATT / ATT.While implementing a GATT client for that peripheral, I've observed, that the bluetooth stack on my MacBook Pro (15 Zoll, 2016) running macOS Catalina seems to not support more than one PDU per connection event (per direction) on the link layer. The link layer master closes the connection event, even when the link layer ***** indicates more data to be send (by setting the MD Bit in the LL header). In the other direction, when the ATT client issues multiple Write Commands, the MD bit is not set in the PDU from the LL master and only one PDU (containing one Write Command) is send to the peripheral per connection event.The LL_VERSION_IND PDU on the link layer identifies the stack as BLE 4.2 compatible, from Broadcom; Subversion Number: 0x220bIs there a way to ask the MacBooks to use the MD bit and send / receive more than one PDU per direction in a single connection event? Is there any chance that the situation will be different, when using a more recent MacBook?best regards,Torsten
Posted Last updated
.