<?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>pairing cancel cause reset on ble_cts_c</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6192/pairing-cancel-cause-reset-on-ble_cts_c</link><description>Hello, 
 I&amp;#39;m testing current time service client example on SDK 8.0.0 with iOS. 
 After connected the devices, iOS show confirmation to pairing.
When I canceled this or the request timeout, the application on nrf51 is reset (or called app_error_handler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Mar 2015 08:39:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6192/pairing-cancel-cause-reset-on-ble_cts_c" /><item><title>RE: pairing cancel cause reset on ble_cts_c</title><link>https://devzone.nordicsemi.com/thread/21681?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2015 08:39:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6c032f3-d97a-4e3c-bbb5-fb921a7d9dea</guid><dc:creator>H&amp;#229;vard</dc:creator><description>&lt;p&gt;Hello Kawajiri,
Thanks for reports on the CTS. (I already fixed the &amp;quot;adjust reason&amp;quot; bug.)
You are right, it would be better to go back to advertising more gracefully in case of timeout or cancelling. I will take it into consideration.&lt;/p&gt;
&lt;p&gt;-Håvard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pairing cancel cause reset on ble_cts_c</title><link>https://devzone.nordicsemi.com/thread/21680?ContentTypeID=1</link><pubDate>Tue, 24 Mar 2015 01:07:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b628e5ae-98c5-421e-a5f4-845557fefb0f</guid><dc:creator>R. Kawajiri</dc:creator><description>&lt;p&gt;I found a solution. It works with implementation that do nothing like below code.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;void app_error_handler(uint32_t error_code, uint32_t line_num, const uint8_t * p_file_name)  { }
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;However, I still have the question that this is right solution for release products? Or, is there better solution?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pairing cancel cause reset on ble_cts_c</title><link>https://devzone.nordicsemi.com/thread/21679?ContentTypeID=1</link><pubDate>Mon, 23 Mar 2015 09:57:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbec13c7-2447-43f9-8cca-f2ad3b64d20d</guid><dc:creator>R. Kawajiri</dc:creator><description>&lt;p&gt;I would like to CTS for calibrating timer for sensing. That is, the reseting is big issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pairing cancel cause reset on ble_cts_c</title><link>https://devzone.nordicsemi.com/thread/21678?ContentTypeID=1</link><pubDate>Mon, 23 Mar 2015 09:25:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:678f4541-3e7b-4a40-b148-9a628c33c4c2</guid><dc:creator>R. Kawajiri</dc:creator><description>&lt;p&gt;[confirm failed] &lt;a href="http://developer.nordicsemi.com/nRF51_SDK/nRF51_SDK_v8.x.x/doc/8.0.0/s110/html/a00893.html"&gt;developer.nordicsemi.com/.../a00893.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[timeout] &lt;a href="http://developer.nordicsemi.com/nRF51_SDK/nRF51_SDK_v8.x.x/doc/8.0.0/s110/html/a00895.html"&gt;developer.nordicsemi.com/.../a00895.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The messaging and events suppose to become like above. However, the assertion is called before the catching BLE_GAP_EVT_AUTH_STATUS on app code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>