<?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>Do callbacks, interrupts, event handling, and main loops belong to the same context?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111284/do-callbacks-interrupts-event-handling-and-main-loops-belong-to-the-same-context</link><description>Hello, the chip I am currently using is nrf52832 and the SDK version is SDK15.0. May I ask if all callbacks, interrupts, event handling, and main loops belong to the same context? If they do, is there any documentation to explain them? If not, what should</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 22 May 2024 06:20:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111284/do-callbacks-interrupts-event-handling-and-main-loops-belong-to-the-same-context" /><item><title>RE: Do callbacks, interrupts, event handling, and main loops belong to the same context?</title><link>https://devzone.nordicsemi.com/thread/485279?ContentTypeID=1</link><pubDate>Wed, 22 May 2024 06:20:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9a793b9-7c47-4ba7-9be0-21e1e44f32c2</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Could you please tell us why you are using very very old SDK for prototyping for your new products? I strongly suggest you to use latest &lt;a href="https://www.nordicsemi.com/Products/Development-software/nRF-Connect-SDK"&gt;nRF Connect SDK&lt;/a&gt;. nRF5SDK is deprecated and no new features will be added in that.&lt;/p&gt;
&lt;p&gt;If you still want to use this old SDK, then here is the answer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- Main - Read &lt;a href="https://medium.com/@raihann.eu/thread-mode-and-handler-mode-in-arm-6e3c6ff4d7ca#:~:text=Thread%20mode%20also%20called%20as,advancing%20through%20the%20program%20flow."&gt;this &lt;/a&gt;external Thread mode explanation. Main function runs in main thread mode.&lt;/p&gt;
&lt;p&gt;- All other contexts run in their own handler mode (interrupt handler mode or exception mode)&lt;/p&gt;
&lt;p&gt;Documentation for this nRF5SDKv15 can be found &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Findex.html&amp;amp;cp=9_5_4"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you are not using BLE stack (Softdevice) then read ARM Cortex M4 technical reference manual for more details.&lt;/p&gt;
&lt;p&gt;If you are using BLE stack (softdevice) for your application, you can also read the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsds_s132%2FSDS%2Fs1xx%2Fprocessor_avail_interrupt_latency%2Fprocessor_avail_interrupt_latency.html&amp;amp;cp=5_7_3_0_15"&gt;Interrupt model and processor availability&lt;/a&gt; info.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>