<?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>Timeslot request leads to HardFault</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55400/timeslot-request-leads-to-hardfault</link><description>Hello Community, 
 I want to request a timeslot with sd_radio_session_open(). Whenever i call this API function, the Application crashes with a HardFault. 
 I have no idea what is causing this issue. Any ideas?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Dec 2019 11:14:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55400/timeslot-request-leads-to-hardfault" /><item><title>RE: Timeslot request leads to HardFault</title><link>https://devzone.nordicsemi.com/thread/224391?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2019 11:14:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75358ad3-5974-477d-96f7-9c94beb13fb4</guid><dc:creator>sewes</dc:creator><description>&lt;p&gt;Ups...You&amp;#39;re right. I missed this fact.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you very much :-)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Problem solved!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Timeslot request leads to HardFault</title><link>https://devzone.nordicsemi.com/thread/224381?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2019 10:55:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:996399aa-946e-4d4a-acc4-0e7861f817e8</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;you cannot call any sd_xxx related calls from the interrupt context which are higher in priority than the SVC call.&lt;/p&gt;
&lt;p&gt;As you can see &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsds_s132%2FSDS%2Fs1xx%2Fprocessor_avail_interrupt_latency%2Fexception_mgmt_sd.html&amp;amp;cp=4_5_2_0_15_1"&gt;here&lt;/a&gt;&amp;nbsp;that SVC interrupt priority on nRF52832 is set to 4. And if your interrupt handler from where you are calling sd_xxx function has a priority higher (lower in actual number = higher priority on ARM core) then it would generate a hardfault.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>