<?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>Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21717/restart-ble-stack-causes-chip-reset</link><description>Hi everybody, 
 I&amp;#39;m trying to hide some characteristics till the user write the right value to a secure pin characteristic the devise exposes at the beginning.
I already did it but, when the user disconnects his device and repeat the pairing procedure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 04 May 2017 07:05:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21717/restart-ble-stack-causes-chip-reset" /><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85310?ContentTypeID=1</link><pubDate>Thu, 04 May 2017 07:05:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16ac3d76-a1b1-4543-a32b-6778b060ab80</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;I converted your comment to an answer, and accepted it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85309?ContentTypeID=1</link><pubDate>Wed, 03 May 2017 15:40:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06b166ff-e186-4e22-aace-cfc4d1f87547</guid><dc:creator>Massimo Pilia</dc:creator><description>&lt;p&gt;Yes it is.
Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85308?ContentTypeID=1</link><pubDate>Wed, 03 May 2017 14:55:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0f060fac-b400-4fa9-87bc-939c0dbb65d1</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Great! So is everything is okay now?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85307?ContentTypeID=1</link><pubDate>Wed, 03 May 2017 14:54:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8afe3fe2-0764-4683-9557-5e9c6d546bde</guid><dc:creator>Massimo Pilia</dc:creator><description>&lt;p&gt;Yes, &lt;code&gt;softdevice_handler_init&lt;/code&gt; called inside the macro &lt;code&gt;SOFTDEVICE_HANDLER_INIT&lt;/code&gt;. Anyway, I discovered the problem wasn&amp;#39;t the handler. The proper error code was &lt;code&gt;NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION&lt;/code&gt; (0x1001) that comes up because I had set the adc IRQ priority level too high (0). To discover it I had to disable all the IRQs and than enable them once a time. Finally, when I founded the issue was caused by the adc module, I set its IRQ priority to &lt;code&gt;APP_IRQ_PRIORITY_LOW&lt;/code&gt; (3) and everything starts to work fine!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85306?ContentTypeID=1</link><pubDate>Wed, 03 May 2017 13:29:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fbd36bb-a8c3-462d-84d5-502f7a370af9</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Do you mean softdevice_handler_init()? So 0x0001 is returned? Could you go inside it and see which function that returns NRF_ERROR_SVC_HANDLER_MISSING? What SoftDevice version are you using?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85305?ContentTypeID=1</link><pubDate>Tue, 02 May 2017 15:20:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e852845-4fe5-4bb1-8212-d169072f8f0f</guid><dc:creator>Massimo Pilia</dc:creator><description>&lt;p&gt;Actually I do need to remove some characteristics when the user disconnects from the device and add them again only when the user provides a correct pin number in the unique visible characteristic.
Debugging the code I discover that the problem is in the &lt;code&gt;ble_stack_init()&lt;/code&gt; where, internally, the &lt;code&gt;SOFTDEVICE_HANDLER_INIT(&amp;amp;clock_lf_cfg, NULL)&lt;/code&gt; return this error: &lt;code&gt;NRF_ERROR_SVC_HANDLER_MISSING&lt;/code&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Restart BLE stack causes chip reset</title><link>https://devzone.nordicsemi.com/thread/85304?ContentTypeID=1</link><pubDate>Tue, 02 May 2017 10:16:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf59b3fe-099a-4113-a4bc-b3bec0f00e3b</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;You are only adding services aren&amp;#39;t you? That shouldn&amp;#39;t be a problem, the post you refer to are about removing services. Anyways, what error code does sd_softdevice_disable() return?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>