State Not Answered
Replies 6 replies
Subscribers 88 subscribers
Views 1519 views
Users 0 members are here

Attachments (0)

Nordic Case Info

Case ID: 221223

Options

This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nrf Connect for PC fails to negotiate ATT_MTU > 247 bytes

Peter Kenyon over 7 years ago

Using nRF Connect for PC Version 2.6.1

Connect to a peripheral device that ask for an ATT_MTU > 247 bytes

NRF Connect fails with

Failed to call gattsExchangeMtuReply (NRF_ERROR_INVALID_PARAM)

This is a show stopper

Top Replies

Sigurd over 7 years ago in reply to kobyatom +1

Hi, The bug fix for this issue will likely be fixed in the next release of nRF-Connect BLE app. The fix in the underlaying pc-ble-driver-js was just fixed a couple of days ago as part of this PR .

Parents

0 Peter Kenyon over 7 years ago

It works OK with a PCA10031 and sets an MTU of 23 bytes.

It doesn't work with a PCA10059 or a Nrf5240 DK
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Peter Kenyon over 7 years ago

It works OK with a PCA10031 and sets an MTU of 23 bytes.

It doesn't work with a PCA10059 or a Nrf5240 DK
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data

Related