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:
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.
I tested using Samsung J1 (SM-J120F) with Android 5.1.1 - works perfectly. So I guess the issue is with my Moto G5...
When I program my nRF52-DK with this pre-compiled hex file:
I get "Error 133" in "nRF Beacon for Eddystone" on my Moto G5.
When I use "Beacon Tools" on my Moto G5 with the pre-compiled hexfile, I get the following on the Provisioning tab:
"Eddystone configuration service not supported by this beacon."
Using nRF Connect the log shows:
Generic Access (0x1800)
then 30 seconds later:
Error 22 (0x16): GATT CONN TERMINATE LOCAL HOST
I tested with Sweetblue Toolbox, it connects to the beacon but takes forever to discover services and finally disconnects, logfile attached.