<?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>Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22724/using-freertos-rtc-and-softdevice</link><description>Just a general resource question. The Softdevice uses RTC0, FreeRTOS (by coded default) uses RTC1. So in order for the SDK ble_conn_params.c to run properly I have to link app_timer_freertos.c to the Makefile. 
 This leaves RTC2 available for general</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 14 Jun 2017 07:24:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22724/using-freertos-rtc-and-softdevice" /><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89346?ContentTypeID=1</link><pubDate>Wed, 14 Jun 2017 07:24:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c864bfb-2b94-430b-b5c5-6860241b9f51</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Smells like a bug. After you have succesfully handled the SYS_ATTR_MISSING, try to send an HVX notification again and check if the it returns success and also check if the power consumption goes low.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89341?ContentTypeID=1</link><pubDate>Wed, 14 Jun 2017 00:26:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15d0bb04-cc02-4217-9010-2156900aac5e</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;I have noticed that if I send an HVX notification, if the Central has not subscribed to the characteristic then the system stays up consuming power and not able to go to sleep.  As soon as I enable notifications, the system goes back to proper idle sleep.&lt;/p&gt;
&lt;p&gt;Even after handling an unsubscribed notification error, this never caused high power consumption in previous SDKs.   	&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;if( err_code == BLE_ERROR_GATTS_SYS_ATTR_MISSING)
{
	err_code = sd_ble_gatts_sys_attr_set(p_myService-&amp;gt;conn_handle, NULL, 0, 0);
	APP_ERROR_CHECK(err_code);
}
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89344?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 20:51:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94aef332-d86f-441e-bee1-78df46afcf79</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;For some reason I found the thread priority changing to priority 6 instead of 2 (set to 2 when initialized).  Thus causing a condition where an interrupt was triggering another interrupt of high priority&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89343?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 20:49:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43f01ce6-5e02-4f63-bc86-1b8ba34f2a62</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;Symbol &amp;#39;RTC2_CC_NUM&amp;#39; could not be resolved	my_rtc.c&lt;/p&gt;
&lt;p&gt;Error shown on code line:  const nrf_drv_rtc_t rtc = NRF_DRV_RTC_INSTANCE(2); /**&amp;lt; Declaring an instance of nrf_drv_rtc for RTC2 */&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89339?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 18:58:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da70fd73-5a3c-4f3f-a2b5-a54346b23746</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;What exactly does Eclipse complain? Can you please post that message. Was it about the priorities you mentioned in other post that went away after installing new sdk?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89340?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 18:46:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92051a97-b844-4c6f-a85f-d0e377302557</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;I tried replacing this file.  Everything still works fine but Eclipse is still complaining about RTC2.  So far I haven&amp;#39;t had any issues today.   In regards to the thread you mentioned, the root cause was something change the Thread priority causing Cortex Thread faults.  Not sure how it happened but since I&amp;#39;ve re-installed SDK12.3.0 I have only seen this issue a couple times.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89345?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 09:42:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:403ee34f-b08b-466e-974e-715c2542763d</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I am quite confident that this is also related to the problem mentioned in &lt;a href="https://devzone.nordicsemi.com/question/149472/hardfault-on-an-sd_ble_gatts_hvx-call-in-sdk123/"&gt;this&lt;/a&gt; thread. The problem is that sdk 13 and sdk12.3 introduced a corner case in the freertos internal timers that could cause problems in features of RTOS dependent on RTOS timing.&lt;/p&gt;
&lt;p&gt;We should try to solve the compile errors you are getting when you are trying to patch the file mentioned in &lt;a href="https://devzone.nordicsemi.com/question/132346/freertos-rtc-issue-in-port_cmsis_systickc/?answer=133085#post-id-133085"&gt;this&lt;/a&gt; thread.&lt;/p&gt;
&lt;p&gt;Ideally, it should not have given any warning, which compiler are you using? Please post your errors when you try to use the patched file?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using FreeRTOS, RTC and Softdevice?</title><link>https://devzone.nordicsemi.com/thread/89342?ContentTypeID=1</link><pubDate>Mon, 12 Jun 2017 23:24:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9689a645-9224-4526-b1fb-f7b69f53e286</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;Also Eclipse always complains about this setup up with the error:&lt;/p&gt;
&lt;p&gt;Symbol &amp;#39;RTC2_CC_NUM&amp;#39; could not be resolved	my_rtc.c&lt;/p&gt;
&lt;p&gt;The console shows that it compiles fine, but just can&amp;#39;t get Eclipse to drop this error.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>