Updating ATT MTU to 0 bytes (desired: 0) on connection 0x0.

RE: Updating ATT MTU to 0 bytes (desired: 0) on connection 0x0.

Susheel Nuguru — Wed, 23 May 2018 06:36:26 GMT

there are no stupid questions in this forum. Only experiences that might help others. Thanks for coming back to give a reply. I am marking your answer as verified.

RE: Updating ATT MTU to 0 bytes (desired: 0) on connection 0x0.

Quentin — Tue, 22 May 2018 21:28:55 GMT

I finally found what I was doing wrong. I had a first instance of nrf_ble_gatt_t m_gatt; declared in the context of my init function, but I also had NRF_BLE_GATT_DEF(m_gatt); somewhere else. Which mean that the init was declare with a different structure than the observer and the event handler was called with an uninitialized struct.

I think it is coming from the migration to 14.2. I have been following the migration instructions without thinking too much of what I was doing, and that's when bad things happen.

Anyway, thanks a lot for your help, and sorry for this stupid question.

RE: Updating ATT MTU to 0 bytes (desired: 0) on connection 0x0.

Susheel Nuguru — Tue, 22 May 2018 12:27:43 GMT

Hi Quentin,

Seems strange with that log. But it seems that ATT MTU size is set to 0 explicitly in the app. Can't you set a breakpoint at the place where you set this and see why your app is trying to set the ATT_MTU size to 0?