<?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>nRF-IEEE-802.15.4-radio-driver SDK for Thread and Zigbee</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/66989/nrf-ieee-802-15-4-radio-driver-sdk-for-thread-and-zigbee</link><description>Dear all, 
 I would like to implement the IEEE 802.15.4 stack, using the driver inside the SDK for Thread and Zigbee. Unfortunately there aren&amp;#39;t any examples ad so everything is way more difficult. I would like to ask you some things about implementation</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Oct 2020 08:40:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/66989/nrf-ieee-802-15-4-radio-driver-sdk-for-thread-and-zigbee" /><item><title>RE: nRF-IEEE-802.15.4-radio-driver SDK for Thread and Zigbee</title><link>https://devzone.nordicsemi.com/thread/274515?ContentTypeID=1</link><pubDate>Tue, 13 Oct 2020 08:40:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41cf30ea-c165-4eec-8973-b64e6fa690b1</guid><dc:creator>Elia_pell</dc:creator><description>&lt;p&gt;Dear&amp;nbsp;J&amp;oslash;rgen,&lt;/p&gt;
&lt;p&gt;Thank you very much for the answer, in few lines you blow away a lot of doubts!&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Elia&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF-IEEE-802.15.4-radio-driver SDK for Thread and Zigbee</title><link>https://devzone.nordicsemi.com/thread/274375?ContentTypeID=1</link><pubDate>Mon, 12 Oct 2020 14:26:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:020fcae6-874d-48c2-ba61-9f74933455e0</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;SWI stands for Software Interrupts, and will trigger an interrupt handler in the application if enabled. The interrupt handler can process the events, or call additional handlers/schedulers.&lt;/li&gt;
&lt;li&gt;SWI it typically used in operations with a Softdevice (BLE stack). The softdevice is an external application, provided as a precompiled hex-file. Communication with the softdevice happens through Supervisor calls and SWI. The softdevice cannot trigger handlers inside the application/radio driver, but it can trigger an interrupt in the application through SWI. If you are not using a softdevice, the radio driver, which is compiled along with the application, can call handlers directly in the application without the need to go through SWI. See the radio driver documentation for &lt;a href="https://infocenter.nordicsemi.com/topic/15.4_radio_driver_v1.8.0/rd_source_files.html#rd_source_files_arbiter"&gt;which files to include for the various radio arbiters&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;I did create some &lt;a href="https://github.com/jorhol/nRF-Radio-802.15.4-Projects/"&gt;example projects&lt;/a&gt; for an older version of the driver, but they do not provide support for the softdevice arbiter. Should be simple to update to the latest version, but I have not tested this.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>