<?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>Scheduler library examples</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63379/scheduler-library-examples</link><description>Hi, 
 I&amp;#39;m discovering documetation of the Scheduler library. So, as I understand the idea is to call function app_sched_event_put(...,some_func) from the interrupt/event handler and then passed some_func will be executed from the main. app_sched_execute</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Jul 2020 18:15:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63379/scheduler-library-examples" /><item><title>RE: Scheduler library examples</title><link>https://devzone.nordicsemi.com/thread/261451?ContentTypeID=1</link><pubDate>Thu, 23 Jul 2020 18:15:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d53363d4-03bd-4647-9bb2-ca2e225a833f</guid><dc:creator>Ars Morozov</dc:creator><description>&lt;p&gt;Thank you for the answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Scheduler library examples</title><link>https://devzone.nordicsemi.com/thread/259855?ContentTypeID=1</link><pubDate>Tue, 14 Jul 2020 09:25:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a761ec29-396c-4bd2-8375-76e54fc736a4</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;The difference between APPSH and INTERRUPT method is only that the SDH library will schedule a call to the SDH function that polls the events from the softdevice, when the softdevice interrupt happens, in the APPSH method, instead of calling it directly like it is done in the INTERRUPT method. The event/data pointers will be valid/received in the same way for both methods.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Scheduler library examples</title><link>https://devzone.nordicsemi.com/thread/258481?ContentTypeID=1</link><pubDate>Sun, 05 Jul 2020 20:51:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:05cadd48-9e0b-49a7-bace-7d70e30bde55</guid><dc:creator>Ars Morozov</dc:creator><description>&lt;p&gt;Also, one more question regarding Scheduler. If I set&amp;nbsp;NRF_SDH_DISPATCH_MODEL&amp;nbsp; 1, so is it correct that all BLE events will be passed to main context? If yes, what will be with data the pointer to which passed to the sheduled handlers? For example if I have BLE_GATTS_EVT_WRITE event I want to handle written data, thus I need a pointer to this data. In case if I receive normal interrupts, then I receive the pointer to the data, which are valid only while interrupt is handling. But if I receive this interrupt in the main context, what will be with this data? Where they will be stored and how long?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Scheduler library examples</title><link>https://devzone.nordicsemi.com/thread/258478?ContentTypeID=1</link><pubDate>Sun, 05 Jul 2020 20:30:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7583ace-59c8-46fe-97af-d4d46e8adf17</guid><dc:creator>Ars Morozov</dc:creator><description>&lt;p&gt;Thank you for this link, it&amp;#39;s usefull. Not good, that in the documentation there are no links to those tutorials.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Scheduler library examples</title><link>https://devzone.nordicsemi.com/thread/258476?ContentTypeID=1</link><pubDate>Sun, 05 Jul 2020 20:13:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:652a8dfc-7695-486a-9e22-5caadd525a46</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is a &lt;a href="https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/scheduler-tutorial"&gt;scheduler tutorial&lt;/a&gt; available here on DevZone.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sheduler library examples</title><link>https://devzone.nordicsemi.com/thread/258452?ContentTypeID=1</link><pubDate>Sun, 05 Jul 2020 09:00:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3a1a9ca-e94c-4fc6-a420-8443417613d7</guid><dc:creator>Ars Morozov</dc:creator><description>&lt;p&gt;It seems that usage of the Scheduler for App Timer Events in those examples it&amp;#39;s a demonstration of using Scheduler library. But it&amp;#39;s not clear when you looking on examples. Because you expect to see it in main.c or in other files in application folder. On my oppnion you should note it in &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.0.0%2Flib_scheduler.html"&gt;documentation &lt;/a&gt;on the Scheduler library, where you refer on examples HID Mouse Application and HID Keyboard Application. You should note that Scheduler used for handling App timer events in main context. It&amp;#39;s done by enabling&amp;nbsp;APP_TIMER_CONFIG_USE_SCHEDULER...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>