<?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>Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28597/getting-non-advertising-packets-with-nrf-sniffer</link><description>Hi, I would like to analyze data between a peripheral and a central (BLE 4.1.) It seems that the nRF52 and sniffer can only monitor advertising channels. Am I missing something?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 19 Dec 2017 14:11:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28597/getting-non-advertising-packets-with-nrf-sniffer" /><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113339?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 14:11:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4cc3d735-57ce-453f-af0c-0daf46e83896</guid><dc:creator>mwmccabe</dc:creator><description>&lt;p&gt;Yes, this was resolved. Sometimes (as endnonde mentioned in his original post) the packets won&amp;#39;t be detected beyond the CONNECT_REQ, which happened the first time I tried it (could also have been due to having multiple peripherals with similar names and the one I selected was grabbed by a central when I was selecting it, which also makes the peripheral undetectable unless already selected.) Tried again, and it was working fine.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113340?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 09:43:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6b5b959-d8b3-4e69-9bbf-a745fda91f4b</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;@mwmccabe  Is this issue fixed. If the issue is still not fixed, please add a comment. This type of issue usually points to a segger jlink issue, you need to have segger jlink 6.16c for the nRF sniffer v2-beta1. Follow the troubleshooting guide to downgrade the segger jlink emulator firmware on the board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113338?ContentTypeID=1</link><pubDate>Fri, 15 Dec 2017 17:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af181147-17f3-4773-b151-5605520cb32c</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Well debugging as usual:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Are you running the latest sniffer software, firmware and Wireshark? What nRF5x DK version you use to host sniffer FW?&lt;/li&gt;
&lt;li&gt;Can you make it work withbother BLE devices as test set-up (whih you are sure run BT LE 4.0 or 4.1)?&lt;/li&gt;
&lt;li&gt;If nothing helps can you attach few PCAP capture files and at leat one screenshot?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Using encrypted link shouldn&amp;#39;t matter (but you might be missing PDU decoding) but using anonymous MAC might be a problem (never tried it).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113337?ContentTypeID=1</link><pubDate>Fri, 15 Dec 2017 16:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00252711-95d1-4479-bdf3-60e4be42f3d5</guid><dc:creator>mwmccabe</dc:creator><description>&lt;p&gt;I select the device but there are no packets being detected. I don&amp;#39;t believe there is a passkey or a OOB. What few packets are detected aren&amp;#39;t what I would expect, and are from the advertising channels... Could it be something with the way our BT protocol was structured?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113336?ContentTypeID=1</link><pubDate>Fri, 15 Dec 2017 16:01:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:976a30c0-4388-433a-8167-de126fcffd03</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Have you seen the user guide? &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/sniffer/sniffer_intro.html?resultof=%22%73%6e%69%66%66%65%72%22%20"&gt;infocenter.nordicsemi.com/.../sniffer_intro.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It should be described there.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113335?ContentTypeID=1</link><pubDate>Fri, 15 Dec 2017 15:52:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b89f325-dd40-4c75-8fd2-fd10276ccaf7</guid><dc:creator>mwmccabe</dc:creator><description>&lt;p&gt;Thank you for the reply. I&amp;#39;ve found a CONNECT_REQ packet, but how can I follow the connection?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting non-advertising packets with nRF Sniffer?</title><link>https://devzone.nordicsemi.com/thread/113334?ContentTypeID=1</link><pubDate>Fri, 15 Dec 2017 15:33:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5beff5ec-c22f-4cf8-a4bf-5fe07bdd085d</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;nRF Sniffer can indeed follow the connection so what it is missing is probably CONNECT_REQ packet. Sometimes it happens because nRF Sniffer has only single radio on nRF5x DK board and while it tries to jump over all 3 channels to catch the CONNECT_REQ it cannot do magic. Also make sure that sniffer is in good position because again PCB antenna on nRF5x DK boards doesn&amp;#39;t have properties of some more powerful and more expensive RF analyzers...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>