<?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>If EVENTS_HFCLKSTARTED never triggers is the problem definitely pcb related?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50326/if-events_hfclkstarted-never-triggers-is-the-problem-definitely-pcb-related</link><description>Hello All, 
 We have a custom board with nRF52840 and I believe, we have problem with the HFCLK. 
 We are trying to test our board with the ble_app_blinky example and it works fine with our nRF52840 Preview DK. Using the same example on our custom board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 Jul 2019 15:19:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50326/if-events_hfclkstarted-never-triggers-is-the-problem-definitely-pcb-related" /><item><title>RE: If EVENTS_HFCLKSTARTED never triggers is the problem definitely pcb related?</title><link>https://devzone.nordicsemi.com/thread/201329?ContentTypeID=1</link><pubDate>Tue, 30 Jul 2019 15:19:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f13d09f-d76e-4ae7-b4c9-a63d79867bbf</guid><dc:creator>Gurel</dc:creator><description>&lt;p&gt;Thank you very much for your help RK, I really appreciate your help. As you also noticed someone made a mistake during the production of our custom board and they put a crystal oscillator instead of a crystal.&lt;/p&gt;
&lt;p&gt;Update: Yes the issue was with the clock source. Once we replaced the old component with the coorect one everything worked as expected.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: If EVENTS_HFCLKSTARTED never triggers is the problem definitely pcb related?</title><link>https://devzone.nordicsemi.com/thread/201081?ContentTypeID=1</link><pubDate>Mon, 29 Jul 2019 23:42:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fdc68b6c-efd9-4533-8ede-3b908b58aa75</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;If you&amp;#39;re correct about the crystal which has been mounted then .. it&amp;#39;s not even a crystal, it&amp;#39;s a crystal oscillator designed with the same form factor as a 2mm x 1.6mm crystal. That thing requires power into pin #4 which I&amp;#39;m 99.999% you&amp;#39;ve grounded as pins #2 and #4 are ground on a real 2x1.6 crystal. It would actually be possible to use a crystal oscillator such as this one as the nRF does accept a driven oscillator input, however you&amp;#39;d need a different circuit to apply power to it and you&amp;#39;d need different settings on the nRF to use it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know why anyone would replace the crystal you specified with an entirely incompatible device. But it&amp;#39;s not going to work.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: If EVENTS_HFCLKSTARTED never triggers is the problem definitely pcb related?</title><link>https://devzone.nordicsemi.com/thread/201056?ContentTypeID=1</link><pubDate>Mon, 29 Jul 2019 16:51:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6649fa1-4eeb-4620-90b5-67e4619075c7</guid><dc:creator>Gurel</dc:creator><description>&lt;p&gt;Thanks for the answer RK.&lt;/p&gt;
&lt;p&gt;The crystal that is used on the board is &lt;a href="https://media.digikey.com/pdf/Data%20Sheets/NDK%20PDFs/NT2016SA-32M-END4263A.pdf" rel="noopener noreferrer" target="_blank"&gt;this crystal.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I noticed that the crystal used on the board is different than &lt;a href="https://eu.mouser.com/datasheet/2/3/ABM11W-101-32.0000MHz-T3-1359246.pdf" rel="noopener noreferrer" target="_blank"&gt;the crystal&lt;/a&gt; that was selected by the design team. It looks like pins are not compatible between the crystal that is used and the crystal that is selected by the design team. I would really appreciate if someone can verify if this two crystals are not compatible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: If EVENTS_HFCLKSTARTED never triggers is the problem definitely pcb related?</title><link>https://devzone.nordicsemi.com/thread/200863?ContentTypeID=1</link><pubDate>Mon, 29 Jul 2019 01:08:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:72736881-ed88-4df3-8e0d-4fb53d6b13a8</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Yes it is most likely a crystal problem. Either it&amp;#39;s soldered badly or the load capacitance is incorrect or the load caps are incorrectly soldered or you put the wrong load caps on&amp;nbsp; there is something else about the crystal which is out of spec. The only board I ever had which failed that simple test you have above, starting the HFCLK and waiting for it to start, had a crystal soldering issue.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you want to post the exact make and model of the crystal someone can check it&amp;#39;s a model which ought to work.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>