Closed GrubbyHalo closed 1 month ago
Hard to tell what is going on. Looks like the MTU negotiation fails. You could try not doing that in the nRF app....
Yes the MTU negotiation seems to be the issue. I changed it from the default of 23 to the max of 517 and it seems to work
I have an app that registers a characteristic. Nothing unusual at all. It works flawlessly on one of my devices but on the other it times out. specifically after running the app a second time. I am using the nRF Connect app as a client. I can't seem to figure out what the problem could be. If i run the bluetoothd with the -d and -n flags, this is the output on the second attempt (the one that fails). Any idea's would be appreciated.
and another but slightly different log output