<?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>error code: 0x08</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4268/error-code-0x08</link><description>hello,
I am using S130 softdevice. While I am trying to connect with MCP I am getting one error with error code :0x08. and MCP is showing a message like &amp;quot;Lost connection to the device. Reason: BTLE CONNECTION TIMEOUT&amp;quot;. 
 My code looks like this: 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Mar 2016 15:36:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4268/error-code-0x08" /><item><title>RE: error code: 0x08</title><link>https://devzone.nordicsemi.com/thread/15243?ContentTypeID=1</link><pubDate>Tue, 29 Mar 2016 15:36:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c662c63a-9f56-461d-a6a1-1a87e13b84b1</guid><dc:creator>AmiguelS</dc:creator><description>&lt;p&gt;For those looking for more information on this subject, I will leave here a comment on what was causing this same problem on my application. The last line of the &lt;code&gt;ble_conn_params_init(..)&lt;/code&gt; funtion is a call to &lt;code&gt;app_timer_create(...)&lt;/code&gt;. This timer creation function may return three different codes, one of which is the mentioned &lt;code&gt;NRF_ERROR_INVALID_STATE&lt;/code&gt;. According to the documentation, that error code is returned &lt;em&gt;&amp;quot;If the application timer module has not been initialized or the timer is running&amp;quot;&lt;/em&gt;. So, in the end, I was missing a timer definition, which looks something like &lt;code&gt;APP_TIMER_DEF(m_our_char_timer_id);&lt;/code&gt; Remember to also define the timer timeout callback function.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: error code: 0x08</title><link>https://devzone.nordicsemi.com/thread/15242?ContentTypeID=1</link><pubDate>Wed, 05 Nov 2014 05:15:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a1c28704-3e17-45e1-a345-1097a70f3b15</guid><dc:creator>Anjaly</dc:creator><description>&lt;p&gt;I tried with peripheral only. I could figure out my mistake. Thanks for the help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: error code: 0x08</title><link>https://devzone.nordicsemi.com/thread/15241?ContentTypeID=1</link><pubDate>Tue, 04 Nov 2014 09:34:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0d050f3-a364-4dcf-8bdb-9db7050495bb</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;Error code 0x08 NRF_ERROR_INVALID_STATE indicate that you are trying to do an operation from a state that the specific operations isn&amp;#39;t allowed. It could be that you are trying to change the connection parameters too early, for example before you have established the connection itself.&lt;/p&gt;
&lt;p&gt;Are you running the S130 with just one peripheral or do you have it running as a central as well? Make sure that you are updating the connection parameters for the right connection. In the S130 example they differentiate between a peripherals connection parameter request and what the central will allow.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>