<?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>Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42156/nordic-mesh-sdk-issue-with-a-nordic-module-by-laird-bl652</link><description>Hello, 
 I have been working with Bluetooth Mesh SDK since few months. Recently, we came across a custom BLE module which has Laird&amp;#39;s BL652(nRf52832) chip on it (Not the BL652 DK). We tried to execute few UART examples on the module which worked fine</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Feb 2019 15:41:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42156/nordic-mesh-sdk-issue-with-a-nordic-module-by-laird-bl652" /><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/170694?ContentTypeID=1</link><pubDate>Tue, 12 Feb 2019 15:41:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fba5ea3-58ca-496e-94be-9cb5fe9f90d3</guid><dc:creator>DeveloperZ</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;Any progress on the issue?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/165493?ContentTypeID=1</link><pubDate>Mon, 14 Jan 2019 13:58:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad89b74a-e032-4608-ba2b-f6e6c63e41bb</guid><dc:creator>DeveloperZ</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;Any update on the issue?&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/164310?ContentTypeID=1</link><pubDate>Mon, 07 Jan 2019 14:35:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fac9408d-941a-4916-885c-dc469e31f046</guid><dc:creator>DeveloperZ</dc:creator><description>&lt;p&gt;Also, does the packaging affect the initialization as this custom board has a completely different I/O compared to the nRF52832 on the nRF52 DK.&lt;/p&gt;
&lt;p&gt;In order to test the UART communication, I made changes to the UART pins in the pca10040.h file and it worked. I am curious to know if the pin configurations does affect the soft_device enabling and initialization of Mesh.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/164285?ContentTypeID=1</link><pubDate>Mon, 07 Jan 2019 13:52:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f11df4e5-dd15-48aa-bdff-c16797248111</guid><dc:creator>DeveloperZ</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I changed the clock source as you mentioned and I also changed the&amp;nbsp;NRF_SDH_CLOCK_LF_ACCURACY to&amp;nbsp;NRF_CLOCK_LF_ACCURACY_500_PPM as it prompted in the warning. Now, it results in a Mesh error 7 at 0x00000000(:0)&lt;/p&gt;
&lt;p&gt;I traced that the error was pointed to nrf_sdh_enable request function in the ble_stack_init(). The part of the code resulting in error is&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;ret_code = sd_softdevice_enable(&amp;amp;clock_lf_cfg, app_error_fault_handler);
#endif
    m_nrf_sdh_enabled = (ret_code == NRF_SUCCESS);
    CRITICAL_REGION_EXIT();

    if (ret_code != NRF_SUCCESS)
    {
        return ret_code;
    }&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Any additional changes required to enable the soft device?&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/164272?ContentTypeID=1</link><pubDate>Mon, 07 Jan 2019 13:24:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9921993c-623a-4cf5-b66a-36bc8e84b93c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;If you don&amp;#39;t have the 32kHz crystal on the board you would need to configure the softdevice to use the RC oscillator instead.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You need to modify sdk_config.h&amp;nbsp;NRF_SDH_CLOCK_LF_SRC to&amp;nbsp;NRF_CLOCK_LF_SRC_RC instead of&amp;nbsp;NRF_CLOCK_LF_SRC_XTAL&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/164260?ContentTypeID=1</link><pubDate>Mon, 07 Jan 2019 13:09:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b616eff1-8a5d-4cef-8826-ea5d97117b47</guid><dc:creator>DeveloperZ</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We are using just the BL652 chip but not the development board. So, we do not have the 32KHz crystal on this custom board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nordic Mesh SDK issue with a Nordic Module by Laird(BL652)</title><link>https://devzone.nordicsemi.com/thread/164056?ContentTypeID=1</link><pubDate>Fri, 04 Jan 2019 22:08:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8f5f41e-8e8d-46c1-811b-f03b998ed346</guid><dc:creator>emh203</dc:creator><description>&lt;p&gt;Make sure the 32KHz crystal is connected.&amp;nbsp; &amp;nbsp;I think the mesh SDK defaults to turning it on.&amp;nbsp; &amp;nbsp; I had this issue with the BL654 module on their DVK&amp;nbsp; so it may be the same for the BL652&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>