<?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>SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/15812/sdk-11-peer-manager-smd_params_reply-returns-nrf_error_internal</link><description>Hi. I&amp;#39;m using SDK 11, SD s130, gcc, nRF51822. My application is a peripheral that advertises OK and gets a connection from our mobile app OK, but then gets a PM_EVT_ERROR_UNEXPECTED event on bonding. 
 Here&amp;#39;s the stack trace at the time of the pm_evt_handler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Aug 2016 08:39:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/15812/sdk-11-peer-manager-smd_params_reply-returns-nrf_error_internal" /><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60370?ContentTypeID=1</link><pubDate>Wed, 24 Aug 2016 08:39:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2567141d-9785-40d7-84a1-98b7ef176b11</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Thank you for the update.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60369?ContentTypeID=1</link><pubDate>Fri, 19 Aug 2016 19:37:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0dfc0075-9313-4345-ad56-8f48bff320d4</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;This was down to an error in the linker script for the application. We use the example bootloader from SDK 11 and I had wrongly assumed that the .fs_data SECTION in the application&amp;#39;s linker script should match the one in the bootloader. It should not. The application uses the fstorage module, the bootloader doesn&amp;#39;t. Best explained here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/question/72778/fs_data-usage-in-dfu-bootloader-and-ble_app_hrs__with_dfu/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60362?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 14:42:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9e9a0bd-5178-4a8e-aaa1-f490add5fc80</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;Had to open a case, sorry. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60366?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 13:58:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd6a94c6-bab9-4a8c-ba7e-f13114fe5785</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Sounds like a plan.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60368?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 13:50:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25e5db91-61cf-4a8e-8d08-680aafe8ab46</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;Sure. I&amp;#39;ll just step back through some old checkins and see if a change I made has caused it. If I can&amp;#39;t pin it down I&amp;#39;ll open a case with the project attached - too much code to post here. Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60367?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 13:37:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbd521a9-ed00-413e-ac03-25a5abcf1ff7</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;I guess the error is coming from somewhere else then. I would like to help you to debug this, could you share your project? Or a project that reproduces the issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60365?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 12:55:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07338146-22ee-419c-8907-bf520e7f2945</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;Line numbers above are for security_dispatcher.c, not peer_id.c, btw.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60364?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 12:54:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1a1e1bb-caee-4dbb-ab7e-fb6136201e5a</guid><dc:creator>Eliot Stock</dc:creator><description>&lt;p&gt;That&amp;#39;s exactly what&amp;#39;s confusing me - that line with err_code = NRF_ERROR_INTERNAL, L588 does NOT execute. err_code is still 0 at L592. Nothing in the block that follows is getting a non-zero err_code when I debug it. No error at L592, nor L596, nor L612. And yet at L621, err_code is 3. (These are all breakpoints set in isolation and I&amp;#39;m reflashing and resetting before testing each one, I&amp;#39;m not expecting to step through code while in a BLE connection, just to be clear.)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 11 peer manager: smd_params_reply() returns NRF_ERROR_INTERNAL</title><link>https://devzone.nordicsemi.com/thread/60363?ContentTypeID=1</link><pubDate>Thu, 18 Aug 2016 12:15:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04d70439-00c3-49fe-9d52-ea7cd6dc0879</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;If you put a breakpoint at err_code = NRF_ERROR_INTERNAL;, do you hit it? If you do, where in PM_PEER_ID_INVALID returned from inside pdb_peer_allocate()?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>