<?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>Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/80515/integrating-ble-service-into-an-rtos-application</link><description>I have an RTOS application into which I integrated a custom BLE service code. Question is, there isn&amp;#39;t any need for a separate thread for handling BLE stuff? I see BLE events still fire off fine though not sure how that affects the thread execution. Also</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 28 Oct 2021 08:25:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/80515/integrating-ble-service-into-an-rtos-application" /><item><title>RE: Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/thread/336351?ContentTypeID=1</link><pubDate>Thu, 28 Oct 2021 08:25:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:534f68b7-a790-4e44-a4d6-c570abf1db8f</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;In the nRF connect app you will see the attribute value beeing updated. You could try one of the SDk examples. i.e. heart rate service, then eneble notifications for this to see how the value is updated in the nRF connect app. The value will simply be sent to the peer in the first possible connection event. Then you should see it update in nRF connect app.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/thread/335590?ContentTypeID=1</link><pubDate>Sun, 24 Oct 2021 15:53:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a5bab4a-cbb9-4abb-95c5-2383cb9d9831</guid><dc:creator>morpho</dc:creator><description>&lt;p&gt;i understand the part about updating the attribute value but&amp;nbsp;not quite about&amp;nbsp;the notification. How does it appear in the nRF Connect app?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/thread/335157?ContentTypeID=1</link><pubDate>Wed, 20 Oct 2021 20:27:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4b95e67-ebd7-4446-94b3-bb50e84ab5c9</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;To change between the models you need to choose a different &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/group__nrf__sdh__config.html#ga8c62266e692470ae085da5cd4e995a81"&gt;NRF_SDH_DISPATCH_MODEL&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;sd_ble_gatts_hvx is used to update the attribute value and send a notification/indication to the peer device.For the notification to be sent to the peer the peer will first have to enable notifications by writing to the CCCD of the characteristic.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/thread/333620?ContentTypeID=1</link><pubDate>Tue, 12 Oct 2021 05:47:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7fe29b1-fb78-43e7-b943-7de54b3a4e72</guid><dc:creator>morpho</dc:creator><description>&lt;p&gt;Thanks. Where&amp;#39;s the configuration to switch between interrupt driven and thread mode located?&lt;/p&gt;
&lt;p&gt;Also, is&amp;nbsp;&lt;strong&gt;sd_ble_gatts_hvx&lt;/strong&gt; used to set the attribute of the said characteristic? Once done, the new value shall be reflected in the nRF Connect app? I see it&amp;#39;s invoked in&amp;nbsp;&lt;strong&gt;ble_hrs_heart_rate_measurement_send()&lt;/strong&gt; which is called when the timer expires&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Integrating BLE service into an RTOS application</title><link>https://devzone.nordicsemi.com/thread/333492?ContentTypeID=1</link><pubDate>Mon, 11 Oct 2021 12:00:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aeb2046d-fe64-42bd-88b4-a5240c3138a4</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have two ways of retrieving events from the SD, &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s140.api.v7.3.0/group___b_l_e___c_o_m_m_o_n___i_r_q___e_v_t___m_s_c.html"&gt;Interrupt-driven Event Retrieval&lt;/a&gt; and &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s140.api.v7.3.0/group___b_l_e___c_o_m_m_o_n___t_h_r_e_a_d___e_v_t___m_s_c.html"&gt;Thread Mode Event Retrieval&lt;/a&gt;. We have the &lt;span&gt;&lt;a title="SoftDevice Handler library" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_softdevice_handler.html?cp=8_1_3_48"&gt;SoftDevice Handler library&lt;/a&gt;&lt;/span&gt; to handle this, but which is used depends on you configuration. Note that we have an example in the SDK that could be helpfull: &lt;span&gt;&lt;a title="Heart Rate Application with FreeRTOS" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/ble_sdk_app_hrs_freertos.html?cp=8_1_4_2_2_14"&gt;Heart Rate Application with FreeRTOS&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Also note some background information on the Softdevice: &lt;span&gt;&lt;a title="Interrupt model and processor availability" href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/processor_avail_interrupt_latency/processor_avail_interrupt_latency.html?cp=4_7_4_0_15"&gt;Interrupt model and processor availability&lt;/a&gt;&lt;/span&gt; and &lt;span&gt;&lt;a title="System on Chip resource requirements" href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/sd_resource_reqs/sd_resource_reqs.html?cp=4_7_4_0_6"&gt;System on Chip resource requirements&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>