<?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>Sleep mode with FreeRTOS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47088/sleep-mode-with-freertos</link><description>Hello, 
 I am using NRF52832 and nRF5_SDK_15.2.0 for the our device. 
 I am using FreeRTOS also. 
 
 I have some issue about sleep mode with FreeRTOS. 
 I refer to some suggestion such as Link 1 . So, I applied those kind code to handle FPU interrupt</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 May 2019 18:42:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47088/sleep-mode-with-freertos" /><item><title>RE: Sleep mode with FreeRTOS</title><link>https://devzone.nordicsemi.com/thread/186263?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 18:42:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b6133b24-e296-4963-b4c9-66fd229bfbdd</guid><dc:creator>Chongchun Moon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp;I found one way to resolve this issue. After adding FPU IRQ handler(&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/39681/handle-fpu-irq-with-freertos-and-sdk-14-2-0"&gt;Link&lt;/a&gt;), It looks that sleep current and BLE connection is okay.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Thanks for supporting.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sleep mode with FreeRTOS</title><link>https://devzone.nordicsemi.com/thread/186230?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 14:13:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4670a5b2-7cc8-4ac5-b091-f8ac7284fb5c</guid><dc:creator>Chongchun Moon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Thank you for respond.&lt;/p&gt;
&lt;p&gt;&amp;nbsp; How do I increase the size of the task sizes?&amp;nbsp; or&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Do you mean increase size of stack size when task is created?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; If so,&amp;nbsp; I tried to increase stack size of task as below, but it looks like situation is same.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&lt;pre class="ui-code" data-mode="text"&gt; BaseType_t xReturned = xTaskCreate(softdevice_task,
                                       &amp;quot;BLE&amp;quot;,
                                       NRF_BLE_FREERTOS_SDH_TASK_STACK+400,
                                       p_context,
                                       2,
                                       &amp;amp;m_softdevice_task);&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;By the way, Is the way I modified code in&amp;nbsp;port_cmsis_systick.c&amp;nbsp; okay to handle unwanted FPU interrupt when device goes to sleep?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Chongchun Moon&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Sleep mode with FreeRTOS</title><link>https://devzone.nordicsemi.com/thread/186145?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 10:48:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5728401-ee7c-4962-92cc-e9e7dfa8da32</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Seems like the task TCB is corrupted. this could happen if the task restore from the scheduler happened with a corrupted stack data. Can you increase the sizes of the task sizes (when task is created) to see if that helps? For some reason FPU interrupt that you are not handling in the application, could be triggered too many times pre-empting the BLE task and causing stack overflow.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Just a theory, but worth a shot to try.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>