This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

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.

Parents

0 Joakim Jakobsen over 6 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 NordicHam over 6 years ago in reply to Joakim Jakobsen

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Joakim Jakobsen over 6 years ago in reply to NordicHam

Yes, I tested this using a Samsung smartphone using Android 7.0 and Android 8.1.0, and it works as expected.

Is there any particular reason that you are working with an older version of the nRF5 SDK? Maybe you could test the latest nRF5 SDK (currently SDK v.15.2.0)?

Best regards,
Joakim
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 NordicHam over 6 years ago in reply to Joakim Jakobsen

Thank you for the feedback Joakim,

I programmed my nRF52-DK with the following pre-compiled hex:

D:\Nordic\nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_eddystone\hex\ble_app_eddystone_pca10040_s132.hex

Same behaviour on my Moto G5 - when I click connect on the app, the progress circle goes around forever and never connects...

Best regards
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Joakim Jakobsen over 6 years ago in reply to NordicHam

Hi again.

Thanks for testing the new SDK.

Could you try erasing the chip before reprogramming the ble_app_eddystone_pca10040_s132.hex file?

Also, try turning off bluetooth on your phone for around 30 sec. before testing the example again.
Make sure that you follow these instructions when testing the example.

Do you have some logs or maybe a sniffer trace from when you try to connect to the beacon?

Best regards,
Joakim
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Joakim Jakobsen over 6 years ago in reply to NordicHam

Hi again.

Thanks for testing the new SDK.

Could you try erasing the chip before reprogramming the ble_app_eddystone_pca10040_s132.hex file?

Also, try turning off bluetooth on your phone for around 30 sec. before testing the example again.
Make sure that you follow these instructions when testing the example.

Do you have some logs or maybe a sniffer trace from when you try to connect to the beacon?

Best regards,
Joakim
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 NordicHam over 6 years ago in reply to Joakim Jakobsen

Hi Joakim

I did first erase the DK with nRFgo Studio 1.21.2.10, and then programmed it using the hex file.

Waiting 30 seconds before turning on BT did not make any difference.

I am using the test instructions as you've provided - I never reach step 6.

I used Sweetblue to capture a log on my phone, as attached, hopefully it helps

Fullscreen Sweetblue Log.txt Download

12:07:06  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [queue empty]

12:07:06  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Connect(QUEUED nrf5x_eddys_05A6 254165051 )]

12:07:06  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Connect(QUEUED nrf5x_eddys_05A6 254165051 ), Scan(QUEUED 42397820 )]

12:07:06  2018 Info/P_TaskQueue: UPDATE(13545) print() - Connect(EXECUTING nrf5x_eddys_05A6 254165051 ) [Scan(QUEUED 42397820 )]

12:07:07  2018 Warn/P_BleDevice_Listeners: UPDATE(13545) onConnectionStateChange_updateThread() - GATT_ERROR(133) STATE_DISCONNECTED(0)

12:07:07  2018 Info/P_NativeDeviceWrapper: UPDATE(13545) updateNativeConnectionState() - STATE_DISCONNECTED(0)

12:07:07  2018 Info/PA_Task: UPDATE(13545) setState() - Connect(FAILED nrf5x_eddys_05A6 254165051 ) - 412

12:07:07  2018 Warn/P_ConnectionFailManager: UPDATE(13545) onConnectionFailed() - NATIVE_CONNECTION_FAILED, timing=EVENTUALLY

12:07:07  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Connect(QUEUED nrf5x_eddys_05A6 142994609 ), Scan(QUEUED 42397820 )]

12:07:07  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Connect(QUEUED nrf5x_eddys_05A6 142994609 ), Scan(QUEUED 42397820 )]

12:07:07  2018 Info/P_TaskQueue: UPDATE(13545) print() - Connect(EXECUTING nrf5x_eddys_05A6 142994609 ) [Scan(QUEUED 42397820 )]

12:07:08  2018 Info/P_BleDevice_Listeners: UPDATE(13545) onConnectionStateChange_updateThread() - GATT_CONN_SUCCESS(0) STATE_CONNECTED(2)

12:07:08  2018 Info/P_NativeDeviceWrapper: UPDATE(13545) updateNativeConnectionState() - STATE_CONNECTED(2)

12:07:08  2018 Info/PA_Task: UPDATE(13545) setState() - Connect(SUCCEEDED nrf5x_eddys_05A6 142994609 ) - 463

12:07:08  2018 Debug/BleDevice: UPDATE(13545) onNativeConnect() - BOND_BONDED(12)

12:07:08  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [DiscoverServices(QUEUED nrf5x_eddys_05A6 17425814 ), Scan(QUEUED 42397820 )]

12:07:08  2018 Info/P_TaskQueue: UPDATE(13545) print() - DiscoverServices(EXECUTING nrf5x_eddys_05A6 17425814 ) [Scan(QUEUED 42397820 )]

12:07:21  2018 Info/PA_Task: UPDATE(13545) setState() - DiscoverServices(TIMED_OUT nrf5x_eddys_05A6 17425814 ) - 1026

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Disconnect(QUEUED nrf5x_eddys_05A6 221160727 ), Scan(QUEUED 42397820 )]

12:07:21  2018 Warn/P_ConnectionFailManager: UPDATE(13545) onConnectionFailed() - DISCOVERING_SERVICES_FAILED, timing=TIMED_OUT

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - Disconnect(EXECUTING nrf5x_eddys_05A6 221160727 ) [Scan(QUEUED 42397820 )]

12:07:21  2018 Warn/BleManager: UPDATE(13545) update() - Update loop took longer to run than the current interval of 20ms

12:07:21  2018 Info/P_BleDevice_Listeners: UPDATE(13545) onConnectionStateChange_updateThread() - GATT_CONN_SUCCESS(0) STATE_DISCONNECTED(0)

12:07:21  2018 Info/P_NativeDeviceWrapper: UPDATE(13545) updateNativeConnectionState() - STATE_DISCONNECTED(0)

12:07:21  2018 Info/PA_Task: UPDATE(13545) setState() - Disconnect(SUCCEEDED nrf5x_eddys_05A6 221160727 ) - 1027

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Connect(QUEUED nrf5x_eddys_05A6 166952196 ), Scan(QUEUED 42397820 )]

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - Connect(EXECUTING nrf5x_eddys_05A6 166952196 ) [Scan(QUEUED 42397820 )]

12:07:21  2018 Info/P_BleDevice_Listeners: UPDATE(13545) onConnectionStateChange_updateThread() - GATT_CONN_SUCCESS(0) STATE_CONNECTED(2)

12:07:21  2018 Info/P_NativeDeviceWrapper: UPDATE(13545) updateNativeConnectionState() - STATE_CONNECTED(2)

12:07:21  2018 Info/PA_Task: UPDATE(13545) setState() - Connect(SUCCEEDED nrf5x_eddys_05A6 166952196 ) - 1028

12:07:21  2018 Debug/BleDevice: UPDATE(13545) onNativeConnect() - BOND_BONDED(12)

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [DiscoverServices(QUEUED nrf5x_eddys_05A6 31171309 ), Scan(QUEUED 42397820 )]

12:07:21  2018 Info/P_TaskQueue: UPDATE(13545) print() - DiscoverServices(EXECUTING nrf5x_eddys_05A6 31171309 ) [Scan(QUEUED 42397820 )]

12:07:33  2018 Warn/BleManager: MAIN(13516) startScan_private() - A startScan method was called when there's already a scan task in the queue!

12:07:33  2018 Info/PA_Task: UPDATE(13545) setState() - DiscoverServices(TIMED_OUT nrf5x_eddys_05A6 31171309 ) - 1590

12:07:33  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Disconnect(QUEUED nrf5x_eddys_05A6 123849717 ), Scan(QUEUED 42397820 )]

12:07:33  2018 Warn/P_ConnectionFailManager: UPDATE(13545) onConnectionFailed() - DISCOVERING_SERVICES_FAILED, timing=TIMED_OUT

12:07:33  2018 Info/P_TaskQueue: UPDATE(13545) print() - Disconnect(EXECUTING nrf5x_eddys_05A6 123849717 ) [Scan(QUEUED 42397820 )]

12:07:33  2018 Info/P_BleDevice_Listeners: UPDATE(13545) onConnectionStateChange_updateThread() - GATT_CONN_SUCCESS(0) STATE_DISCONNECTED(0)

12:07:33  2018 Info/P_NativeDeviceWrapper: UPDATE(13545) updateNativeConnectionState() - STATE_DISCONNECTED(0)

12:07:33  2018 Info/PA_Task: UPDATE(13545) setState() - Disconnect(SUCCEEDED nrf5x_eddys_05A6 123849717 ) - 1591

12:07:33  2018 Info/P_TaskQueue: UPDATE(13545) print() - Scan(EXECUTING 42397820 ) [queue empty]

12:07:43  2018 Warn/BleManager: UPDATE(13545) update() - Update loop took longer to run than the current interval of 20ms

12:07:44  2018 Info/P_ScanManager: UPDATE(13545) update() - Restarting paused scan...

12:07:47  2018 Info/PA_Task: MAIN(13516) setState() - Scan(SUCCEEDED 42397820 ) - 2143

12:07:47  2018 Info/P_TaskQueue: MAIN(13516) print() - no current task [queue empty]

12:07:47  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Scan(QUEUED 201292711 )]

12:07:47  2018 Info/P_TaskQueue: UPDATE(13545) print() - Scan(EXECUTING 201292711 ) [queue empty]

12:07:51  2018 Info/PA_Task: MAIN(13516) setState() - Scan(SUCCEEDED 201292711 ) - 2314

12:07:51  2018 Info/P_TaskQueue: MAIN(13516) print() - no current task [queue empty]

12:07:51  2018 Info/P_TaskQueue: UPDATE(13545) print() - no current task [Scan(QUEUED 177500532 )]

12:07:51  2018 Info/P_TaskQueue: UPDATE(13545) print() - Scan(EXECUTING 177500532 ) [queue empty]

12:08:01  2018 Info/P_ScanManager: UPDATE(13545) update() - Restarting paused scan...

Thank you

Regards

Jacques

0 Joakim Jakobsen over 6 years ago in reply to NordicHam

Hi.

I didn't see anything from the Log that indicates what the issue is.

I'll keep digging and see if I can find what the cause of this might be.

Best regards,
Joakim
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 NordicHam over 6 years ago in reply to Joakim Jakobsen

Thank you Joakim,

I received a free nRF Dongle at the Nordic Tour here in Cape Town on Monday, so will try use that to implement the Sniffer & send some logs. :-)

Best regards

Jacques
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Joakim Jakobsen over 6 years ago in reply to NordicHam

That's good to hear!

Let me know if you make any progress.

Best regards,
Joakim
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 NordicHam over 6 years ago in reply to Joakim Jakobsen

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel