<?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>Gazell reception interrupt for nRF24LU1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51843/gazell-reception-interrupt-for-nrf24lu1</link><description>To the kind attention of Nordic support team, 
 I have got legacy code to work with for nRF24LU1. Radio packets payload and receiving pipe are retrieved using if(gzll_rx_fifo_read(payload, &amp;amp;length, &amp;amp;receive_pipe)) instruction inside a super loop polling</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 06 Sep 2019 13:56:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51843/gazell-reception-interrupt-for-nrf24lu1" /><item><title>RE: Gazell reception interrupt for nRF24LU1</title><link>https://devzone.nordicsemi.com/thread/208490?ContentTypeID=1</link><pubDate>Fri, 06 Sep 2019 13:56:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59835364-dedd-4e1d-9d4d-fb7c42a4c1f3</guid><dc:creator>astella</dc:creator><description>&lt;p&gt;Thank you very much&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell reception interrupt for nRF24LU1</title><link>https://devzone.nordicsemi.com/thread/208480?ContentTypeID=1</link><pubDate>Fri, 06 Sep 2019 13:36:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3eea39f7-9e15-4e4d-b930-2cdeb9f18908</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;Unfortunately, the nRF24L implementation of gazell is designed around polling. There&amp;#39;s certain aspects in 8051 that can be challenging, such as function pointers, as there&amp;#39;s several RAM types in 8051, and handling memory overlaying can then be challenging. See this app note for more info:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.keil.com/appnotes/docs/apnt_129.asp"&gt;http://www.keil.com/appnotes/docs/apnt_129.asp&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&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>