<?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>ESB Device address from hardware ID.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33240/esb-device-address-from-hardware-id</link><description>I have previously developed on the nRF24LU1+. This device would have a CHIPID in the InfoPage, This ID would have guaranteed it does not violate the requirements for ESB addresses. On the rRF5x, I have NRF_FICR-&amp;gt;DEVICEID[2] and NRF_FICR-&amp;gt;DEVICEADDR[2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Apr 2018 10:53:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33240/esb-device-address-from-hardware-id" /><item><title>RE: ESB Device address from hardware ID.</title><link>https://devzone.nordicsemi.com/thread/127798?ContentTypeID=1</link><pubDate>Wed, 11 Apr 2018 10:53:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f99156bb-a2e1-490a-aeb8-5c43f46c9d68</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Andre,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;That is correct. This shall work for BE format.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ESB Device address from hardware ID.</title><link>https://devzone.nordicsemi.com/thread/127668?ContentTypeID=1</link><pubDate>Tue, 10 Apr 2018 15:03:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da9f4916-bea5-4dfd-a6fa-608c0ba8b31d</guid><dc:creator>Andre</dc:creator><description>&lt;p&gt;Thanks for your quick reply,&lt;/p&gt;
&lt;p&gt;Looking at nrf_esb.c, function update_rf_payload_format_esb_dpl, ESB is configured to use big endian.&lt;/p&gt;
&lt;p&gt;So, if I were to use&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;uint32_t address = __REV(NRF_FICR-&amp;gt;DEVICEADDR[0]);&lt;br /&gt;nrf_esb_set_base_address_1(&amp;nbsp;&amp;nbsp; (uint8_t*)&amp;amp;address );&lt;/p&gt;
&lt;p&gt;it would always be valid?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ESB Device address from hardware ID.</title><link>https://devzone.nordicsemi.com/thread/127622?ContentTypeID=1</link><pubDate>Tue, 10 Apr 2018 12:49:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96625dea-026e-462b-9a02-536946b6c200</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;The DEVICEADDR has checks for 0, 0xFF, 0x55, 0xAA in the first byte going on-air, but it has it for little-endian. If you are to use big endian packet format, you&amp;#39;ll have to check the corresponding byte for the four non-recommended values.&lt;/p&gt;
&lt;p&gt;You can set the endianness of the RF payload in the nRF5-series devices (NRF_RADIO-&amp;gt;PCNF1 register, field ENDIAN), so it is important that you check for valid address based on your configured endianness.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;PS: Endianness used in bluetooth LE is little endian.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best 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>