<?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>BLE STACK INIT AND BLE EVENT  HANDLER REGISTRATION</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41632/ble-stack-init-and-ble-event-handler-registration</link><description>when we pass the BLE event handler as a function argument to BLE stack init function and register the function results in a deadlock mechanism. Is that we cant able to register the event handler function by passing as an argument to stack init</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Dec 2018 09:38:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41632/ble-stack-init-and-ble-event-handler-registration" /><item><title>RE: BLE STACK INIT AND BLE EVENT  HANDLER REGISTRATION</title><link>https://devzone.nordicsemi.com/thread/162448?ContentTypeID=1</link><pubDate>Wed, 19 Dec 2018 09:38:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb3d4ce7-a5da-40ff-b23d-4163f34833f7</guid><dc:creator>SatzTechGeek</dc:creator><description>&lt;p&gt;&lt;span&gt;Thanks for the clarification! I will check&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE STACK INIT AND BLE EVENT  HANDLER REGISTRATION</title><link>https://devzone.nordicsemi.com/thread/162319?ContentTypeID=1</link><pubDate>Tue, 18 Dec 2018 14:50:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f20e9461-5eaf-4647-96aa-21c1504cab1b</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Does the function pointer&amp;nbsp;Ble_Core_ble_event correspond to its placement in the map file? Do you jump to the correct location in memory when a SD event occur? Maybe the pointer modified somehow?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE STACK INIT AND BLE EVENT  HANDLER REGISTRATION</title><link>https://devzone.nordicsemi.com/thread/162266?ContentTypeID=1</link><pubDate>Tue, 18 Dec 2018 11:52:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8468500-4b37-4aa6-bb79-a0d3423186f3</guid><dc:creator>SatzTechGeek</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am using Nordic SDK 15.2&amp;nbsp; and develop my application using c++ as a rogramming language&amp;nbsp;&lt;pre class="ui-code" data-mode="text"&gt;In mainFile.Cpp 
        
		Ble_Core_ble_event(ble_evt_t const * p_ble_evt, void * p_context ){
		   instance-&amp;gt;on_ble_Event(ble_evt_t const * p_ble_evt, void * p_context)
		}
		
        ble_stack_init(Ble_Core_ble_event);
		
		
In BleConfigFile.cpp
        ble_stack_init(Ble_Core_ble_event) {
            NRF_SDH_BLE_OBSERVER(m_ble_observer, APP_BLE_OBSERVER_PRIO, BleCore_onBleEvent, NULL);
		}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When I register member function as event handler function results in a system hang up (not a hard fault error) even though the events are getting triggered from&amp;nbsp;nrf_sdh_ble_evts_poll and&amp;nbsp;nrf_sdh_evts_poll&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE STACK INIT AND BLE EVENT  HANDLER REGISTRATION</title><link>https://devzone.nordicsemi.com/thread/162067?ContentTypeID=1</link><pubDate>Mon, 17 Dec 2018 12:33:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f70db32a-0afe-44c1-b344-83a0f1a40f12</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;could state which SDK version and SoftDevice version you are using? Also, please attach the code snippet where you set the event handler function pointer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It could sound like the event handler function pointer is set to a Null pointer. This will lead to a Hardfault and the device will reset.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>