multiperipheral with 64byte MTU

RE: multiperipheral with 64byte MTU

endnode — Tue, 12 Dec 2017 04:41:41 GMT

Just based on this info it suggests that stack don't have enough RAM space to allocate all the resources needed to handle larger MTU sizes in (G)ATT layer. But that would be indicated by certain error codes returned to some SD calls. So if you run the project with proper level of debug print-outs in UART or RTT console you should see it easily. That's why I'm asking what does it mean for you "it doesn't work". If you don't know what is happening inside your system then we cannot help you...

RE: multiperipheral with 64byte MTU

endnode — Tue, 12 Dec 2017 04:24:47 GMT

Again you cannot say "it doesn't work". You need to say "I did this and this, I'm expecting this and this but I see this instead". No one can help you with "it doesn't work" cry.

RE: multiperipheral with 64byte MTU

Dream Cob — Tue, 12 Dec 2017 03:56:00 GMT

Thank you for your comment. Yes, I have tried debug on RTT debugger, but I can't find the solution. when I add following function in gatt_init() function, it doesn't work.

err_code = nrf_ble_gatt_att_mtu_periph_set(&m_gatt, BLE_PACKET_SIZE + OPCODE_LENGTH + HANDLE_LENGTH); APP_ERROR_CHECK(err_code);

BLE_PACKET_SIZE is 65.

RE: multiperipheral with 64byte MTU

endnode — Tue, 12 Dec 2017 03:50:37 GMT

You cannot just say "it doesn't work for 64 byte MTU size", you need to debug it and say what goes wrong according to UART or RTT debug print-outs.