ble_app_uart device is not supported

[Ron]

Hello,

I'm just getting started with my nRF52832 and I am still trying to get the first example of the tutorial page running (Getting started with nRF5 DK. I did everything as described. I work with the SDK V11, Keil 5.21, Termite. Everything works fine, until it comes to using the nRF Toolbox app. I have an HTC One M7 which has Bluetooth 4.0 (HTC One M7) and Android version 5.0.2. But, when I try to connect with the app, it says connected for a fraction of a second and then uncennects and says device is not supported. The log shows the following...

Does this mean my phone is not ready for BLE? I thought that BLE = Bluetooth 4.0.

Thanks for your help.

[Stefan Birnir Sverrisson]

Hi

Yes, Bluetooth 4.0 is BLE, that should be fine. The ble_app_uart example should work out of the box. Just erase the IC, program the softdevice and then program the application, as described in the tutorial. What Android version do you have? Are you able to connect with something else than your phone, just to see if it is a HTC problem or not. Also, make sure you use S132 v2.0.1 with SDK 11 and nRF52.

Also check the accepted answer on this thread.

[Ron]

Hi I use Android version 5.0.2. I only found S132 v2.0.0. in my SDK 11 and on the web. I followed the answer of the other thread. Now two errors appear in the log of the nRF Connect app after refreshing the device cache:

• Cache refreched

• Connected to ...

• Error 129 (0x81): Gatt internal error

• Diconnected

• Error 22(0x16):Gatt Conn terminate local host

there is already an answered question to the first error in this thread. But it didnt help me.

Yes it does work with an iPad, but only with encoding problems (see my other question).

[Ron]

I cleared the bonding and now I get a different error. After connecting and discovering the services successfully, it is stuck in gatt.writeDescriptor(...) and shows error (0x85): GATT error after a few seconds. It disconnects afterwards and shows error(0x8): GATT conn timeout.

I retried more often and once I got it perfectly running, but couldnt repeat this afterwards and dont know what I could have done differently that time.

[Stefan Birnir Sverrisson]

Hi Ron

SD 132 version 2.0.1 is available here.

I suspect the android device is still not making full device discovery for the services and still has an old gatt table with services that you previously bonded with. Try to go into Bluetooth settings on your phone, forget all bluetooth services/devices that you have listed there and perhaps disable Bluetooth and enable it again. Then try to connect with the nRF52 device.

[Ron]

I can now get it the example to run. But still sometimes it is stuck in the write descriptor function. Restarting and stuff like that works in this case.

Thank you