<?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>Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8074/sniffer-for-nrf52-dk</link><description>Hi, 
 I got one of nRF52 DKs. Is there any chance that we can use this DK similar to nRF51 DK as a sniffer in near future? 
 I tried to program the board with the HEX file for nRF51. It will say successfully programmed, but when the Sniffer application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 18 Aug 2018 05:49:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8074/sniffer-for-nrf52-dk" /><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/144778?ContentTypeID=1</link><pubDate>Sat, 18 Aug 2018 05:49:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b9da103-0b57-4e5c-9658-bfeb73e6da92</guid><dc:creator>kaefert</dc:creator><description>&lt;p&gt;I downloaded this package but I&amp;#39;m missing a readme / instructions on how to use it.&lt;br /&gt;&lt;br /&gt;Step 1 probably flashing &amp;quot;sniffer_pca10040_51296aa.hex&amp;quot; on my PCA10040 Dev board.&lt;br /&gt;Already have installed Jlink software for use with the Segger Embedded Studio, but how do I now make my wireshark read and display packages from the NRF52832 board?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;UPDATE: okey so I found this nrf_sniffer python script and tried running it, but even though the python-serial package installed on my system is 3.0.1-1 it fails with this error:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrf_sniffer_2.0.0-beta-1_51296aa/extcap $ ./nrf_sniffer.py --extcap-interfaces
extcap {version=2.0.0}{display=nRF Sniffer}{help=http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer#Downloads}
Traceback (most recent call last):
  File &amp;quot;./nrf_sniffer.py&amp;quot;, line 598, in &amp;lt;module&amp;gt;
    extcap_interfaces()
  File &amp;quot;./nrf_sniffer.py&amp;quot;, line 138, in extcap_interfaces
    for interface_port in get_interfaces():
  File &amp;quot;./nrf_sniffer.py&amp;quot;, line 123, in get_interfaces
    raise RuntimeError(&amp;quot;Too old version of python &amp;#39;serial&amp;#39; Library. Version 3 required.&amp;quot;)
RuntimeError: Too old version of python &amp;#39;serial&amp;#39; Library. Version 3 required.
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;UPDATE2: I found a userguide! &lt;a href="https://www.nordicsemi.com/eng/nordic/Products/nRF52-DK/nRF-Sniffer-UG-v2/65245"&gt;https://www.nordicsemi.com/eng/nordic/Products/nRF52-DK/nRF-Sniffer-UG-v2/65245&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Will read that now.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;UPDATE3: was able to resolve the issue with python-serial by uninstalling the package python-serial v3.0.1-1 from my distribution and installing pyserial 3.4 using this command:&lt;/p&gt;
&lt;pre&gt;&lt;span class="n"&gt;python&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;m&lt;/span&gt; &lt;span class="n"&gt;pip&lt;/span&gt; &lt;span class="n"&gt;install&lt;/span&gt; &lt;span class="n"&gt;pyserial&lt;/span&gt;
&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/121207?ContentTypeID=1</link><pubDate>Mon, 19 Feb 2018 09:24:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c895ca2c-eb31-48a7-8020-4a49991badd9</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;The nRF Sniffer v2 beta 1 is now &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/sniffer/sniffer_intro.html?cp=5_4"&gt;available for nRF52-DK&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28976?ContentTypeID=1</link><pubDate>Wed, 04 Oct 2017 05:02:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa6a4b43-47bf-4313-b10b-29f1ca625583</guid><dc:creator>ajay</dc:creator><description>&lt;p&gt;When i run the sniffer, it crashed and give the following log.&lt;/p&gt;
&lt;p&gt;12:59:49 (China Standard Time) ERROR:
Traceback (most recent call last):
File &amp;quot;C:\bamboo\xml-data\build-dir\BLESNIFFER-RELEASEBUILD-JOB1\Host\Application\SnifferAPI\Packet.py&amp;quot;, line 160, in getPacket
File &amp;quot;C:\bamboo\xml-data\build-dir\BLESNIFFER-RELEASEBUILD-JOB1\Host\Application\SnifferAPI\Packet.py&amp;quot;, line 137, in decodeFromSLIP
UARTPacketError: Unexpected character after SLIP_ESC: 124.
04-Oct-2017 12:59:49 (China Standard Time) ERROR: CRASH
Traceback (most recent call last):
File &amp;quot;C:\bamboo\xml-data\build-dir\BLESNIFFER-RELEASEBUILD-JOB1\Host\Application\SnifferAPI\Sniffer.py&amp;quot;, line 150, in run
File &amp;quot;C:\bamboo\xml-data\build-dir\BLESNIFFER-RELEASEBUILD-JOB1\Host\Application\SnifferAPI\Sniffer.py&amp;quot;, line 175, in runSniffer
File &amp;quot;C:\bamboo\xml-data\build-dir\BLESNIFFER-RELEASEBUILD-JOB1\Host\Application\SnifferAPI\SnifferCollector.py&amp;quot;, line 153, in _continuouslyPipe
AttributeError: &amp;#39;NoneType&amp;#39; object has no attribute &amp;#39;valid&amp;#39;&lt;/p&gt;
&lt;p&gt;any clues?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28975?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 10:12:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:950a55da-479a-473f-bb19-0ec880d72c94</guid><dc:creator>Nivetha</dc:creator><description>&lt;p&gt;Is there an official nRF sniffer released for nRF52840?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28966?ContentTypeID=1</link><pubDate>Fri, 24 Mar 2017 12:25:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:733cfefd-a370-47ca-bec2-6d9631a62b9e</guid><dc:creator>lbehhhh</dc:creator><description>&lt;p&gt;I&amp;#39;m just going to include all the stuff I used to get this working:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;nRFgo Studio:  &lt;a href="https://www.nordicsemi.com/chi/node_176/2.4GHz-RF/nRFgo-Studio"&gt;www.nordicsemi.com/.../nRFgo-Studio&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;nRF command line tools - this might be your problem.  I couldnt get setup working with the package that came bundled with nRFgo Studio, so I uinstalled the version that came with nRFgo studio (via computer -&amp;gt; Uninstall programs) and downloaded the latest v9.3.1 from here and installed with defaults:  &lt;a href="https://www.nordicsemi.com/eng/nordic/Products/nRF51822/nRF5x-Command-Line-Tools-Win32/33444"&gt;www.nordicsemi.com/.../33444&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The hex file I used was the one from directly below this post posted by Hung Bui:  Unofficial_nRF_Sniffer_4_nRF52DK.hex&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;nRF Sniffer.exe:  &lt;a href="http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer/(language)/eng-GB/"&gt;www.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Wireshark v1.10.14:  &lt;a href="https://www.wireshark.org/download/win64/all-versions/"&gt;www.wireshark.org/.../&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Let me know if that does/doesnt work.  I wrote down a bunch of notes as I was troubleshooting.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28965?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2017 21:37:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49f68410-b853-487d-8a30-debb705387eb</guid><dc:creator>kirchki</dc:creator><description>&lt;p&gt;@lbehhhh. When I type &amp;#39;w&amp;#39; the wireshark does start up. But, doesn&amp;#39;t show any packets. However, I could see atleast the initial advertising packets before starting the wireshark. I will try with v1.10.14. Also, can you please let me know which particular hex file you used for testing. Because, there are multiple hex files on this forum, which works for some and doesn&amp;#39;t for some others. So, I would prefer having the same hex file as yours.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28964?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2017 18:47:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9dad7cb3-56f1-4eeb-8157-9f8d1a8dfede</guid><dc:creator>lbehhhh</dc:creator><description>&lt;p&gt;@kirchki When you type &amp;#39;w&amp;#39; into the sniffer console does wire shark actually start up?  Does it give you an error?  I tried with latest version of wireshark and was unsuccessful.  I installed v1.10.14 and got it to work.  I am using nRF52840 DK and can capture packets.   Also make sure you are running the Sniffer.exe as admin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28963?ContentTypeID=1</link><pubDate>Wed, 08 Mar 2017 12:31:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f516ce83-4aac-4f5c-83ee-350c96883af7</guid><dc:creator>kirchki</dc:creator><description>&lt;p&gt;Hello,
I flashed the hex on the nRF52DK and start the ble-sniffer_win_1.0.1_1111_Sniffer.exe. The sniffer finds the BLE devices. After this i select a device to sniff the packets on it. But it says firmware outdated. From the other posts, i understand that this message can be ignored(?) since the hex is not official. But, once i select a device to sniff and type &amp;#39;w&amp;#39; to start the wireshark, i dont see any packets captured by the wireshark. I tried with setting a filter of Tx power &amp;lt;= 4dB, because the advertisements are being Txed at 4dBm. Can anybody tell me what I am missing&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28960?ContentTypeID=1</link><pubDate>Fri, 25 Nov 2016 20:06:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7619be2e-1c49-4a93-a562-a65aedd8c513</guid><dc:creator>morgan</dc:creator><description>&lt;p&gt;I know which settings I&amp;#39;m using, how do someone edit the hex to change the pins? Unless I&amp;#39;ve totally missed the source the of the sniffer being available.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28962?ContentTypeID=1</link><pubDate>Fri, 25 Nov 2016 09:10:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd947acd-ac79-4900-8230-a2590da25958</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;you have to look into boards.h file and see which board settings you are using.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28961?ContentTypeID=1</link><pubDate>Thu, 24 Nov 2016 23:54:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6dd58153-fd4e-4182-9c16-3bf36cf41d58</guid><dc:creator>morgan</dc:creator><description>&lt;p&gt;How does one remap the UART pins? I&amp;#39;m trying to load the Sniffer on an OSHChip (nRF51822) that doesn&amp;#39;t have pins 9/11 exposed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28977?ContentTypeID=1</link><pubDate>Thu, 27 Oct 2016 19:07:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4846675-8fb6-4c35-9394-6223e1516fba</guid><dc:creator>wr</dc:creator><description>&lt;p&gt;I have a NRF52 dev kit and trying to get this board to work as a sniffer. Downloaded above firmware Unofficial_nRF_Sniffer_4_nRF52DK.hex and using python sniffer example. but it is not detecting any ble devices. Do i need to download another firmware?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28974?ContentTypeID=1</link><pubDate>Thu, 28 Apr 2016 21:24:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b2abf61-5ef4-4d9e-9010-307beb6f916a</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;Did a quick test on two laptops.&lt;/p&gt;
&lt;p&gt;Laptop A with nRF51 Dongle, official sniffer firmware, wireshark v1.12.7&lt;/p&gt;
&lt;p&gt;Laptop B with nRF52DK, this hex file, wireshark v2.0.3&lt;/p&gt;
&lt;p&gt;Laptop A is showing SCAN_REQ/SCAN_RSP no problem.&lt;/p&gt;
&lt;p&gt;Laptop B is only showing SCAN_REQ, no SCAN_RSP is captured.&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t try more configurations to see where is the problem. I am afraid of breaking my working environment.&lt;/p&gt;
&lt;p&gt;I thought just reporting what I saw.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28973?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 14:36:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:beb0882c-12ef-4392-b1bf-cfd8a16de65a</guid><dc:creator>Diogo</dc:creator><description>&lt;p&gt;No luck here... Installed Segger 5.10u force a firmware update (meaning that it wasn&amp;#39;t detecting a old one) and still got the same message.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28972?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 14:28:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b66470e-cdc4-40ee-af09-596456258460</guid><dc:creator>KingKarl237</dc:creator><description>&lt;p&gt;Solved it by myself. Updated Segger, restarted, worked.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28971?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 11:38:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2620e9f4-3c06-482f-b0d1-b2c6820b1730</guid><dc:creator>Diogo</dc:creator><description>&lt;p&gt;Also the firmware outdated continues to appear... My guess that the CTRL-R programming fails is that the application is passing the wrong family in the programming line... But even then, how does it detect an outdated version, shouldn&amp;#39;t this unofficial release be an higher revision version? Also which firmware is it complaining about? nRF or JLink?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28970?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 11:25:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b35eaea-7e40-42b8-9324-e0ecd68aabd3</guid><dc:creator>KingKarl237</dc:creator><description>&lt;p&gt;Same problem with this firmware. Just showing Advertisement-Packets.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28969?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 11:21:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c67f102e-609f-4cad-b7cd-b85c1b101055</guid><dc:creator>Diogo</dc:creator><description>&lt;p&gt;Thanks, Hung will try that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28968?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 11:13:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cebe8133-5266-400a-8cc5-8e803110c5b4</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Thanks Hung&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28967?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 11:10:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5047c193-45c0-47d4-8b8f-5f4bbec0c8b6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I attached here a new hex file for the sniffer for nRF52 DK. Please be aware that this is unofficial, and not fully tested. A small bug fix for &lt;a href="https://devzone.nordicsemi.com/question/66725/why-does-my-ble-sniffer-stops-after-2h-and-a-ll_channel_map_req/"&gt;this bug&lt;/a&gt; also added.&lt;/p&gt;
&lt;p&gt;You will see the sniffer console complains about firmware outdated, please ignore that.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/Unofficial_5F00_nRF_5F00_Sniffer_5F00_4_5F00_nRF52DK.hex"&gt;Unofficial_nRF_Sniffer_4_nRF52DK.hex&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28959?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 10:19:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77edbfdb-4de8-477d-851d-d50e634345ea</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Diago,&lt;/p&gt;
&lt;p&gt;The reason that you are not able to program is because the internal scripts of sniffer became outdated as nrfjprog latest version made removed &amp;#39;--programs&amp;#39; and does not allow mixing commands anymore. So it is best to program the sniffer using nRFGo or explicitly by nrfjprog. It should not be a program and seems like you managed to do it. My Colleague @hungbui will update this thread soon with &lt;code&gt;latest unofficial version&lt;/code&gt; with few fixes. I am sorry but it will still be unofficial as we do not know when the official version be released.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28958?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 10:06:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59fe3c18-5b59-4123-a3b4-b366c11b9dff</guid><dc:creator>Diogo</dc:creator><description>&lt;p&gt;Hi Aryan,&lt;/p&gt;
&lt;p&gt;Yes, nRF Studio is able to program it with no problem... Everything seems to be working apart from that annoying message... I thought there was a new Sniffer Release (which there isn&amp;#39;t), and it was complaining from the sniffer version rather than the Segger version...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28957?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 09:58:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58d94c9f-848c-4102-bd19-5b2979a9954c</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Diogo,
Are you having latest segger firmware, i did not understand why your programming failed?!!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28956?ContentTypeID=1</link><pubDate>Tue, 29 Mar 2016 16:28:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8637b4c4-d6ac-4864-828c-852bd68c0c83</guid><dc:creator>Diogo</dc:creator><description>&lt;p&gt;Hi Aryan,&lt;/p&gt;
&lt;p&gt;Would it be possible to get the same change of pin mapping for the last Sniffer firmware?&lt;/p&gt;
&lt;p&gt;I tried the on you posted and I get a message saying:
!!Your firmware is outdated!!
Please upgrade (press CTRL-R).&lt;/p&gt;
&lt;p&gt;Pressing CTRL-R will result on:&lt;/p&gt;
&lt;p&gt;!!Programming Failed!!
An error occurred while programming, you might need to program manually using nRFgo Studio.&lt;/p&gt;
&lt;p&gt;I think the last firmware with just the uart remapping will do...&lt;/p&gt;
&lt;p&gt;Thanks,
Diogo&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sniffer for nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/28955?ContentTypeID=1</link><pubDate>Tue, 22 Mar 2016 07:16:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d481d933-fb8e-436a-82f7-4d6951fcb9ee</guid><dc:creator>KingKarl237</dc:creator><description>&lt;p&gt;Hi. I have tried this Hex-File too and it works first but Wireshark shows only Advertising-Packets. In Sniffer.exe i have marked the Device i want to sniff but if it gets connected, no new Packets are shown. Any Suggestions?
Sniffer.exe says Software V.1111, Firmware V.1, Nordic Plugin: version information unavailable, BTLE plugin V.1111. Wireshark has Version 1.12.10&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>