nRF5_SDK_12.3.0_d7731ad - BLE Peripheral:Eddystone Beacon Application - cannot connect

[NordicHam]

I was able to successfully make the BLE Peripheral Eddystone Beacon Application in "nRF5_SDK_12.3.0_d7731ad" in Windows 7 32-bit (pca10040), using GNU Tools ARM Embedded version "7 2018-q2-update".

I used nRFgo Studio-Win32 version 1.21.2 to program my nRF52-DK with the hex file, as well as S132.

I can view the app on "nRF Beacon for Eddystone" on my Moto G5 Android 7 phone which has the latest kernel and patch.  However, I cannot connect to it, the progress wheel keeps rolling.  Referring to:

http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.gs%2Fdita%2Fgs%2Fnordic_tools.html&cp=1_1

I am never prompted to "Enter the beacon manufacturer lock code" on the Android app.

When I press button 1 on the DK, LED3 illuminates solid, but when I press Connect on the Android app, LED3 switches off, LED2 illuminates solid and LED1 again starts flashing, as if somehow the DK goes back to Broadcast mode.

Any ideas?  I can successfully launch the Eddystone URL using other Android BLE apps.

Thank you.

[Joakim Jakobsen]

Hi.

Sorry about the delay.

Did you make any progress on your issue?

It seems this might be an issue with the phone, as it is working on other models.

It works as expected when I test this myself, but I'll take a look and see what I can find out.

Best regards,
Joakim

[NordicHam]

Thank you Joakim, last time I tested on my Moto G5 (Android 8.1.0) I still had the issue (its now on Android 8.1.0).

Did you test on another phone brand with Android 8.1.0?

[Joakim Jakobsen]

That's good to hear!

Let me know if you make any progress.

Best regards,
Joakim

[NordicHam]

Hi Joakim

I was about to embark on implementing nRF Sniffer on the nRF52840 dongle, but noticed in this post that no s/w available is for the dongle yet:

https://devzone.nordicsemi.com/f/nordic-q-a/40331/nrf52840-dongle-sniffer/156695#156695

Best regards

Jacques

[Joakim Jakobsen]

Hi.

I'm afraid that the nRF52840 dongle isn't supported by the sniffer yet.
We are working on improving the sniffer solution, but I don't have a timeline for when this will be available.

Best regards,
Joakim.

[NordicHam]

I understand, thank you for the update Joakim.

Best regards

Jacques

[Joakim Jakobsen]

No problem.

I will try to update this thread when I know when the Dongle will be supported.

Best regards.

[NordicHam]

Good day Joakim,

HNY!

I programmed this 3rd party beacon:

https://www.beaconzone.co.uk/RadiolandNRF51822Cased

with the BLE Eddystone example in nRF SDK 12.3.0 referencing pca10028.  I had to modify BUTTON_1 in pca10028.h to reference pin 28.

Interestingly I am able to connect to this beacon using "nRF Beacon for Eddystone" Android app on my Moto G5, but with the same app I am unable to connect to the nRF52-DK beacon, as reported in my post above.

When I program my nRF52-DK with:

..\nRF5_SDK_12.3.0\examples\ble_peripheral\ble_app_eddystone\hex\ble_app_eddystone_pca10040_s132.hex

I am still unable to connect.  nRF Logger shown below

Thank you
Regards
Jacques

nRF Connect, 2019-01-04
nRF5x_Eddys (DB:A7:7C:5F:05:A6)
D 09:14:25.858 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED

V 09:14:26.247 Connecting to DB:A7:7C:5F:05:A6...

D 09:14:26.247 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, opportunistic = true, preferred PHY = LE 1M) (hidden)

D 09:14:26.283 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)

I 09:14:26.283 Connected to DB:A7:7C:5F:05:A6

D 09:14:26.286 wait(1600ms)

V 09:14:27.888 Discovering services...

D 09:14:27.888 gatt.discoverServices()

D 09:14:54.248 [Callback] Connection state changed with status: 22 and new state: DISCONNECTED (0)

E 09:14:54.249 Error 22 (0x16): GATT CONN TERMINATE LOCAL HOST

I 09:14:54.249 Disconnected

D 09:14:54.375 [Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED

[Joakim Jakobsen]

That sounds very strange.

It sounds like there might be an issue with the phone.
I'll see if we have a Moto G5 available, so that I can do some tests myself.

Best regards,
Joakim