NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Tue, 19 Mar 2019 14:50:57 GMT

Hi,

Looks like one of my colleague are handling your case :)

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Shrinidhi Bhat — Tue, 19 Mar 2019 11:14:17 GMT

Hello. I have created a new case ID 225579 regarding a similar problem.

Can any Nordic developer help me out here?

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Tue, 22 Jan 2019 12:05:16 GMT

Hi,

Thanks for reporting this, this have been reported to the nRF connect developers.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Peter Kenyon — Thu, 17 Jan 2019 16:02:53 GMT

This works OK with PCA10031 BUT not with any of the 82540 devices ie PCA10059 or 82540 DK, I repeat THIS IS A BUG!!!!

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Peter Kenyon — Thu, 17 Jan 2019 15:18:01 GMT

The point is NOT that the MTU should be increased BUT that the negotiation should work correctly,

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Peter Kenyon — Thu, 17 Jan 2019 15:16:13 GMT

Shurely this is a BUG and should be fixed, my device will try to use an MTU up to 500 bytes, but the NRF connect should negotiate downwards to 247 bytes, it does NOT do so correctly and fail with the above message, I have some devices that will stick to 23 bytes and they work OK

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Wed, 16 Jan 2019 13:54:44 GMT

Unfortunately, we won't be able to add this in the near future. This has been added to our list and will be added sometimes later.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

nikiizvorski — Thu, 10 Jan 2019 14:18:19 GMT

We are making some tests at our office and we need it for that. Is it possible for you to make it a variable? Otherwise different devices have different MTU capabilities right. Can we have it In the next update? Much appreciated.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Thu, 10 Jan 2019 12:39:45 GMT

Hi,

Can you give me more details on why it is important for you guys that the MTU size are increased?

Best Regards,

Martin

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

nikiizvorski — Mon, 07 Jan 2019 15:22:57 GMT

Hey guys we have the same issue, can we require a fix for this? on the next update please. Its very important to us we have a lot of chips that we are using and testing.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

nikiizvorski — Mon, 07 Jan 2019 15:01:54 GMT

Hey guys we have the same issue, can we require a fix for this? on the next update please. Its very important to us we have a lot of chips that we are using and testing.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Mon, 22 Oct 2018 13:53:15 GMT

Hi,

I talked to one of my colleague and it seems that nRF Connect for Desktop only support MTU size up to 247, which is why you see the error when going above. Theoretically we could have support bigger MTU size, but chose to limit it to reduce buffer sizes in the connectivity firmware.

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

paul — Fri, 19 Oct 2018 19:07:54 GMT

Yes, same error message occurs on Windows.

I've experimented a bit and found that setting NRF_SDH_BLE_GATT_MAX_MTU_SIZE to 248 in the NRF52 with which NRF Connect is connecting (basically, my device under test) triggers the issue. Setting it to 247 seems to make the issue go away. Value in NRF_SDH_BLE_GAP_DATA_LENGTH seems to have no effect.

Is this a bug in NRF connect?

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

Mttrinh — Fri, 19 Oct 2018 10:29:15 GMT

Hi,

Have you tested with nRF Connect on PC? Do you see the same issue there?

RE: NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

jean-marc — Wed, 17 Oct 2018 12:46:07 GMT

I do have the same problem, setup the server and try to connect with a peripheral.

Jean-Marc