NRF Connect: failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

[paul]

Hi Nordic,

I'm trying to use a nrf52832 dev kit (v1.1.1) with NRF Connect (v2.5.0 on mac) to communicate to my device (NRF52832). My device has implemented MTU exchange using SDK 15.1.0. However, upon connection, NRF Connect throws an error related to MTU reply. Note that I've tried running "msddisable" on j-link on the DK. 

In my device logs, I don't see anything strange, but the NRF connect thinks that the remote user terminated the connection.

Is this a known issue?

[Peter Kenyon]

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

[Peter Kenyon]

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

[Peter Kenyon]

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

[Mttrinh]

Hi, 

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

[Shrinidhi Bhat]

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

Can any Nordic developer help me out here?

[Mttrinh]

Hi,

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