<?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>Ozone debugger causes hardfault</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/103904/ozone-debugger-causes-hardfault</link><description>I have a rather big application on a nRF52840 under Zephyr 2.4.0 that needs debugging. When starting the Ozone debugger, I can load and run the program as expected. I can see the output in the terminal, all seems to be ok. But when I set a breakpoint</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Sep 2023 18:39:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/103904/ozone-debugger-causes-hardfault" /><item><title>RE: Ozone debugger causes hardfault</title><link>https://devzone.nordicsemi.com/thread/446953?ContentTypeID=1</link><pubDate>Wed, 20 Sep 2023 18:39:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:80c2c107-79e5-4b66-8554-3c5c99ab9b49</guid><dc:creator>Sigurd</dc:creator><description>[quote user="BvdP4Celsius"]Is your answer relevant for Zephyr OS also? You mentioned &amp;#39;Softdevice&amp;#39;, however under Zephyr I don&amp;#39;t use the softdevice (right?)[/quote]
&lt;p&gt;Yes, in nRF Connect SDK&amp;#39;s case, it will be the SoftDevice Controller. If you pause the CPU, so that BLE real-time&amp;nbsp;&lt;span&gt;requirements are not meet, you wil get a MPSL assert and then a hardfault in the log. Example:&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1695235072710v1.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Ozone debugger causes hardfault</title><link>https://devzone.nordicsemi.com/thread/446764?ContentTypeID=1</link><pubDate>Wed, 20 Sep 2023 06:32:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1c3ee7b-5196-4925-906a-9781b108a7d1</guid><dc:creator>BvdP4Celsius</dc:creator><description>&lt;p&gt;Hi Sigurd,&lt;/p&gt;
&lt;p&gt;Is your answer relevant for Zephyr OS also? You mentioned &amp;#39;Softdevice&amp;#39;, however under Zephyr I don&amp;#39;t use the softdevice (right?)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Ozone debugger causes hardfault</title><link>https://devzone.nordicsemi.com/thread/446668?ContentTypeID=1</link><pubDate>Tue, 19 Sep 2023 12:59:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46a515c3-e6c4-46ff-81d2-056596fa6d45</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi,&lt;br /&gt;If you are&amp;nbsp;halting the CPU using breakpoints,&amp;nbsp;while the SoftDevice is active, then it will assert, since it needs the CPU to meet it&amp;#39;s real-time requirements, and it will detect that it was not able to process interrupts and events in time if the CPU is halted, and it will then assert.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>