<?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>Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8087/windows-how-to-distinguish-ble-dongle-from-ble-dev-board</link><description>Thanks to this post we can find USB port number of all segger devices connected. 
 But, as commented: 
 
 If I have both the dongle and the dev
kit (plugged to the PC by USB to get
power supply). Then both port names
are found and we cannot know</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Jul 2015 13:31:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8087/windows-how-to-distinguish-ble-dongle-from-ble-dev-board" /><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29030?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:31:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:053b19e5-16cd-4c58-994e-8e9397fdf3be</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;OK, I did not fully understand what &amp;quot;snr&amp;quot; meant in the other post. Now I got it and it works! Thanks a lot for your help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29029?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:18:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:10ef889b-492f-4e9f-8b61-a8d1d63bfd22</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;What do you mean? the registry contains both the Segger ID and the COM Port, that&amp;#39;s how it matches a Segger ID with its COM port, see this line:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;segger_entry_trimmed.StartsWith(snr))
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29028?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:16:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ef740e0-d118-4627-897b-564e8dcf67bf</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;OK, but nrfjprog is most likely unavailable on the end user machine I&amp;#39;ll deploy my application on....the only thing I can use is the registry...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29027?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:14:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d324bbe-2ec4-425d-9e3a-eb6b680e9055</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;It&amp;#39;s the first digits of the segger ID. So if you have:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;$ nrfjprog -i
480208968
480112992
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then you match 4802 and 4801&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29026?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:11:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5f20f0c-5adb-40b7-893f-b0f2b15be7f2</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;Does &lt;code&gt;&amp;lt;SeggerRange snr=&amp;quot;4801&amp;quot; type=&amp;quot;USBDongle&amp;quot; /&amp;gt;&lt;/code&gt; mean dongle can be identified with id 4801? I could not find any key with value 4801 in my registry, what key should I look for?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29025?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:10:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dbf86c0e-b0f3-4cb2-aa8d-14bee163af1f</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;Sorry! this is a public file since it&amp;#39;s placed in users&amp;#39; folders but I myself didn&amp;#39;t know of its existence till today&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29024?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:08:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:264b3cd2-2fc5-439f-acd9-05c8161def80</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I would have killed for that file when I wrote RKNRFGO!!!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29023?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:06:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbb5af03-15f0-4af3-aa88-063e23b50c1c</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;use the  section to identify the type of card based on the Segger ID&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29022?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 13:05:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7371523f-571e-49cd-8148-73cf90dc76bc</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;Found the file, but am not sure to understand how to use the information it contains...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29021?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 12:58:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:62f17ce0-ffba-4056-a2f7-6186d3954774</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;No, but you can take the info in that .xml file and place it in your program&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29020?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 12:57:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3af94016-3848-4d91-b9f9-64ee52b82c75</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;Is &amp;quot;nrfgo studio&amp;quot; always installed when you install the windows drivers? Because my application (trying to find and connect to the dongle) may be deployed on a machine where only the driver was installed (without any debugging/diagnosis tools)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29019?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 12:54:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a71c850-476d-4887-a6ec-0abe33f5be31</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;Look for the following file:&lt;/p&gt;
&lt;p&gt;nrF51deviceids.xml&lt;/p&gt;
&lt;p&gt;in&lt;/p&gt;
&lt;p&gt;c:\users&amp;lt;user&amp;gt;\appdata\local\nordic semiconductor\nrfgo studio&amp;quot;&lt;/p&gt;
&lt;p&gt;should have the information you need.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29018?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 12:40:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4a73143a-1579-4198-80b1-cb592a23ea69</guid><dc:creator>jpo38</dc:creator><description>&lt;p&gt;Exactly ;-) I&amp;#39;d like something generic, plug any dongle, dev kit and it will find out who is who.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Windows: How to distinguish BLE dongle from BLE dev board</title><link>https://devzone.nordicsemi.com/thread/29017?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2015 12:37:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68c4088d-b232-4ffd-bbd4-bf95f1d5cc1d</guid><dc:creator>Carles</dc:creator><description>&lt;p&gt;And I assume having a table mapping Segger ID to type (dongle or devkit) inside your program is not good enough?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>