<?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>Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13367/tickless-overrun-issue-using-freertos-nrf52</link><description>Question about usage. I am using the nRF52, and ported product code that was running on the Alpha SDK11 to the release SDK11. I believe that what I will describe is a new issue, after the port, but I have not yet fully investigated the reverted build</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 May 2016 13:01:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13367/tickless-overrun-issue-using-freertos-nrf52" /><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50979?ContentTypeID=1</link><pubDate>Fri, 20 May 2016 13:01:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e719bb43-e33a-4cb8-a43f-dd06924331c6</guid><dc:creator>Anders Strand</dc:creator><description>&lt;p&gt;This is now a know bug, see &lt;a href="https://devzone.nordicsemi.com/question/80413/freertos-tick-issue-can-lead-to-lockups-sdk11/"&gt;this&lt;/a&gt; thread.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50978?ContentTypeID=1</link><pubDate>Mon, 25 Apr 2016 19:30:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7dee988-bad4-4063-81ee-b48d1562a285</guid><dc:creator>Michael Dierks</dc:creator><description>&lt;p&gt;I have looked at the example, I see that I am using the _cmsis version of the port.  I don&amp;#39;t see those in the FreeRTOS distribution, so I will track down when they enter the Nordic SDK.  The port_cmsis_systick.c has specific code focused on dealing with TICKLESS and the use of RTC1 as the tick interrupt source.  This file contains elements of low_power_tick_management_RTCC.c that you pointed to,  plus some other changes.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50977?ContentTypeID=1</link><pubDate>Mon, 25 Apr 2016 13:32:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c7fa9ad-15c4-4afb-9a6e-f4a4b2b584d0</guid><dc:creator>www.FreeRTOS.org</dc:creator><description>&lt;p&gt;&lt;a href="https://sourceforge.net/p/freertos/code/HEAD/tree/trunk/FreeRTOS/Demo/CORTEX_EFM32_Pearl_Gecko_Simplicity_Studio/Low_Power_Demo/low_power_tick_management_RTCC.c"&gt;Here&lt;/a&gt; is an example of an implementation that uses a slow (32K) up counting peripheral that you can use as a template.  There are others in the download.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50976?ContentTypeID=1</link><pubDate>Mon, 25 Apr 2016 13:25:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c3ceb3c5-3d3c-49ac-ab39-e8bb3178caf6</guid><dc:creator>Michael Dierks</dc:creator><description>&lt;p&gt;I am using the selection macros in the latest FreeRTOS port in the SDK 11.  It configures the xSysTick to run from RTC1 interrupt, configured as a up-counting real-time counter, using the 32K external crystal as input.  It is configured to count 1ms systick intervals, so approx 31 counts per systick.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50975?ContentTypeID=1</link><pubDate>Mon, 25 Apr 2016 07:31:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd78c728-a7ec-47af-9501-98643e88137c</guid><dc:creator>www.FreeRTOS.org</dc:creator><description>&lt;p&gt;Is RTC1 an up counter or a down counter?  We have part specific examples for both types where the clock is 32K.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50974?ContentTypeID=1</link><pubDate>Mon, 25 Apr 2016 03:51:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0161a91f-efb2-49b9-ba1d-2a78b83b5717</guid><dc:creator>Michael Dierks</dc:creator><description>&lt;p&gt;Long weekend.  I am running the SysTick from the RTC1 on the 32K XTAL.  I am looking for very low power draw, which we have mostly.&lt;/p&gt;
&lt;p&gt;I did review the link you provided, I could not access the low-power file included in the last few responses from &amp;quot;rtel&amp;quot; on that thread.    I have seen some other posts on tickless and 32K operation.  I will review those more.  Suppose I will need a more complex trap on where I might be going when the clock tick values get separated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tickless overrun issue using FreeRTOS, nRF52</title><link>https://devzone.nordicsemi.com/thread/50973?ContentTypeID=1</link><pubDate>Thu, 21 Apr 2016 08:32:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e99b029e-ca9f-4a88-8fb4-362331a805eb</guid><dc:creator>www.FreeRTOS.org</dc:creator><description>&lt;p&gt;What is the frequency of the clock feeding the SysTick counter?  There was somebody that had an issue when it was &lt;a href="http://www.freertos.org/FreeRTOS_Support_Forum_Archive/February_2015/freertos_Where_to_put_WFI_in_FreeRTOS_e717bb2fj.html"&gt;slowed right down to 32K&lt;/a&gt; (search for 2016 in the thread to find the start of the relevant part) - but they never reported back with the conclusion - in the thread there is also a link to a source file that shows how very slow clocks can be used, if that is indeed how your system is configured (very unusual).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>