<?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>802.15.4 stack unusable due to immediate crashes stemming from unsound swi usage in driver code</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127840/802-15-4-stack-unusable-due-to-immediate-crashes-stemming-from-unsound-swi-usage-in-driver-code</link><description>In theory all driver calls are suspect, but for example I see crashes in nrf_802154_buffer_free_raw, at this assert: 
 
 This is easily reproducible by running 802154_phy_test example on nrf52840. It crashes less an a second after startup. I also tried</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Apr 2026 21:23:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127840/802-15-4-stack-unusable-due-to-immediate-crashes-stemming-from-unsound-swi-usage-in-driver-code" /><item><title>RE: 802.15.4 stack unusable due to immediate crashes stemming from unsound swi usage in driver code</title><link>https://devzone.nordicsemi.com/thread/565267?ContentTypeID=1</link><pubDate>Tue, 21 Apr 2026 21:23:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9abe0b28-a01d-40ea-b450-bfd12167862d</guid><dc:creator>Andrew0123</dc:creator><description>&lt;p&gt;I tried ncs v3.0.2 and the issue was there too. I&amp;#39;ve not tried 2.x versions.&lt;/p&gt;
&lt;p&gt;There&amp;#39;s nothing special about the sample, openthread samples (I tried coap_server) are also broken in the same way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 802.15.4 stack unusable due to immediate crashes stemming from unsound swi usage in driver code</title><link>https://devzone.nordicsemi.com/thread/565228?ContentTypeID=1</link><pubDate>Tue, 21 Apr 2026 11:04:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ffa5fb04-731e-4c02-b9d3-d3b1160e0e40</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;I am not that familiar with the sample, but I believe I am seeing the same thing now. Did you happen to recently switch to&amp;nbsp;ncs v3.2.4 from an NCS version in which this did not occur?&lt;/p&gt;
&lt;p&gt;Regards.&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 802.15.4 stack unusable due to immediate crashes stemming from unsound swi usage in driver code</title><link>https://devzone.nordicsemi.com/thread/565188?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2026 15:39:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:422daab4-4375-4607-9830-152176e7fc80</guid><dc:creator>Andrew0123</dc:creator><description>&lt;p&gt;Default 802154_phy_test example in ncs v3.2.4&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 802.15.4 stack unusable due to immediate crashes stemming from unsound swi usage in driver code</title><link>https://devzone.nordicsemi.com/thread/565176?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2026 13:32:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:353d9c60-a270-4ebb-964f-087fcbb23fdd</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is this with a default&amp;nbsp;&lt;span&gt;802154_phy_test&amp;nbsp;example?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Or are you, like in the case you linked to, not able to see this problem with default samples, but only when&amp;nbsp;migrating&amp;nbsp;an older project accross NCS versions? If so, what did you move it from?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>