Issue with peripheral_mds sample not connecting to nRF Memfault application

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Amanda Hsieh — Tue, 27 Jun 2023 15:30:07 GMT

Try to delete the bond information (forget the device from the Bluetooth setting) before pairing it with nRF5340DK, and try reading this characteristic in nRF connect for mobile app and check what is the value.

-Amanda H.

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Anthony W — Fri, 23 Jun 2023 17:56:54 GMT

Yes, the same code with the same key worked for the nRF52 DK (for 2.4.0, same error for NCS 2.3.0).

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Amanda Hsieh — Fri, 23 Jun 2023 17:01:54 GMT

Is the product key from Memfault Dashboards?

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Anthony W — Fri, 23 Jun 2023 16:50:11 GMT

iOS 16.5.1

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Amanda Hsieh — Fri, 23 Jun 2023 16:36:13 GMT

What is your iOS version?

[quote user="Anthony W"]that the app immediately fails to connect with that URI error[/quote]

Can you provide the screen shot?

-Amanda H.

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Anthony W — Fri, 23 Jun 2023 14:50:47 GMT

For the nRF52 DK, using NCS 2.4.0, I'm able to do exactly what you said. I'm not sure why 2.3.0 gives that error. But following the same procedure for the nRF5340 DK the issue I get, from looking at the iOS app and the serial communication, is that the app immediately fails to connect with that URI error, and the serial communication suggests that the device connects, changes the security, then disconnects:

*** Booting Zephyr OS build v3.3.99-ncs1 ***
Starting Bluetooth Memfault example
Bluetooth initialized
Advertising successfully started
Connected 98:50:2E:25:3A:2B (public)
Security changed: 98:50:2E:25:3A:2B (public) level 2
[00:00:05.097,229] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
Disconnected (reason 19)
uart:~$

I don't change anything about the setup (except that I have to add the heap configuration to the _ns build since it's not done by default), I just directly build, flash, and run.

Update:

Sorry, I forgot I was actually able to pair the device. The error above comes after pairing the two. The product key is set (I use the same code, different build configuration for the nRF52 DK).

*** Booting Zephyr OS build v3.3.99-ncs1 ***
Starting Bluetooth Memfault example
Bluetooth initialized
Advertising successfully started
Connected 47:63:DE:A9:8B:93 (random)
[00:00:10.694,000] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
Pairing confirmation required for 47:63:DE:A9:8B:93 (random)
Press Button 1 to confirm, Button 2 to reject.
Pairing confirmed
Security changed: 47:63:DE:A9:8B:93 (random) level 2
Pairing completed: 98:50:2E:25:3A:2B (public), bonded: 1
Disconnected (reason 19)
Connected 98:50:2E:25:3A:2B (public)
Security changed: 98:50:2E:25:3A:2B (public) level 2
[00:00:23.744,537] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
Disconnected (reason 19)
uart:~$

RE: Issue with peripheral_mds sample not connecting to nRF Memfault application

Amanda Hsieh — Fri, 23 Jun 2023 14:41:22 GMT

Hi,

Do you set the project key in the project settings from Memfault Dashboards? If not, please do it.

[quote user=""]After pairing, when trying to connect with the nRF Memfault application on iOS, I would always get the error "Unable to Read Device URI".[/quote]

Do you press Button 1 to confirm pairing? What is the device log when you get the error?

I have tested nRF5340DK and nRF52DK with NCS v2.4.0, but I could not reproduce that error. Could you elaborate in more detail on how to reproduce it?

Regards,
Amanda H.