Easy ways to debug BLE connectivity issues

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Thu, 04 Nov 2021 14:28:16 GMT

I unfortunately do not have any way to influence the priority of the tasks for the iOS team - for this you would have to reach out to your Regional Sales Manager (RSM), and ask them to evaluate it.
If you do not know who your RSM is, please send me a direct message with your location so I may provide you with their contact information.

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Wed, 03 Nov 2021 04:28:32 GMT

Isn't it possible to set the priority of the issue you assigned to the iOS team? sure I don't want it resolved overnight but at least some idea as to whether the bug actually exists or some input from the corresponding team?

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Tue, 02 Nov 2021 08:50:02 GMT

[quote user="morpho"]I think the smart approach would be to first trying it on your end, and see whether you're successful in doing so.[/quote]

Part of the issue here is that I am unable to reproduce the behavior you describe on my end, which diminishes the value of debugging actions taken on my end - since I have no idea if the steps I take resolve the issue on your end.
I have discussed this with multiple colleagues as well, and none of them have seen or heard about the behavior you describe, unfortunately.

[quote user="morpho"]And as mentioned earlier too, I have tried deleting the app and reinstalling TO NO AVAIL. I tried it again and the same result.[/quote]

I know this, and I hear you. I only asked you to confirm that you did not do so using the Offload Apps option when you did the reinstallation, as this would mean that the iOS device could keep app data.

[quote user="morpho"]

Please provide a helpful response regarding this. This seems to be getting dragged for a bit now...

[/quote]

As mentioned I have already reported this to our nRF Connect for iOS developers, and I will update you as soon as I hear anything back from them on this issue. Unfortunately, I can not say anything about when this will be.

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Tue, 02 Nov 2021 02:43:46 GMT

I think the smart approach would be to first trying it on your end, and see whether you're successful in doing so. As mentioned earlier, I CANNOT see a clear cache option for the nRF Connect App (as the article talks about third-party apps which isn't the same for ALL the apps including nRF Connect). And as mentioned earlier too, I have tried deleting the app and reinstalling TO NO AVAIL. I tried it again and the same result.

Please provide a helpful response regarding this. This seems to be getting dragged for a bit now...

Thanks

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Mon, 01 Nov 2021 10:11:05 GMT

Hello,

[quote user="morpho"]have you tried it yourself? I know you don't have an iPhone but it'd have been worth a try at least, cause I can't seem to find any option to delete the cache.[/quote]

Ah, my mistake - it seems my described approach was a little too android-y.
My colleague confirm this, and tells me that the way to make sure that an apps cache is cleared in iOS is as described in this article in the Reinstall apps to clear cache section. Could you confirm that you did not use the Offload App option when you reinstalled the application last?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Fri, 29 Oct 2021 16:06:52 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/336695#336695"] I meant the iPhone's system settings, not the nRF Connect's setting. If you go to the settings in which you can administer apps and permissions, etc. there should be an option to clear the app data and cache.[/quote]

have you tried it yourself? I know you don't have an iPhone but it'd have been worth a try at least, cause I can't seem to find any option to delete the cache.

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Fri, 29 Oct 2021 13:25:15 GMT

[quote user="morpho"]Thought you had an iPhone X (or maybe it was someone else's). Regardless, I couldn't find an option to clear the cache in the app. [/quote]

Oh, yes, I borrowed a colleagues iPhone X to perform the previous test.
My apologies, I should have been more specific, I meant the iPhone's system settings, not the nRF Connect's setting. If you go to the settings in which you can administer apps and permissions, etc. there should be an option to clear the app data and cache.
Our developers has unfortunately not gotten back to me yet about the internal ticket I created. I will update you as soon as they do, but I can unfortunately not say anything about when this might be.

[quote user="morpho"]I already mentioned the issues I had with setting up the sniffer. I don't see any relevant option to select the nRF device in wireshark despite copying the Profile_nRF_Sniffer_Bluetooth_LE dir into the profiles folder of wireshark[/quote]

Could you confirm if you successfully program your nRF Device prior to this? And have you successfully installed the python requirements from \extcap\?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Thu, 28 Oct 2021 18:46:03 GMT

I already mentioned the issues I had with setting up the sniffer. I don't see any relevant option to select the nRF device in wireshark despite copying the Profile_nRF_Sniffer_Bluetooth_LE dir into the profiles folder of wireshark

RE: Easy ways to debug BLE connectivity issues

morpho — Thu, 28 Oct 2021 18:38:17 GMT

Thought you had an iPhone X (or maybe it was someone else's). Regardless, I couldn't find an option to clear the cache in the app.

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Thu, 28 Oct 2021 11:13:23 GMT

But, getting back to your original question - we should proceed to look at getting your sniffer up and running in order to properly being able to see what is being transmitted on-air between your devices. This will greatly help any BLE related debugging effort.

Do you have an additional device that you may use as the sniffer's connectivity device for your connection?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Thu, 28 Oct 2021 07:23:47 GMT

Thank you for confirming - I'll write this up in the internal ticket.

To clear an app's cache in iOS you should see a "Clear cache" option when navigating to the app in Settings. I do not have an iOS device myself, but I am making an assumption that this should be an available option for all apps.

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Wed, 27 Oct 2021 16:35:44 GMT

Yes, it says Connecting even though I think it's connected as mentioned earlier. How do you clear the app's cache? In settings?

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Wed, 27 Oct 2021 13:03:33 GMT

[quote user="morpho"]I actually tried this the first time it happened, and it solved the issue but this time i have tried like 4-5 times to no avail[/quote]

That sounds very peculiar indeed. I have not heard of anyone else experiencing this either yet, but I will file an internal ticket with the developers of the application so that they could be aware of it.

Before I do so, could you try to clear the app's cache too, to see if this perhaps fixes the issue?
And just to have it confirmed, the issue is that the view in the screenshot you sent does not change to 'connected' right? It only ever says 'connecting' when this happens?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Tue, 26 Oct 2021 23:51:16 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335973#335973"]could you try this again after uninstalling and reinstalling the nRF Connect application for smartphone entirely?[/quote]

I actually tried this the first time it happened, and it solved the issue but this time i have tried like 4-5 times to no avail

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Tue, 26 Oct 2021 12:49:39 GMT

[quote user="morpho"]App version 2.4.12, and it's an iOS app.[/quote]

Thank you for clarifying.
I just tested this on an iPhone X with the 2.4.12 version without issues - testing against the ble_app_uart application.
Are these the only loggings available in the "Log" section during a connection? Does it not show anything about service discovery and connection parameter updates, etc?

I know that iOS devices sometimes might experience a caching issue if their bluetooth adapter has been on for a long time. Could you try this again after having turned off and on again the phone's bluetooth?
If this does not resolve the issue, could you try this again after uninstalling and reinstalling the nRF Connect application for smartphone entirely?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Tue, 26 Oct 2021 03:30:51 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335746#335746"]Could I ask which phone you are using the nRF Connect application with, and what version of the application you are using?[/quote]

App version 2.4.12, and it's an iOS app.

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335746#335746"]What does the log on the nRF Connect's side say when you connect to a peripheral device (as indicated by the connected event on the peripheral side)?[/quote]

devzone.nordicsemi.com/.../text_2D00_0A90696B4C64_2D00_1.txt

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Mon, 25 Oct 2021 12:38:21 GMT

Hello Morpho,

[quote user="morpho"]right, but how does the phone app work then? I already have my FW running on nRF MCU and I use the app to connect to the BLE profile.[/quote]

Most smartphones already have a available BLE adapter, so the nRF Connect for smartphone application will use this instead of needing an external device.

[quote user="morpho"]

Okay, so ALL i'm trying to do is: create a custom BLE service, and add read/write characteristics to read/send the attribute values. PREVIOUSLY, I have been able to connect to the BLE profile via nRF Connect phone app, but lately i have been seeing issues with nRF Connect app showing it's not CONNECTED, despite the ble_evt_handler getting invoked with a BLE_GAP_EVT_CONNECTED parameter passed in.

I even tried the existing samples from the SDK including the ble_nus app, and it behaves the same way: nRF app doesn't show it's connected/i don't see any profiles but the ble_evt_handler does get passed with BLE_GAP_EVT_CONNECTED.

To me, it looks like connection does happen and there's an issue with the app itself.

[/quote]

Aha - now I understand what you meant earlier. Thank you for elaborating, this made you issue much more clear to me!
This does indeed definitely sound like it could be an issue with the nRF Connect for Smartphones application. Could I ask which phone you are using the nRF Connect application with, and what version of the application you are using?
I will try to reproduce this on my end so that I may raise an internal ticket on this to have it examined, if I am able to reproduce it properly.

[quote user="morpho"]that's what I mean[/quote]

How does the Client tab look? Could you also show me the logs from the nRF Connect application? You could click the 'Log' button to see these.
What does the log on the nRF Connect's side say when you connect to a peripheral device (as indicated by the connected event on the peripheral side)?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Sun, 24 Oct 2021 19:19:56 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335594#335594"]the nRF Connect BLE desktop application requires a nRF device to act as its BLE adapter. The nRF Connect application will prompt you to program the device when you select it from the dropdown menu - it will then program the connectivity firmware it needs to be able to communicate with the device.[/quote]

right, but how does the phone app work then? I already have my FW running on nRF MCU and I use the app to connect to the BLE profile.

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335594#335594"]I am under the impression that you are looking for a way to debug a peripheral application's connectivity / connection issues, is this correct?[/quote]

To me, it looks like connection does happen and there's an issue with the app itself.

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335594#335594"]Could you confirm for me whether you are referring to the program running on the peripheral when you say application?[/quote]

I mean my program/FW is programmed on the said nRF device

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335594#335594"]Could you also elaborate what you mean when you say that the peripheral prints connect when the nRF Connect for Smartphone application attempts to connect, but 'it doesn't "connect" on the phone app'?[/quote]

that's what I mean

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Sun, 24 Oct 2021 16:56:53 GMT

Hello again, Morpho

[quote user="morpho"]I only see one device in nRF Connect desktop app which is my nRF52840. I was trying to simulate on my desktop what I see on the mobile app basically. The desktop app doesn't seem to work the same way though: it doesn't let me scan until I select a device but why?[/quote]

Oh, this is because the nRF Connect BLE desktop application requires a nRF device to act as its BLE adapter. The nRF Connect application will prompt you to program the device when you select it from the dropdown menu - it will then program the connectivity firmware it needs to be able to communicate with the device.
You may then have this device do either scanning or advertising, as you would like. In the central / scanner case you could just click "start scan", but in the advertising / peripheral case you will need to first configure it as a GATT server (different button at the top).

[quote user="morpho"]

Ah, no! I already mentioned in this response that I'm trying to simulate on the desktop with the phone app to see if there's an issue with the phone app itself.

1. I tried following the steps in the tutorial but I can't seem to find the COM PORT in wireshark.

[/quote]

I am still having a hard time understanding exactly what you are trying to achieve here. I am under the impression that you are looking for a way to debug a peripheral application's connectivity / connection issues, is this correct?

If so, I would recommend the following approach:
- Make sure that the peripheral is programmed and running as expected. Is there any indication that the program is running, and the device has started advertising? What does the log's (if enabled) say?
- When you have confirmed that the peripheral is functioning as expected, and that it is advertising, we can move on to debugging the connection itself.
- Choose either the nRF Sniffer or the nRF Connect for Desktop's BLE application to proceed with. The nRF Sniffer gives the complete picture of what is happening on-air between two devices, and can quickly highlight issues within a connection, or issues with advertising.
The nRF Connect for Desktop's BLE application quickly gives a good overview, and visualizes how the peripheral will look to a scanning central device.

So, if your issue is with which profiles, services, and characteristics is exposed - choose nRF Connect for desktop. If your issue is with connection throughput, latency, request rejections, or other connection-specific technicalities, choose the nRF Sniffer.

[quote user="morpho"]Alright. So I tested one more time and I'm fairly certain it's the app that's not functioniong as expected! In the program, ble_evt_handler is invoked and I see the Connect print as soon I attempt to connect from the phone app, but since it doesn't "connect" on the phone app, i don't see any profiles. Are you aware of the issue?[/quote]

Could you confirm for me whether you are referring to the program running on the peripheral when you say application?
I am not aware of any such issue, no. Are you working with a custom application, or are you testing this with a specific example? In case of the latter,, which example?
It would be great if you could share the peripheral's logs with me as well. You could do so by using the Insert -> Code -> Text option here on DevZone.

Could you also elaborate what you mean when you say that the peripheral prints connect when the nRF Connect for Smartphone application attempts to connect, but 'it doesn't "connect" on the phone app'?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Sat, 23 Oct 2021 19:21:11 GMT

Alright. So I tested one more time and I'm fairly certain it's the app that's not functioniong as expected! In the program, ble_evt_handler is invoked and I see the Connect print as soon I attempt to connect from the phone app, but since it doesn't "connect" on the phone app, i don't see any profiles. Are you aware of the issue?

RE: Easy ways to debug BLE connectivity issues

morpho — Sat, 23 Oct 2021 18:32:38 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335415#335415"]which device are you using to do the BLE scanning in the nRF Connect desktop application, or which device have you programmed with the sniffer's connectivity hex? [/quote]

I only see one device in nRF Connect desktop app which is my nRF52840. I was trying to simulate on my desktop what I see on the mobile app basically. The desktop app doesn't seem to work the same way though: it doesn't let me scan until I select a device but why?

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335415#335415"]Are you trying to connect your nRF Connect desktop application to your nRF Connect smartphone application?[/quote]

Ah, no! I already mentioned in this response that I'm trying to simulate on the desktop with the phone app to see if there's an issue with the phone app itself.

1. I tried following the steps in the tutorial but I can't seem to find the COM PORT in wireshark.

2. Is this really needed to debug my issue since I can't even connect to my profile all of a sudden (which I was previously able to!).

3. Is it possible to have a live debug session to help solve the issue a bit faster?

Thanks

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Fri, 22 Oct 2021 08:27:21 GMT

[quote user="morpho"]Yes. Running the script in wireshark/extcap folder does seem to run fine as well. Refreshed the interfaces in Wireshark and still don't see nRF interface showing up.[/quote][quote user="morpho"]I'm using a Mac, and trying to connect to the BLE profile (similar to how I connect using nRF Connect using a phone app). Trying to see i there's something wrong with the phone app[/quote]

Thank you for clarifying.
It seems I was not explicit enough in my previous comment, my mistake, I meant to ask which device you are using for your connectivity device. I.e which device are you using to do the BLE scanning in the nRF Connect desktop application, or which device have you programmed with the sniffer's connectivity hex?

[quote user="morpho"]the BLE profile (similar to how I connect using nRF Connect using a phone app). Trying to see i there's something wrong with the phone app[/quote]

Are you trying to connect your nRF Connect desktop application to your nRF Connect smartphone application?
I have not personally tried this before, but you would then have to set the smartphone to act as a peripheral (GATT server) and have it advertise so that it is connectable for the nRF Connect for desktop application.
Is this what you meant, or might I have misunderstood you?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Thu, 21 Oct 2021 16:03:51 GMT

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335188#335188"]Could you confirm that you completed the step of the installation that concerns the python files and dependencies?[/quote]

Yes. Running the script in wireshark/extcap folder does seem to run fine as well. Refreshed the interfaces in Wireshark and still don't see nRF interface showing up.

 ./nrf_sniffer_ble.sh --extcap-interfaces
extcap {version=3.1.0}{display=nRF Sniffer for Bluetooth LE}{help=https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE}




control {number=0}{type=selector}{display=Device}{tooltip=Device list}
control {number=1}{type=string}{display=Passkey / OOB key}{tooltip=6 digit temporary key or 16 byte Out-of-band (OOB) key in hexadecimal starting with '0x', big endian format. If the entered key is shorter than 16 bytes, it will be zero-padded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,32}))$\b}
control {number=2}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Advertising channel hop sequence. Change the order in which the siffer switches advertising channels. Valid channels are 37, 38 and 39 separated by comma.}{validation=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true}
control {number=3}{type=button}{role=help}{display=Help}{tooltip=Access user guide (launches browser)}
control {number=4}{type=button}{role=restore}{display=Defaults}{tooltip=Resets the user interface and clears the log file}
control {number=5}{type=button}{role=logger}{display=Log}{tooltip=Log per interface}
value {control=0}{value= }{display=All advertising devices}{default=true}

[quote userid="87869" url="~/f/nordic-q-a/80855/easy-ways-to-debug-ble-connectivity-issues/335188#335188"]I notice that you are having some issue with the BLE application of nRF Connect also. Which device are you using for the nRF Connect here? Are you getting the prompt to re-program it when you select it in the drop-down menu?[/quote]

I'm using a Mac, and trying to connect to the BLE profile (similar to how I connect using nRF Connect using a phone app). Trying to see i there's something wrong with the phone app

RE: Easy ways to debug BLE connectivity issues

Karl Ylvisaker — Thu, 21 Oct 2021 07:06:30 GMT

[quote user="morpho"]Alright. It gets frustrating at times when you try to follow along and still don't make it through. I programmed the nRF Sniffer firmware but in wireshark, I don't see the nRF Sniffer COM PORT showing up. Plus I can't seem to get the interface toolbar as shown in the screenshot here. I also have the nRF Sniffer API folder which has a bunch of python files but the link you shared doesn't seem to talk about it. [/quote]

Could you confirm that you completed the step of the installation that concerns the python files and dependencies?

[quote user="morpho"]Also, in my case, BLE doesn't even connect. Do you still think nRF Sniffer tool would be useful? Can I not use nRF Connect on my desktop? Scan devices option is greyed out let alone any scanned devices[/quote]

Yes, if you are able to scan and connect to the device you could use nRF Connect to test that the device works as expected. However, when debugging connection issues the nRF Sniffer is better suited since you may then monitor exactly what is being transferred and negotiated between the two devices.

I notice that you are having some issue with the BLE application of nRF Connect also. Which device are you using for the nRF Connect here? Are you getting the prompt to re-program it when you select it in the drop-down menu?

Best regards,
Karl

RE: Easy ways to debug BLE connectivity issues

morpho — Thu, 21 Oct 2021 05:07:41 GMT

Alright. It gets frustrating at times when you try to follow along and still don't make it through. I programmed the nRF Sniffer firmware but in wireshark, I don't see the nRF Sniffer COM PORT showing up. Plus I can't seem to get the interface toolbar as shown in the screenshot here. I also have the nRF Sniffer API folder which has a bunch of python files but the link you shared doesn't seem to talk about it.

Also, in my case, BLE doesn't even connect. Do you still think nRF Sniffer tool would be useful? Can I not use nRF Connect on my desktop? Scan devices option is greyed out let alone any scanned devices

Any quick support is appreciated