<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116077/cannot-run-sample-peripheral-hids-mouse-on-nrf52-dongle</link><description>Hi, 
 
 While I understand that the sample code is not intended for the nRF52 Dongle, I am still wondering if I can make it work on it. 
 I have successfully tested it on the nRF52DK with nRF52832. 
 
 First, I used a custom overlay for device tree to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 07 Nov 2024 14:18:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116077/cannot-run-sample-peripheral-hids-mouse-on-nrf52-dongle" /><item><title>RE: Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/thread/509479?ContentTypeID=1</link><pubDate>Thu, 07 Nov 2024 14:18:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:083f5293-4fd4-40cd-adb1-199a445464b7</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Seems like it, but it is still the pairing itself that is failing, so they don&amp;#39;t actually reach the pairing status. Are you able to debug and find from what function this pairing failed error is triggered, or where it stops during pairing before it times out I guess is more correct. Could be that the service discovery is what is taking long and just timing out, but it&amp;#39;s hard to say with just these messages. Have you set enabled any debugging logging to get more details on what&amp;#39;s going on. Debugging in nRF Connect SDK is very well described in l&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/"&gt;esson 2 of our NCS intermediate course&lt;/a&gt; on the DevAcademy.&lt;/p&gt;
&lt;p&gt;Another idea could be to sniff the connection using a spare nRF52 DK and the &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE"&gt;nRF Sniffer firmware&lt;/a&gt; and Wireshark to see what&amp;#39;s going on over the air, as that might point out what is causing the pairing process to time out and fail like this.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/thread/509332?ContentTypeID=1</link><pubDate>Wed, 06 Nov 2024 22:47:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f234645-a701-4925-a288-a96f4a09b59f</guid><dc:creator>TomX</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In my understanding, since the Serial Print said&lt;/p&gt;
&lt;p&gt;&amp;quot;&lt;span&gt;Numeric Match, conn 0x20002030&lt;/span&gt;&lt;br /&gt;&lt;span&gt;Security changed: 04:CF:4B:E5:1B:8A (public) level 4&lt;/span&gt;&lt;br /&gt;&amp;quot;&lt;/p&gt;
&lt;p&gt;That means the &amp;quot;accept&amp;quot; buttons has been pressed successfully, right?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/thread/509249?ContentTypeID=1</link><pubDate>Wed, 06 Nov 2024 13:38:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f41d323f-2b10-4ed0-9065-4738858f2c20</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Then I&amp;#39;m inclined to think that the button on the Dongle is not set up correctly as &amp;quot;button 1&amp;quot; in the sample. Have you made sure to change the main file so that the pairing check actually polls the status of the correct pin for the Dongle&amp;#39;s button, and that you build the sample for the nRF52840 Dongle board so the button is set correctly there.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/thread/509172?ContentTypeID=1</link><pubDate>Tue, 05 Nov 2024 18:53:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e24d92f0-97ee-4f63-b892-34ecd11cfc74</guid><dc:creator>TomX</dc:creator><description>[quote userid="75734" url="~/f/nordic-q-a/116077/cannot-run-sample-peripheral-hids-mouse-on-nrf52-dongle/509058"]you have set up the button on the Dongle to work as the &amp;quot;confirm&amp;quot; button during pairing, right?[/quote]
&lt;p&gt;Yes&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I was using a Windows11 device. I was in system&amp;#39;s bluetooth setting page.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When I see the pairing numbers, I clicked accept on the computer first, then press the button.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The same procedure worked for nRF52DK, but not for the nRF52840 Dongle&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Cannot run sample: Peripheral HIDS mouse on nRF52 Dongle</title><link>https://devzone.nordicsemi.com/thread/509058?ContentTypeID=1</link><pubDate>Tue, 05 Nov 2024 09:21:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7845d463-177f-4f3b-8e8a-0106416b77c2</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Just to confirm, you have set up the button on the Dongle to work as the &amp;quot;confirm&amp;quot; button during pairing, right? And then press it when the pairing prompts you to. The pairing failed reason seems to point to a timeout while the disconnect reason is pointing towards the remote user terminating the connection, so whatever you&amp;#39;re trying to connect/pair to is deciding to disconnect. Likely because the pairing timed out. Can you share some details on what device it is that&amp;#39;s functioning as the central here? A phone, a DK or computer? Does it have a log that might show of what&amp;#39;s going wrong?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>