<?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>Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27587/why-52dk-10056-reset-when-i-connected-the-nrfuart-app</link><description>Hi,
I add the NUS in the ble_app_hids_mouse example which the sdk version is 14.0.
There are four services in the project: dis, bas, hids and nus.
When I connceted the 52DK from the nrfUART app, a reset ocurred while I pushing a button to
send the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 26 Nov 2017 10:00:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27587/why-52dk-10056-reset-when-i-connected-the-nrfuart-app" /><item><title>RE: Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/thread/108948?ContentTypeID=1</link><pubDate>Sun, 26 Nov 2017 10:00:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92083146-311c-4fc2-abbc-c8e01ac8dc8c</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Thank you.I find the way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/thread/108947?ContentTypeID=1</link><pubDate>Sun, 26 Nov 2017 09:42:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9449e8b1-f193-4eda-b08e-fd1776120aac</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;(2/2)&lt;/p&gt;
&lt;ol start="3"&gt;
&lt;li&gt;Finally reading the comment at the signature of this SVCALL you get &lt;code&gt;/ * @retval ::NRF_ERROR_FORBIDDEN The connection&amp;#39;s current security level is lower than the one required by the write permissions of the CCCD associated with this characteristic.*/&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Voilà, it took us 2 minutes. Good luck with your urgent project;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/thread/108946?ContentTypeID=1</link><pubDate>Sun, 26 Nov 2017 09:41:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:576b8158-cd77-4f1d-a577-ac4f3f1bbcbc</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Come on, that&amp;#39;s trivial:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You will look where function &lt;code&gt;ble_hids_inp_rep_send&lt;/code&gt; is implemented in SDK. It either is implemented in source code (and then you simply read it or even put some debug into it if not present) or just in header files as SVALL directly to SD (in that case you should get explanation of all possible error codes. This is the first case so we jump to file &lt;code&gt;components\ble\ble_services\ble_hids\ble_hids.c&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Now you see that the only way how this error status could be returned is by call of SD API function &lt;code&gt;sd_ble_gatts_hvx&lt;/code&gt;. So you will find its signature in header file &lt;code&gt;components\softdevice\s132\headers\ble_gatts.h&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;(1/2)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/thread/108945?ContentTypeID=1</link><pubDate>Sun, 26 Nov 2017 09:28:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a77186c-551f-4b47-bd96-2738b24fe8ea</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Hi,I&amp;#39;m sorry about that.
The reset is caused by calling  ble_hids_inp_rep_send, and the err_code is NRF_ERROR_FORBIDDEN. Could you please tell me how is that ocurred?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why 52DK(10056) reset when I connected the nrfUART app?</title><link>https://devzone.nordicsemi.com/thread/108944?ContentTypeID=1</link><pubDate>Sun, 26 Nov 2017 08:41:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b372f79c-a310-4bb9-81c9-f2be3cbab718</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;(Why? How should we know with such poor info supplied?! It&amp;#39;s great to know that it&amp;#39;s urgent and the whole universe should help you ASAP - for free - but you don&amp;#39;t bother to supply any debug information:)&lt;/p&gt;
&lt;p&gt;Debug, debug, debug, debug. What UART or RTT logging says when enabled? On which line in your source code hard fault or asserted error code from some SD or SDK function return occurs?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>