<?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>howto identify nrf24l01</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/974/howto-identify-nrf24l01</link><description>hello, on my board the nrf24l01 is optional. 
 what is the preferred solution to identify if a nrf24l01 is present. 
 I tried to read the status register. But sometimes I have a xtalk on MISO line that seems to be a NRF24L01 present. 
 Do you have</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 03 Dec 2013 20:19:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/974/howto-identify-nrf24l01" /><item><title>RE: howto identify nrf24l01</title><link>https://devzone.nordicsemi.com/thread/4625?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2013 20:19:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8970cb15-54df-4433-84be-32db3de630c4</guid><dc:creator>Bastiaan</dc:creator><description>&lt;p&gt;yo, I was just thinking to use that and in addition the RX_ADDR_P1  register which should read 0xC2C2C2C2C2 after reset.
This gives an stronger identificator.&lt;/p&gt;
&lt;p&gt;Thx, for your answer!&lt;/p&gt;
&lt;h2&gt;Adib.&lt;/h2&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: howto identify nrf24l01</title><link>https://devzone.nordicsemi.com/thread/4626?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2013 20:19:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec96f63b-4e1d-4b4c-a286-b2c332328703</guid><dc:creator>Guest</dc:creator><description>&lt;p&gt;yo, I was just thinking to use that and in addition the RX_ADDR_P1  register which should read 0xC2C2C2C2C2 after reset.
This gives an stronger identificator.&lt;/p&gt;
&lt;p&gt;Thx, for your answer!&lt;/p&gt;
&lt;h2&gt;Adib.&lt;/h2&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: howto identify nrf24l01</title><link>https://devzone.nordicsemi.com/thread/4624?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2013 13:29:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0294c26f-7930-43eb-b4da-76d00d58a926</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If you have a lot of cross-talk on your SPI lines, you could try to read a multi-byte register, like the RF address on PIPE0 (default value: 0xe7e7e7e7e7).&lt;/p&gt;
&lt;p&gt;What SPI frequency are you operating on? if it&amp;#39;s very high, you could also try to go down in frequency to see if this helps.&lt;/p&gt;
&lt;p&gt;-H&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>