<?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>nRF54L10 ESB runtime configuration switch issue with data whitening on NCS v3.0.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/129014/nrf54l10-esb-runtime-configuration-switch-issue-with-data-whitening-on-ncs-v3-0-0</link><description>**Environment:** - NCS Version: v3.0.0 - Device: nRF54L10 (PRX role) - Protocol: ESB (Enhanced ShockBurst) 
 **Issue Description:** PRX fails to pair with TYPE2-PTX (no ACK received on PTX) after dynamically switching configuration from TYPE1 to TYPE2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Aug 2026 09:28:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/129014/nrf54l10-esb-runtime-configuration-switch-issue-with-data-whitening-on-ncs-v3-0-0" /><item><title>RE: nRF54L10 ESB runtime configuration switch issue with data whitening on NCS v3.0.0</title><link>https://devzone.nordicsemi.com/thread/570566?ContentTypeID=1</link><pubDate>Tue, 25 Aug 2026 09:28:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ea03edc-ea1e-4eca-9085-4834b62e31dc</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;1. I am not quite sure what changes you have done here, but make sure you check the return value of all esb api() calls. I suspect some of the calls are returning error codes here.&lt;/p&gt;
&lt;p&gt;2. Also, you can find in the datasheet of the nRF54L10 the default register values of the radio and other peripherals if you are uncertain of what they should be by default.&lt;/p&gt;
&lt;p&gt;3. Also to compare the hardware configuration you can do the following:&lt;/p&gt;
&lt;p&gt;Read out all registers for the following situations to compare&lt;/p&gt;
&lt;p&gt;3.1 Boot -&amp;gt; Type1&lt;/p&gt;
&lt;p&gt;3.2 Boot -&amp;gt; Type2&lt;/p&gt;
&lt;p&gt;3.3 Boot -&amp;gt; Type1 -&amp;gt; Type2&lt;/p&gt;
&lt;p&gt;&lt;span&gt;3.4 Boot -&amp;gt; Type2 -&amp;gt; Type1&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;You can read out by&amp;nbsp;&lt;/span&gt;running: python .\read_global_registers.py --all&lt;/p&gt;
&lt;p&gt;To store the output to a file call: python .\read_global_registers.py --all &amp;gt; file1.txt &amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrf54l10_5F00_application.zip"&gt;devzone.nordicsemi.com/.../nrf54l10_5F00_application.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Then you can for instance compare 3.2 vs. 3.3 and 3.1 vs. 3.4.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L10 ESB runtime configuration switch issue with data whitening on NCS v3.0.0</title><link>https://devzone.nordicsemi.com/thread/570540?ContentTypeID=1</link><pubDate>Mon, 24 Aug 2026 14:10:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fdbe51b6-37dc-469e-a2cb-ea5585fbcd3e</guid><dc:creator>Maria Gilje</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you for your inquiry. We will investigate and report back with our findings. Thank you for your patience.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Maria&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L10 ESB runtime configuration switch issue with data whitening on NCS v3.0.0</title><link>https://devzone.nordicsemi.com/thread/570514?ContentTypeID=1</link><pubDate>Mon, 24 Aug 2026 03:00:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7909a3b4-2c9f-44fe-aa26-04970ae89df7</guid><dc:creator>Alex</dc:creator><description>&lt;p class="mantine-focus-auto m_b6d8b162 mantine-Text-root"&gt;After TYPE2 pairing fails, the ESB configuration remains identical to the configuration when TYPE2 pairing succeeds exclude&amp;nbsp;&lt;span&gt;DATAWHITE.&lt;/span&gt;&lt;br /&gt;The ESB configuration is as follows，and is same to the define value:&lt;br /&gt;[00:39:38.268,303] &amp;lt;inf&amp;gt; esb_msg_scan: pair msg: 0x4E784AD1,0x4E784AD1, size:28, role:5,5 state:0x81,in-0x1&lt;br /&gt;[00:39:38.348,159] &amp;lt;err&amp;gt; esb: ESB REG: MODE=0x3 FREQ=0x50 PCNF0=0x00030006 PCNF1=0x01040020[whiteen=0 endian=1 balen=4 maxlen=32] DATAWHITE=0x89004A CRCCNF=0x2&lt;br /&gt;[00:39:38.348,168] &amp;lt;err&amp;gt; esb: ESB ADDR: BASE0=0x12345678 BASE1=0x0FA091B3 PREFIX0=0x2ACA4AE7 PREFIX1=0x1BEA6BEE TXADDR=0 RXADDRS=0x01 TXPOWER=0x18&lt;br /&gt;[00:39:38.348,175] &amp;lt;err&amp;gt; esb: ESB CFG: proto=1 rate=3 mode=1 plen=32 s0len=0 whiteen=0 big_endian=1&lt;br /&gt;[00:39:38.354,238] &amp;lt;err&amp;gt; esb: ESB REG: MODE=0x3 FREQ=0x50 PCNF0=0x00030006 PCNF1=0x01040020[whiteen=0 endian=1 balen=4 maxlen=32] DATAWHITE=0x890040 CRCCNF=0x2&lt;br /&gt;[00:39:38.354,247] &amp;lt;err&amp;gt; esb: ESB ADDR: BASE0=0x12345678 BASE1=0x0FA091B3 PREFIX0=0x2ACA4AE7 PREFIX1=0x1BEA6BEE TXADDR=0 RXADDRS=0x01 TXPOWER=0x13&lt;br /&gt;[00:39:38.354,254] &amp;lt;err&amp;gt; esb: ESB CFG: proto=1 rate=3 mode=1 plen=32 s0len=0 whiteen=0 big_endian=1&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>