Hello,
I'm wondering if my nRF DK51 is not broken as it behaves quite strange when trying to connect with a BLE Central (iOS and Android devices). For most of the part everything is ok (flashing, RTT, UART, BLE advertising) but when I try to connect on any of devices it immediately breaks the connection.
Initially I thought that it's an iOS thing since there's a few quirks when changing firmware and GATT for a device with the same MAC address. But the same issue persists on Android which IIRC relies less on caching of GATT.
When trying with ble_app_uartwith nRF5 SDK 11 example on Android logs show the following:
...
Connection state changed with new status: 0 and new state: 2 (CONNECTED)
Connected to [MAC]
Discovering Services...
gatt.discoverServices()
Discovering Services...
gatt.discoverServices() //Yes, second time
[Callback] Connection state changed with status: 0 and new state: 0 (DISCONNECTED)
Connection lost
Connection state changed with new status: 0 and new state: 2 (CONNECTED)
Connected to [MAC]
Connection state changed with new status: 0 and new state: 2 (CONNECTED)
Connected to [MAC] //Yes, second time again
Discovering Services...
gatt.discoverServices()
... //and so on
I started having issues while running my own custom firmware and initially thought that I was running out of RAM but after some debugging I came back to SDK examples and noticed that the behaviour is the same.
Is there a chance that my nRF51822 on the DK got damaged somehow and could behave in such way?