MCP android long write

RE: MCP android long write

Hung Bui — Wed, 20 May 2015 14:06:27 GMT

@bart: I'm glad that you found the solution. I think the reason for this is that on MCP we will check if the write without response is allowed in the property we will use write command. And this won't allow writing more than 20 bytes. If write without response is not allowed, we will use write request, and this will allow long write.

You can modify your app so that it will use write request regardless the property of the characteristic allow write command.

RE: MCP android long write

Hung Bui — Wed, 20 May 2015 14:00:29 GMT

@bart: We don't add any code in the BLE_GATTS_EVT_WRITE because there is no action needed in the application when receiving a write. If you debug the application you can see it's jump to BLE_EVT_USER_MEM_REQUEST event when you start write long.

RE: MCP android long write

bart — Wed, 20 May 2015 13:10:44 GMT

Thanks for the reply, I checked the code, cause I'm working on linux and I don't know how to use all the settings you include with the project to compile and upload it :) It doesn't include the handling of the write event as far as i could tell.

RE: MCP android long write

bart — Wed, 20 May 2015 13:07:59 GMT

Turns out that I had to set char_props.write_wo_resp = 0

RE: MCP android long write

Hung Bui — Wed, 20 May 2015 09:19:28 GMT

@Bart: I don't think you need char_ext_props.reliable_wr = 1 if you just want long write. Not sure what could be wrong in your case but can you try my example here and let me know the result?