[GitHub] [mynewt-nimble] KristjanB opened a new issue #1219: Long read to the server returns MTU size response

[GitBox <gi...@apache.org>]

KristjanB opened a new issue #1219:
URL: https://github.com/apache/mynewt-nimble/issues/1219


   I'm trying to use long read on a characteristics (max size is 500 bytes), with MTU size of 180.
   
   The issue is, that on server side, when BLE_GATT_ACCESS_OP_READ_CHR event is called and I call os_mbuf_append() function (as per example), the server only returns MTU size to the client, even though the long read was called. 
   
   I got somewhat working results by calling multiple os_mbuf_appendfrom() where I used MTU size offset for each call (to get the all 500 bytes), but this seemed very sketchy to me. Or is this perhaps the only way to do this?
   
   I could not find any info on long reads with nimble in examples and on the internet, so I'm hoping somebody here can help me.
   
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org