Support for nRF52x BLE 4.2 and 5 events #6308
Conversation
|
Can confirm that this fixes connection timeout issues I was seeing on the feature-nrf528xx branch. Related forum post: |
|
I believe this is a fix, not a feature (targeting patch release). /morph build |
|
Thanks @AGlass0fMilk for testing :) @0xc0170 more like a fixture ;) - feature enabling a fix? Is that a thing? |
Build : SUCCESSBuild number : 1394 Triggering tests/morph test |
| uint8_t const data_length_peer = | ||
| p_gap_evt->params.data_length_update_request.peer_params.max_tx_octets; | ||
|
|
||
| const uint8_t max_data_length = NRF_SDH_BLE_GATT_MAX_MTU_SIZE + 4 /* L2CAP header size */; |
There was a problem hiding this comment.
The L2CAP header size is defined with L2CAP_HDR_LEN.
There was a problem hiding this comment.
Actually this is defined in nrf_ble_gatt.c in the Nordic SDK so not available in that scope, that's why I put it like that.
Test : SUCCESSBuild number : 1182 |
Exporter Build : SUCCESSBuild number : 1048 |
Description
This pull requests adds handling of 3 BLE 4.2 & 5 events generated by the NRF S132 and S140 softdevices:
It fixes issues encountered when using a device (phone, etc) issuing these requests to the Nordic stack that will issue these events that need to be handled by the application for a connection to be established successfully.
Pull request type