<?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>Looped service discovery causes HardFault</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46160/looped-service-discovery-causes-hardfault</link><description>There is bug in SDK 15.3 in the way the DB discovery procedure handles SoftDevice busy state. In the discovery_start() function the code checks return code from sd_ble_gattc_primary_services_discover(). If it is NRF_ERROR_BUSY then it sets p_db_discovery</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Apr 2019 12:15:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46160/looped-service-discovery-causes-hardfault" /><item><title>RE: Looped service discovery causes HardFault</title><link>https://devzone.nordicsemi.com/thread/182383?ContentTypeID=1</link><pubDate>Tue, 16 Apr 2019 12:15:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f3ec55d-9f51-4225-bcd6-117f62ea0a1b</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for reporting. I have created an internal bug report so that it can be fixed in a future nRF5 SDK release.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>