<?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>Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/52201/facing-issues-with-multiple-interrupts</link><description>Dear all, 
 
 I am using the following peripherals in our product. 
 1. TWI Sensor 
 2. BLE 
 3. APP timer (1. to poll a gpio pin &amp;amp; as RTC) 
 4. SPI flash 
 5. 2 Edge sensitive GPIO pins. 
 6. 2 ADCs 
 Initially I need to wait for APP timer to create</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 24 Sep 2019 09:20:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/52201/facing-issues-with-multiple-interrupts" /><item><title>RE: Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/thread/211478?ContentTypeID=1</link><pubDate>Tue, 24 Sep 2019 09:20:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a92f3422-40fa-4e4c-b2b5-65dd8a73b984</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;You need to read&amp;nbsp;&lt;a title="Schedule handling library" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_scheduler.html?cp=5_1_3_38"&gt;Schedule handling library&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a title="Scheduler" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/group__app__scheduler.html?cp=5_1_6_11_39"&gt;Scheduler&lt;/a&gt;&amp;nbsp;API docs.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/thread/211017?ContentTypeID=1</link><pubDate>Fri, 20 Sep 2019 17:21:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:490e3a0d-d7ca-4ced-b12a-d4d48fcdebfd</guid><dc:creator>Kotteeswaran</dc:creator><description>&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is there any sample application codes available ?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I checked many a files which use app_scheduler.&lt;/p&gt;
&lt;p&gt;All the files calls &amp;quot; APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE);&amp;quot; and then calls &amp;quot;app_sched_execute();&amp;quot;.&lt;/p&gt;
&lt;p&gt;Is the above said things are sufficient or we need to do anything else.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;In my current approach, I am using the following priorities in addition to softdevice.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;1. App_timer (Soft RTC &amp;amp; Reads switch )&amp;nbsp; assigned priority 2&lt;/p&gt;
&lt;p&gt;2. SPI flash uses priority - 4&lt;/p&gt;
&lt;p&gt;3. Sensors (TWIM &amp;amp; GPIO interrupt) -- 2&lt;/p&gt;
&lt;p&gt;4. ADC -- priority - 3&lt;/p&gt;
&lt;p&gt;5. Clock is assigned priority - 6.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Will changing the interrupt levels help me?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thanks &amp;amp; regards,&lt;/p&gt;
&lt;p&gt;Kotteeswaran.E&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/thread/210524?ContentTypeID=1</link><pubDate>Wed, 18 Sep 2019 18:09:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fb10195-496e-40d3-9403-69a4a01652c1</guid><dc:creator>Kotteeswaran</dc:creator><description>&lt;p&gt;Thanks for prompt reply.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Let me try the scheduler approach.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/thread/210099?ContentTypeID=1</link><pubDate>Tue, 17 Sep 2019 11:52:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1caa83ca-3ff5-4253-81ff-662cb01d6ed3</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;You need to adhere to the SoftDevic specification&amp;#39;s&amp;nbsp;&lt;a title="Interrupt priority levels" href="https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/processor_avail_interrupt_latency/exception_mgmt_sd.html?cp=3_4_2_0_15_1"&gt;Interrupt priority levels&lt;/a&gt;.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I then suggest you use Priority 7 and use the app_scheduler to schedule your tasks, there you can set priorities for the individual tasks where they will still execute in priority 7.&lt;br /&gt;I believe the underlying HW drivers use prio 6, so that they can execute whatever they need to, when they need to. Use the HW driver&amp;#39;s callback function to schedule&amp;nbsp;your tasks.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Facing issues with multiple interrupts</title><link>https://devzone.nordicsemi.com/thread/209930?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2019 18:41:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13e27e5e-2415-4c91-8ab8-f39dc28e432b</guid><dc:creator>superpak</dc:creator><description>&lt;p&gt;If you don&amp;#39;t have very tight timing requirements, you could use the app_scheduler and schedule all your functions through the app_scheduler. You can even change the configuration of the app_timer library to schedule it&amp;#39;s callbacks through the app_scheduler.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>