<?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>NRF24 TX to NRF52 RX without ESB, basic config (no AA/DPL)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117218/nrf24-tx-to-nrf52-rx-without-esb-basic-config-no-aa-dpl</link><description>Hi, 
 I have a nRF24L01+ as the TX and have lots of existing nRF24L01+ RXs. I would like use the nRF52810 as the RX as it saves the need for an MCU and on BOM parts. The current nRF24 TX/RX configuration is very basic, 2Mbit, 5 byte address, 2 bytes static</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 17 Dec 2024 06:27:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117218/nrf24-tx-to-nrf52-rx-without-esb-basic-config-no-aa-dpl" /><item><title>RE: NRF24 TX to NRF52 RX without ESB, basic config (no AA/DPL)</title><link>https://devzone.nordicsemi.com/thread/515221?ContentTypeID=1</link><pubDate>Tue, 17 Dec 2024 06:27:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88e27f4b-ba9c-4bba-9720-b4706baf00d0</guid><dc:creator>alex101</dc:creator><description>&lt;p&gt;Thanks, I took a look at the ESB example with the legacy option set and was able to see the registers of the radio while debugging. Looks like the address needed to be reversed and the prefix slightly changed, now it&amp;#39;s working!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF24 TX to NRF52 RX without ESB, basic config (no AA/DPL)</title><link>https://devzone.nordicsemi.com/thread/514764?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 14:00:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea4c043b-fb30-4227-b005-53bb8c3bd2af</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We dont&amp;#39; really provide support on the nRF24L series anymore.&lt;/p&gt;
&lt;p&gt;There is an attachment in this case that describe how to use the various modes of ESB:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/116941/facing-issue-with-dynamic-payload-of-ack-nrf24l01/513262"&gt;RE: Facing issue with Dynamic payload of Ack NRF24l01&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This should work with the ESB in nRF5 SDK and nRF Connect SDK:&lt;br /&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/nrf/protocols/esb/index.html"&gt;https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/nrf/protocols/esb/index.html&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;a href="https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/esb_users_guide.html"&gt;https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/esb_users_guide.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As a tip as start, do make all address bytes of the same value, just to avoid any problems with endianess.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>