sd_ble_gap_data_length_update error 0x13

RE: sd_ble_gap_data_length_update error 0x13

akash — Tue, 16 Apr 2019 08:41:02 GMT

Did you solve the problem?

RE: sd_ble_gap_data_length_update error 0x13

run_ar — Mon, 15 Jan 2018 09:51:43 GMT

There is no exact answer to this as that is depending on the application. So the GAP event length wil affect the number of buffer used by communications. the longer the lengtht the more buffers (max 7 i think). You can also have longer events by using the connection extension in the options api, if you want to limit the number of buffers and still be able to send many packets per connection event. The attribute table will need to be increased if you have a lot of services and characteristics, and/or if the size of the characteristics increase. So if you get a NRF_ERROR_NO_MEM when adding service and characteristecs you need to increase the attr_tab_size.

RE: sd_ble_gap_data_length_update error 0x13

djqtsg — Wed, 27 Dec 2017 08:59:40 GMT

OK, if I use peripheral node to call sd_ble_gap_data_length_update(), the ATT MTU exchange can pass and my two UART nodes can work. However, the effective packet size is still 20.

RE: sd_ble_gap_data_length_update error 0x13

djqtsg — Wed, 27 Dec 2017 06:51:42 GMT

yes, I did change RAM start and size.

Yes, I also use RTT viewer to see log messages.

In my testing code, I modified Nordic UART service example codes to extend MTU packet size. My error may be caused by central node calling sd_ble_gap_data_length_update() upon event BLE_GAP_EVT_CONNECTED.

RE: sd_ble_gap_data_length_update error 0x13

Dream Cob — Wed, 27 Dec 2017 06:42:15 GMT

sd_ble_gap_data_length_update() function is called by peripheral. After you changed NRF_SDH_BLE_GAP_EVENT_LENGTH from 3 to 200, did you change RAM start and size application use? If you connect segger J-link, you can see log on J-Link RTT viewer using NRF_LOG_INFO or other functions.

RE: sd_ble_gap_data_length_update error 0x13

djqtsg — Wed, 27 Dec 2017 06:12:44 GMT

after changing NRF_SDH_BLE_GAP_EVENT_LENGTH from 3 to 200, that 0x13 error is gone, but I have new error, which I am not sure happens at where.

I wonder who should call sd_ble_gap_data_length_update() to exchange new MTU size, central or peripheral nodes, or both can?

RE: sd_ble_gap_data_length_update error 0x13

Dream Cob — Tue, 26 Dec 2017 11:19:49 GMT

I have resolved this error on changing from 3 to 200 for NRF_SDH_BLE_GAP_EVENT_LENGTH. I have unchanged for NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE. It is 1408 in default.

RE: sd_ble_gap_data_length_update error 0x13

djqtsg — Tue, 26 Dec 2017 10:33:15 GMT

I have also encountered this error.

What are the correct values of NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE and NRF_SDH_BLE_GAP_EVENT_LENGTH?

RE: sd_ble_gap_data_length_update error 0x13

Dream Cob — Mon, 04 Dec 2017 10:12:51 GMT

Did you check NRF_SDH_BLE_GAP_EVENT_LENGTH parameter in sdk_config.h?

RE: sd_ble_gap_data_length_update error 0x13

run_ar — Fri, 06 Oct 2017 08:10:37 GMT

Did you check the RAM start and RAM size settings? And also the size of your attribute table: NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE