<?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>Unstable Distance Measurement with Synthesized LFCLK (LFSYNT) on nRF5340</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122918/unstable-distance-measurement-with-synthesized-lfclk-lfsynt-on-nrf5340</link><description>Hello Nordic Team, 
 I&amp;#39;m developing a ranging application on a u-blox NORA-B1 module (which contains an nRF5340) and have encountered a stability issue with the Nordic Distance Measurement (NDM) library when using the synthesized low-frequency clock </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Jul 2025 13:05:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122918/unstable-distance-measurement-with-synthesized-lfclk-lfsynt-on-nrf5340" /><item><title>RE: Unstable Distance Measurement with Synthesized LFCLK (LFSYNT) on nRF5340</title><link>https://devzone.nordicsemi.com/thread/542391?ContentTypeID=1</link><pubDate>Mon, 14 Jul 2025 13:05:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:207c26f7-359b-4ba0-89e6-e648cfd9dcf5</guid><dc:creator>_lumac</dc:creator><description>&lt;p&gt;Hi Vidar,&lt;/p&gt;
&lt;p&gt;Thanks for the explanation and the helpful links!&lt;/p&gt;
&lt;p&gt;Just to clarify, in my current project configuration, both cores already have the same LF clock source selected.&lt;/p&gt;
&lt;p&gt;I will proceed with trying the &lt;code&gt;K32SRC_RC&lt;/code&gt; configuration this week and will share the results. I&amp;#39;m still a bit puzzled as to why the synthesized clock is causing the Distance Measurement (DM) application to crash, but hopefully, the &lt;code&gt;K32SRC_RC&lt;/code&gt; will provide a stable solution.&lt;/p&gt;
&lt;p&gt;Thanks again for your support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable Distance Measurement with Synthesized LFCLK (LFSYNT) on nRF5340</title><link>https://devzone.nordicsemi.com/thread/542388?ContentTypeID=1</link><pubDate>Mon, 14 Jul 2025 12:46:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b5a2796-1f09-41c6-b0e2-37e7c9809104</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;When selecting the clock source on the nRF5340 it is important that you make the same selection on both cores and not only on the application core. The network core FW may fail to boot if not.&amp;nbsp;&lt;span style="font-family:inherit;"&gt;Configurations added to the prj.conf file in your project folder will only be applied to the main application.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;&lt;/span&gt;You can set the default LF clock source in your board file if you are going to define your own custom board like how this boards selects the RCOSC as the default clock source for the app and network core:&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/81a2b95a7e78217ec0ec0173a0dc9bcc4447ea5e/boards/panasonic/pan1783/pan1783a_evb_nrf5340_cpunet_defconfig#L13"&gt;https://github.com/nrfconnect/sdk-zephyr/blob/81a2b95a7e78217ec0ec0173a0dc9bcc4447ea5e/boards/panasonic/pan1783/pan1783a_evb_nrf5340_cpunet_defconfig#L13&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/81a2b95a7e78217ec0ec0173a0dc9bcc4447ea5e/boards/panasonic/pan1783/pan1783a_pa_evb_nrf5340_cpuapp_defconfig#L20"&gt;https://github.com/nrfconnect/sdk-zephyr/blob/81a2b95a7e78217ec0ec0173a0dc9bcc4447ea5e/boards/panasonic/pan1783/pan1783a_pa_evb_nrf5340_cpuapp_defconfig#L20&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable Distance Measurement with Synthesized LFCLK (LFSYNT) on nRF5340</title><link>https://devzone.nordicsemi.com/thread/542365?ContentTypeID=1</link><pubDate>Mon, 14 Jul 2025 10:44:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d220c61-746a-49be-8000-430c4db73ddf</guid><dc:creator>_lumac</dc:creator><description>&lt;p&gt;Hi Turbo J,&lt;br /&gt;&lt;br /&gt;I appreciate the information about LFSYNTH not being compatible with BTLE. I&amp;#39;m actively looking for documentation on that to understand the limitations better.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I&amp;#39;ll try using the calibrated LFRC this week and will post my results back here.&lt;br /&gt;&lt;br /&gt;Thanks for your help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unstable Distance Measurement with Synthesized LFCLK (LFSYNT) on nRF5340</title><link>https://devzone.nordicsemi.com/thread/542281?ContentTypeID=1</link><pubDate>Fri, 11 Jul 2025 18:46:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:65bea3f4-7ed7-4bc6-9f1e-4ce03b12a5a7</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;LFSYNTH is not compatible with BTLE operation at all, no idea where that is documented though.At least it used to be this way with NRF52x chips.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you tried using the calibrated LFRC? That one&amp;nbsp;&lt;em&gt;can&lt;/em&gt; be used in BTLE mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>