<?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>BLE Not Starting on Custom PCB (BC40C, nRF5340) – Possible Clock Problem?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123399/ble-not-starting-on-custom-pcb-bc40c-nrf5340-possible-clock-problem</link><description>Hi everyone, 
 I wanted to share an update on the BLE issue I’m experiencing with the BC40C (nRF5340) module on my custom PCB. I initially described the problem in this , where I suspected that the issue might be related to a missing or incorrect startup</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Aug 2025 06:40:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123399/ble-not-starting-on-custom-pcb-bc40c-nrf5340-possible-clock-problem" /><item><title>RE: BLE Not Starting on Custom PCB (BC40C, nRF5340) – Possible Clock Problem?</title><link>https://devzone.nordicsemi.com/thread/544410?ContentTypeID=1</link><pubDate>Mon, 04 Aug 2025 06:40:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad8fa67b-1e37-47af-a6ed-3b8ffaa09896</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see. I suggest progressing the following way:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Verify that you see this issue with more than one module in case it is a fault device.&lt;/li&gt;
&lt;li&gt;Start logging and debuggign to verify that advertising is successfully started and that there are no errors.&lt;/li&gt;
&lt;li&gt;If that does not reveal any issue, I suggest setting up a carrier using the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/peripheral/radio_test/README.html"&gt;radio test sample&lt;/a&gt; and verifying the frequency with a specrtrum analyzer. This will show if the HFXO is behaving properly. If it is not, I would start by checking if there are clock differences between the two versions of the module, that lead to there perhaps being a need for a different load capacitor configuration.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Not Starting on Custom PCB (BC40C, nRF5340) – Possible Clock Problem?</title><link>https://devzone.nordicsemi.com/thread/544398?ContentTypeID=1</link><pubDate>Sun, 03 Aug 2025 17:54:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bfc3dfaa-a84f-4a2b-8fea-6e5e58a082f1</guid><dc:creator>YeQuit</dc:creator><description>&lt;p data-start="217" data-end="224"&gt;&lt;strong data-start="217" data-end="224"&gt;Hi,&lt;/strong&gt;&lt;/p&gt;
&lt;p data-start="261" data-end="548"&gt;When I say &amp;ldquo;BLE is not working,&amp;rdquo; I mean that the device does not show up in the &lt;em data-start="341" data-end="354"&gt;nRF Connect&lt;/em&gt; mobile app or any other BLE scanner, even though it should be advertising. The same firmware works perfectly on our V1 board (device shows up and connects), but on V2, it doesn&amp;rsquo;t appear at all.&lt;/p&gt;
&lt;p data-start="550" data-end="870"&gt;I&amp;rsquo;ve tested various firmware examples, including ones from the BC40C module manufacturer. Flashing works without any issues on both versions &amp;mdash; the LED behavior changes after flashing, and memory contents are updated correctly (verified via nRF Programmer). However, BLE advertising still does not happen on the V2 board.&lt;/p&gt;
&lt;h3 data-start="872" data-end="919"&gt;Regarding Point 1 (HFXO &amp;amp; load capacitors):&lt;/h3&gt;
&lt;p data-start="921" data-end="1099"&gt;The capacitor values are the same on V1 and V2. The only difference is that V2 uses 0402 components instead of 0603, but both are rated for 6.3 V, so that should not be an issue.&lt;/p&gt;
&lt;p data-start="1101" data-end="1414"&gt;Also important to note:&lt;br data-start="1124" data-end="1127" /&gt;We&amp;rsquo;re using the &lt;strong data-start="1143" data-end="1187"&gt;BC40C as a complete pre-certified module&lt;/strong&gt;, so &lt;strong data-start="1192" data-end="1267"&gt;we did not modify or change anything related to the crystal oscillators&lt;/strong&gt; &amp;mdash; those are integrated into the module. The only external passives we placed are the &lt;strong data-start="1353" data-end="1378"&gt;decoupling capacitors&lt;/strong&gt;, as recommended in the datasheet.&lt;/p&gt;
&lt;p data-start="1416" data-end="1770"&gt;To rule out board-level issues, I also removed the capacitors on the boards and tested with the BC40C wired from the V2 board onto the EV-BC40C evaluation board as well as V1 &amp;mdash; BLE only works when the module is running on the eval board or connected via wires. It does &lt;em data-start="1672" data-end="1677"&gt;not&lt;/em&gt; work when running directly on the V2 PCB, regardless of the capacitors being present or not.&lt;/p&gt;
&lt;h3 data-start="1772" data-end="1818"&gt;Regarding points 2 &amp;amp; 3 (Debugging &amp;amp; Logs):&lt;/h3&gt;
&lt;p data-start="1820" data-end="2031"&gt;I haven&amp;rsquo;t tried logging yet, but I will definitely look into it based on the information you provided. I&amp;rsquo;ll study how to enable and use logging in this context, and follow up with the output once I have results.&lt;/p&gt;
&lt;p data-start="2033" data-end="2071"&gt;Thanks again for your helpful support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Not Starting on Custom PCB (BC40C, nRF5340) – Possible Clock Problem?</title><link>https://devzone.nordicsemi.com/thread/544325?ContentTypeID=1</link><pubDate>Fri, 01 Aug 2025 12:28:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fff6940-9a84-4a98-b916-84253701a9f5</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;When you write that BLE is not working, what exactly does that mean? How have you tested, and do you have any logging enabled? What does the log say? Also, have you done any debugging? What have you learned from the deubgging? Even if the issue may be HW related, we may be able to get usefull pointers from debugging.&lt;/p&gt;
&lt;p&gt;that said, typical BLE related issues when changing the HW is related to oscillator configuration, as you have indicated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;If everythign looks good from SW perspective but you cannot observe BLE advertising packets from the device even if it should be advertising and you see it does from debugging, that could indicate an inacurate HFXO frequency. A typical reason for this would be incorrect load capacitor values.&lt;/li&gt;
&lt;li&gt;If advertising packiets are recived correctly, but establishign and maintaining a connection is difficult or impossible and result in disconnect reason 0x3E (&amp;quot;Connection Failed to be Established&amp;quot;), this could point to a problem with the LF crystall oscillator (if using LFXO, the load caps around that).&lt;/li&gt;
&lt;li&gt;See &lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/f791c49f492c40da0d18efd51087b6fe1ec56aa0/doc/releases/migration-guide-4.0.rst#clock-control"&gt;here&lt;/a&gt; for information on how to configure the load capacitors (it depend on the SDK version, if using a recent SDK version, you do it in the devicetree)&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>