<?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>The bluetooth can not be connected.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122564/the-bluetooth-can-not-be-connected</link><description>We encountered some problems while debugging the nRF54L15. A total of 10 circuit boards were produced, and the chip on the board is nRF54L15CAAA. After programing the code, the bluetooth signal can be detected, but once connected, the chip will reset</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 28 Jun 2025 07:00:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122564/the-bluetooth-can-not-be-connected" /><item><title>RE: The bluetooth can not be connected.</title><link>https://devzone.nordicsemi.com/thread/540786?ContentTypeID=1</link><pubDate>Sat, 28 Jun 2025 07:00:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dedbb11a-ca1c-4e95-8311-a3d06e4012a4</guid><dc:creator>JunLiu</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As your advice, I modified MPSL_HFCLK_LATENCY to 1400, the bluetooth of the PCB can be connected.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Jun&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The bluetooth can not be connected.</title><link>https://devzone.nordicsemi.com/thread/540766?ContentTypeID=1</link><pubDate>Fri, 27 Jun 2025 17:29:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06f1befd-ec3c-4b88-9c1a-5a2c0b1ae85d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I suspect it&amp;#39;s due to&amp;nbsp;&lt;span&gt;CONFIG_MPSL_HFCLK_LATENCY is set to a too short value.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We are in process of updating the value from 854 (think that was the default in older ncs releases) to a higher value (1400 I believe will be the new default value). Please see preliminary release notes and kconfig option:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-3.1.0-preview2.html#developing_with_nrf54l_series"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-3.1.0-preview2.html#developing_with_nrf54l_series&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#CONFIG_MPSL_HFCLK_LATENCY"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#CONFIG_MPSL_HFCLK_LATENCY&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In older ncs releases this value is not configurable, in that case you need to manually edit&amp;nbsp;&lt;span&gt;/subsys/mpsl/init/Kconfig and for instance change to:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;config MPSL_HFCLK_LATENCY&lt;br /&gt;int&lt;br /&gt;default 1400 if SOC_SERIES_NRF54LX&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>