<?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>Custom boards not drawing enough current while advertising (programmable, PPK shows advertising state, but boards not discoverable in mobile app)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69862/custom-boards-not-drawing-enough-current-while-advertising-programmable-ppk-shows-advertising-state-but-boards-not-discoverable-in-mobile-app</link><description>Hey all! So I&amp;#39;m working on some custom boards using the nRF52810-CAAA chip, I write firmware using SDK V15.2.0 (outdated I know). I&amp;#39;m having an issue with a recent batch of PCBs I received - some of the boards work fine, power consumption is great, antenna</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 03 Jan 2021 06:05:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69862/custom-boards-not-drawing-enough-current-while-advertising-programmable-ppk-shows-advertising-state-but-boards-not-discoverable-in-mobile-app" /><item><title>RE: Custom boards not drawing enough current while advertising (programmable, PPK shows advertising state, but boards not discoverable in mobile app)</title><link>https://devzone.nordicsemi.com/thread/287090?ContentTypeID=1</link><pubDate>Sun, 03 Jan 2021 06:05:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c3a46d09-1049-4fd5-a1a8-4b7ad2c580db</guid><dc:creator>Noah</dc:creator><description>&lt;p&gt;Ultimately I think this is just an issue with PCB assembly, I&amp;#39;m ordering small batches of just 20-40 PCBs with a rather delicate 4 layer flex PCB design. About half of the boards work fine, the other half don&amp;#39;t, so I think this just boils down to a yield problem. With more units, more investment into assembly fixturing and calibration, I think the yield will get better. The response is still helpful, thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom boards not drawing enough current while advertising (programmable, PPK shows advertising state, but boards not discoverable in mobile app)</title><link>https://devzone.nordicsemi.com/thread/287068?ContentTypeID=1</link><pubDate>Fri, 01 Jan 2021 03:01:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4a63623a-dd33-4f1c-aba2-9e900f2611ab</guid><dc:creator>Noah</dc:creator><description>&lt;p&gt;I will look into all the points you mentioned, thank you. What&amp;#39;s interesting is how you mention the &amp;quot;good&amp;quot; current draw actually looks too high. I&amp;#39;ve probably tested close to 750 boards in total, across all my designs, and this 12mA spike is what I&amp;#39;ve seen across all of them during advertising. Maybe I never enabled DCDC in my firmware, haha I will double check!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom boards not drawing enough current while advertising (programmable, PPK shows advertising state, but boards not discoverable in mobile app)</title><link>https://devzone.nordicsemi.com/thread/286982?ContentTypeID=1</link><pubDate>Wed, 30 Dec 2020 10:48:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:531cfba7-fc0e-4728-b9d3-72abc6c15a09</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi, are you able to zoom in on the advertising event, and compare the two plots. I think maybe you will have to use the bottom graph in the PPK software to get a good enough resolution. I was thinking if we were able to identify which parts of the advertising event that are consuming less current (if it&amp;#39;s only TX, or both RX and TX, CPU etc), it should help us debug this further.&lt;/p&gt;
&lt;p&gt;If you are using DCDC I think that the &amp;quot;good&amp;quot; plot has too high peak current consumption, even with 4 dBm output power the TX should not be higher than 8-9 mA. And with a 0 dBm output power the bottom plot looks normal. This is of course if nothing else is running at the same time. To me it looks like DCDC is not enabled?&lt;/p&gt;
&lt;p&gt;Maybe you can try to flash a test FW where you both enable and disable the DCDC, and then check if the current consumption changes. Or if the failing boards are working when the DCDC is disabled.&lt;/p&gt;
&lt;p&gt;Yes, a bad connection on DEC2 might cause problems, so maybe you can try to swap out the capacitor with a new one.&lt;/p&gt;
&lt;p&gt;Are you able to measure the voltage on the decoupling caps? DEC1, 2 and 4? Preferably with a scope to see the ripples, and max/min voltages.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>