<?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>micro:bit became unable to talk to nrf52832 by RADIO</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50382/micro-bit-became-unable-to-talk-to-nrf52832-by-radio</link><description>Dear Nordic Semiconductor support team 
 
 Hi, I got your support using micro:bit with nrf52832 by RADIO in the past as follows. 
 https://devzone.nordicsemi.com/f/nordic-q-a/41770/how-can-i-make-nrf52832-talk-to-microbit-by-radio-gazell 
 
 It did work</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Mar 2020 15:38:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50382/micro-bit-became-unable-to-talk-to-nrf52832-by-radio" /><item><title>RE: micro:bit became unable to talk to nrf52832 by RADIO</title><link>https://devzone.nordicsemi.com/thread/242160?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2020 15:38:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a7f4309-7338-4d27-8fe7-2f730f401173</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You might need to do a bytewise_bitswap() on the base_addr_0, before you set it with&amp;nbsp;&lt;span&gt;nrf_esb_set_base_address_0(). If you have further questions about this, please &lt;a href="https://devzone.nordicsemi.com/support/add"&gt;create a new question&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: micro:bit became unable to talk to nrf52832 by RADIO</title><link>https://devzone.nordicsemi.com/thread/241250?ContentTypeID=1</link><pubDate>Tue, 24 Mar 2020 00:38:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f6c9760-d344-4967-aa15-3938afed2139</guid><dc:creator>Le Phuong</dc:creator><description>&lt;p&gt;Hi, Have you any update?&amp;nbsp;&lt;br /&gt;&lt;span&gt;I have a similar problem.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;i config ESB right?&lt;/p&gt;
&lt;p&gt;uint32_t err_code;&lt;br /&gt; uint8_t base_addr_0[4] = {0x75, 0x62, 0x69, 0x74};&lt;br /&gt; uint8_t addr_prefix[8] = {0x00, 0x01, 0xC3, 0xC4, 0xC5, 0xC6, 0xC7, 0xC8 };&lt;/p&gt;
&lt;p&gt;nrf_esb_config_t nrf_esb_config = NRF_ESB_DEFAULT_CONFIG;&lt;br /&gt; nrf_esb_config.protocol = NRF_ESB_PROTOCOL_ESB_DPL;&lt;br /&gt; nrf_esb_config.retransmit_delay = 600;&lt;br /&gt; nrf_esb_config.bitrate = NRF_ESB_BITRATE_1MBPS;&lt;br /&gt; nrf_esb_config.event_handler = nrf_esb_event_handler;&lt;br /&gt; nrf_esb_config.mode = NRF_ESB_MODE_PTX;&lt;br /&gt; nrf_esb_config.selective_auto_ack = false;&lt;/p&gt;
&lt;p&gt;err_code = nrf_esb_init(&amp;amp;nrf_esb_config);&lt;/p&gt;
&lt;p&gt;err_code = nrf_esb_set_base_address_0(base_addr_0);&lt;br /&gt; VERIFY_SUCCESS(err_code);&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;But it not work, microbit not recive.&lt;/p&gt;
&lt;p&gt;Microbit cfg group 0.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;div id="eJOY__extension_root"&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: micro:bit became unable to talk to nrf52832 by RADIO</title><link>https://devzone.nordicsemi.com/thread/202472?ContentTypeID=1</link><pubDate>Mon, 05 Aug 2019 14:53:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fdb69c80-b257-468b-bc40-1df6e414c293</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see the same issue as you describe. The radio &lt;span&gt;peripheral&amp;nbsp;&lt;/span&gt;configuration does not seem to have changed, so there might be something with the payload in the new editor version that makes the&amp;nbsp;gazell lib to not report the received packet.&amp;nbsp;Further debugging could be to setup a radio&amp;nbsp;peripheral example, and check if you are able to receive the packet, and check any differences in the payload.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>