<?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>Evaluation of nRF528xx 802.15.4 capabilities</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/83104/evaluation-of-nrf528xx-802-15-4-capabilities</link><description>Hi, 
 we&amp;#39;re performing an evaluation of using an nRF528xx module with 802.15.4 stack to replace a 3rd-party radio module. There will need to be an AT command protocol for device control eventually, but at this point I just want to get a basic UART passthrough</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Dec 2021 14:13:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/83104/evaluation-of-nrf528xx-802-15-4-capabilities" /><item><title>RE: Evaluation of nRF528xx 802.15.4 capabilities</title><link>https://devzone.nordicsemi.com/thread/345118?ContentTypeID=1</link><pubDate>Mon, 27 Dec 2021 14:13:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fccc3e98-57c2-46b1-b7eb-d5cadeaf1188</guid><dc:creator>Marte Myrvold</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Due to holidays we are short staffed, so please expect increased response time.&lt;/p&gt;
&lt;p&gt;First of all, the changes you make in&amp;nbsp;&lt;span&gt;rf_init() will be overwritten by other parts of the code, such as the channel being set by the default channel mask&amp;nbsp;PTT_CHANNEL_MASK in Kconfig. Because of this, the channel will still be set to 11.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When using&amp;nbsp;nrf_802154_transmit_raw() to transmit a packet, the first byte of the pointer to the data to transmit must contain the frame length, so you cannot give output directly as a parameter in the function. Instead you should use something&lt;/span&gt;&lt;span&gt; like this:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;temp_tx_pkt[0] = len + RF_FCS_SIZE;
memcpy(&amp;amp;temp_tx_pkt[RF_PSDU_START], output, len);
ret = nrf_802154_transmit_raw(temp_tx_pkt, NULL);&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Where len is the length of the data, and RF_FCS_SIZE and&amp;nbsp;RF_PSDU_START are already defined in rf_proc.c in the example. It is a good idea to check what&amp;nbsp;nrf_802154_transmit_raw returns, to see if the driver could schedule the transmission or not.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I would also recommend removing everything regarding the comm module in the sample, as you do not need that for what you are doing. Additionally, if you have an additional nRF52840 DK or dongle, I recommend setting up a&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/ug_sniffer_802154/UG/sniffer_802154/intro_802154.html"&gt;nRF Sniffer for 802.15.4&lt;/a&gt;&amp;nbsp;to see the network traffic.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Marte&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>