<?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>nrf52DK runs in rtos, thread will not be back to ready state after sleep()</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/48181/nrf52dk-runs-in-rtos-thread-will-not-be-back-to-ready-state-after-sleep</link><description>Hi, 
 I meet a problem: 
 nrf52DK runs a rtos similar with nuttx. The debug environment is ubuntu 16.04; the debug log is printed via minicom. 
 When the JLinkExe is not opened, thread will not be back to ready state after sleep(). 
 But after JLinkExe</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Jun 2019 06:52:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/48181/nrf52dk-runs-in-rtos-thread-will-not-be-back-to-ready-state-after-sleep" /><item><title>RE: nrf52DK runs in rtos, thread will not be back to ready state after sleep()</title><link>https://devzone.nordicsemi.com/thread/191774?ContentTypeID=1</link><pubDate>Mon, 10 Jun 2019 06:52:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef3f5b67-2c4d-4a8b-9981-77e2c32694f5</guid><dc:creator>glb1013</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Many thanks for your advice.&lt;/p&gt;
&lt;p&gt;And we found it, in the idle task, the wfi is called, so it goes to sleep when the idle task is running.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;glb1013&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52DK runs in rtos, thread will not be back to ready state after sleep()</title><link>https://devzone.nordicsemi.com/thread/191059?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 11:24:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e48c951f-e4aa-46ed-bbba-34094005fe2b</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi glb1013,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;we do not support other RTOSes than FreeRTOS in our nRF5 SDK, so if this is a third-party port then it is hard for us to say what the issue may be.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;However, by connecting with jlink.exe you are turning on the debugger on the nRF52 DK as well as the DAP on the NRF52. This will for instance cause the HFCLK clock source to always be active etc, so this is something that you can look into.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bj&amp;oslash;rn&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>