Nimble GATTS Characteristic Long Read
Posted: Fri Jul 23, 2021 11:13 pm
Hi there!
I have a GATT server that is communicating to an app on android. I have some characteristics that are over 20 bytes in length, and when I tried to read the characteristics, I do not see a way to implement an offset data pointer(which should be in the ATT packet header if I'm not mistaken). From the access callback I can see multiple read requests being sent to the device. I use the api os_mbuf_append in order to place the data onto the outgoing buffer, but I feel like this isn't actually chunking up the data properly when being sent back out(it looks like it is working properly from the NRFConnect app but not from the app in development), is there some way to actually get the offset of data from the incoming packet headers?
I have a GATT server that is communicating to an app on android. I have some characteristics that are over 20 bytes in length, and when I tried to read the characteristics, I do not see a way to implement an offset data pointer(which should be in the ATT packet header if I'm not mistaken). From the access callback I can see multiple read requests being sent to the device. I use the api os_mbuf_append in order to place the data onto the outgoing buffer, but I feel like this isn't actually chunking up the data properly when being sent back out(it looks like it is working properly from the NRFConnect app but not from the app in development), is there some way to actually get the offset of data from the incoming packet headers?