UART Streaming from central to peripheral

RE: UART Streaming from central to peripheral

TH_HT — Sat, 29 Aug 2020 02:50:17 GMT

Hi Ras,

Could you share me the solution? I have met the same issue.

Thanks a lot.

RE: UART Streaming from central to peripheral

Ros — Tue, 10 Mar 2020 11:20:57 GMT

I have solved the isseue, used DMA to offload some load from CPU at the receiver side.

RE: UART Streaming from central to peripheral

Susheel Nuguru — Thu, 05 Mar 2020 11:56:02 GMT

Sorry for the late response.

from your log itself, it clearly says that

procedure (1) NRF_BLE_GQ_REQ_GATTC_WRITE failed due to 0x13 (NRF_ERROR_RESOURCES)

I see, that is the reason you changed from using WRITE_REQ to WRITE_RSP. That makes sense

using BLE_GATTC_EVT_WRITE_RSP looks correct, but why you got BLE_GATTC_EVT_WRITE_RSP is hard to tell without looking at your code. Can you please post some code snippets.

RE: UART Streaming from central to peripheral

Ros — Sun, 01 Mar 2020 21:43:32 GMT

The disconnection was because the sender goes to the error loop (APP_ERROR_CHECK) while sending the next payload without ACK. I changed back to CMD as I described in the post, I was trying to get a confirmation before sending the next.

Does the following help?

RE: UART Streaming from central to peripheral

Susheel Nuguru — Sun, 01 Mar 2020 17:17:05 GMT

[quote user=""]but the device always disconnects while trying to send second set of data. So I changed the write_req.params.gattc_write.write_op = BLE_GATT_OP_WRITE_CMD to BLE_GATT_OP_WRITE_REQ, and used "BLE_GATTC_EVT_WRITE_RSP" inside[/quote]

It would have been best to actually find out the reason for the disconnect and change the code so as to not to cause the disconnect.

Why did you think that WRITE_REQ would be better than WRITE_CMD in this case? Just trying to understand the need for this change.