<?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>MPSL Assert 107,291 and 107,301</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122498/mpsl-assert-107-291-and-107-301</link><description>Hello, 
 I&amp;#39;m developing my custom sensor application. It&amp;#39;s a matter over thread device. Before final product I&amp;#39;m working on a NRF52840 DK PCA 100056 v3.0.1 and NCS 3.02. It has uart1 in async mode for a sensor and I2c for another sensor and a gpio input</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Jul 2025 13:15:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122498/mpsl-assert-107-291-and-107-301" /><item><title>RE: MPSL Assert 107,291 and 107,301</title><link>https://devzone.nordicsemi.com/thread/541042?ContentTypeID=1</link><pubDate>Tue, 01 Jul 2025 13:15:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:053520bf-c3c8-474f-9432-8e62fb7e2e23</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We tried to reproduce, but the uploaded files seem to be incomplete.&lt;/p&gt;
&lt;p&gt;Could you please share the full project with the building commands to build the project? If it&amp;#39;s sensitive, I can set this case private. Therefore, the project would only be shared with us.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the meantime, we investigated a bit:&lt;/p&gt;
&lt;p&gt;The reason for the&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;MPSL ASSERT: 107, 291&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;MPSL ASSERT: 107, 301&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Assertion failures can be a delay in handling the RTC0 interrupt. It looks strange, because this interrupt should work without any delays on the highest priority (hardware prio 0).&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You could check the following:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;CONFIG_ZERO_LATENCY_IRQS&lt;/code&gt; is set to &lt;code&gt;y&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;This can be checked in the &lt;code&gt;build/&amp;lt;app_name&amp;gt;/zephyr/.config&lt;/code&gt; file.&lt;/p&gt;
&lt;p&gt;If debugging, any breakpoint hit can cause a delay (CPU gets halted, but RTC is still running), so stepping through the code can also result in such behavior.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Could you also share the entire &lt;code&gt;.config&lt;/code&gt; as well as &lt;code&gt;zephyr.dts&lt;/code&gt; file under the build/&amp;lt;app_name&amp;gt;/zephyr/? Maybe some peripherals have been configured to IRQ Prio = 0?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MPSL Assert 107,291 and 107,301</title><link>https://devzone.nordicsemi.com/thread/540485?ContentTypeID=1</link><pubDate>Wed, 25 Jun 2025 13:05:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9bba4b18-149d-44ac-b45a-cf9cc09e8c4e</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for notifying us. The team is trying to reproduce to figure out what might cause this assertion. I will update later when I collect enough information. Please give us more time. Thanks.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;br /&gt;Amanda H.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>