RE: Missing BLE_L2CAP_EVT_CH_RX Event

Torsten Robitzki — Wed, 20 May 2020 14:19:36 GMT

Hi Hung,

are you sure we should take those diagrams as requirements for the number of outstanding read buffers? If so, shouldn't we have at least 3 buffer queued for reading? Otherwise we could not release the channel as shown in this sequence chart: infocenter.nordicsemi.com/.../group___b_l_e___l2_c_a_p___c_h___r_e_l_e_a_s_e___m_s_c.html

If there is a requirement to have at least 2 buffers queued for reading, shouldn't the attempt to configure l2cap_conn_cfg.rx_queue_size to 1 already fail (which it does not).

Anyway, looks like I found a working workaround. So, you can close this topic if you like to.

best regards,

Torsten

Edit: fixed the URL

RE: Missing BLE_L2CAP_EVT_CH_RX Event

Hung Bui — Wed, 20 May 2020 14:04:32 GMT

Hi Torsten,

Could you show how you setup the buffer for L2CAP RX ?
According to this sequence chart you should always has the double buffer:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___l2_c_a_p___c_h___r_x___m_s_c.html?cp=4_6_2_1_2_5_3_1

One in sd_ble_l2cap_ch_setup() and one in first sd_ble_l2cap_ch_rx()