<?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>Device ID of DUT used in nAN34 for DTM</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41059/device-id-of-dut-used-in-nan34-for-dtm</link><description>Hello, Is there an easy way to get the device id of the DUT to print out in the python script used in nAN34 for DTM ? thank-you,</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Nov 2018 21:11:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41059/device-id-of-dut-used-in-nan34-for-dtm" /><item><title>RE: Device ID of DUT used in nAN34 for DTM</title><link>https://devzone.nordicsemi.com/thread/159777?ContentTypeID=1</link><pubDate>Fri, 30 Nov 2018 21:11:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e4fae65-397d-463c-9cde-d25395511e49</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;ok, thank-you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device ID of DUT used in nAN34 for DTM</title><link>https://devzone.nordicsemi.com/thread/159663?ContentTypeID=1</link><pubDate>Fri, 30 Nov 2018 08:45:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e8f1211-bfdf-4542-a2cc-1d61995f23d8</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;No, unfortunately not. You&amp;#39;ll need to connect with a SWD debugger.&lt;/p&gt;
&lt;p&gt;DTM does not use the MAC address when running tests. DTM is used for testing the RF PHY, ie: to see if the output power, RX sensitivity, frequency deviation, carrier drift etc. is per bluetooth&amp;#39;s specification.&lt;/p&gt;
&lt;p&gt;It does not use the higher layer protocol packet format.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;In order to read out the default set bluetooth (MAC) address, you need to read the NRF_FICR-&amp;gt;DEVICEADDR[] fields as explained in this thread:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/2112/how-to-get-6-byte-mac-address-at-nrf51822"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/2112/how-to-get-6-byte-mac-address-at-nrf51822&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>