<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QN9021 current consumption in Deep Sleep mode? in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/QN9021-current-consumption-in-Deep-Sleep-mode/m-p/680379#M3132</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rodrigo Garbi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Achieving the lowest power can be a little tricky since it depends on a lot of factors like hardware and software. Since you are using a custom board, I can't be sure what is causing your excess current. I tested the demo with the &lt;A href="http://www.nxp.com/products/microcontrollers-and-processors/more-processors/application-specific-mcus-mpus/bluetooth-low-energy-ble/a-highly-extensible-platform-for-application-development-of-qn9020:QN9020DK"&gt;QN9020DK &lt;/A&gt;and measured ~2µA. The first thing that comes to mind is to remove&lt;STRONG&gt; #define CFG_DC_DC&lt;/STRONG&gt; because your power supply is configured without DC-to-DC converter as shown in &lt;STRONG&gt;Fig 9. QN9021 typical application schematic without DC-to-DC converter&lt;/STRONG&gt; in the &lt;A href="http://www.nxp.com/documents/data_sheet/QN902X.pdf"&gt;QN902x datasheet&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try configuring your used GPIOs as inputs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to run the sleep demo located in "&lt;EM&gt;C:\QBlue\QN9020\QBlue-1.3.9\Projects\Driver\sleep"&amp;nbsp;&lt;/EM&gt; and see if you get different results. You can set the following macros in &lt;EM&gt;sleep_example.c&lt;/EM&gt; to go to deep sleep:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#define TEST_SLEEP_CPU_CLK_OFF FALSE&lt;BR /&gt;#define TEST_SLEEP_NORMAL FALSE&lt;BR /&gt;#define TEST_SLEEP_DEEP TRUE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Run the demo and press BUTTON1 (P1.4) to go to deep sleep.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you managed to reduce your current.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 May 2017 22:08:03 GMT</pubDate>
    <dc:creator>gerardo_rodriguez</dc:creator>
    <dc:date>2017-05-25T22:08:03Z</dc:date>
    <item>
      <title>QN9021 current consumption in Deep Sleep mode?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/QN9021-current-consumption-in-Deep-Sleep-mode/m-p/680378#M3131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working with QN9021 in SOC Mode, implementing a Quintic private profile in Server Role.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The highlights of my project configuration are:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;driver_config.h&lt;/STRONG&gt; :&lt;/P&gt;&lt;P&gt;#define __AHB_CLK &amp;nbsp; &amp;nbsp; &amp;nbsp; CLK_32M /*!&amp;lt; AHB clock frequency */&lt;BR /&gt;#define __APB_CLK &amp;nbsp; &amp;nbsp; &amp;nbsp; CLK_32M /*!&amp;lt; APB clock frequency */&lt;BR /&gt;#define __BLE_CLK &amp;nbsp; &amp;nbsp; &amp;nbsp; CLK_16M /*!&amp;lt; BLE clock frequency */&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;usr_config.h&lt;/STRONG&gt; :&lt;/P&gt;&lt;P&gt;#define CFG_DC_DC&lt;BR /&gt;#define CFG_DEEP_SLEEP&lt;BR /&gt;#define CFG_BLE_SLEEP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Hardware design&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The hardware I am working with is a propietary one (it is not a evaluation kit) and its power supply is set in such a way VDD and VCC are connected and supplied with same power supply (3V on board).&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;An external 32.768 KHz crystal is connected to XTAL1_32K and XTAL2_32K &amp;nbsp;pins &lt;SPAN&gt;of QN9021&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;An external 32MHz crystal is connected to XTAL1 and XTAL2 pins of QN9021&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;QN9021 is being driven by a master MCU through SPI bus. Before entering sleep mode, master MCU is &lt;STRONG&gt;setting CLK and MOSI lines to '0'.&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;QN9021 chip select line i&lt;/STRONG&gt;s connected to 3V through a pull-up resistor (100K) and so, before entering sleep mode, master MCU is setting that line &lt;STRONG&gt;to '1'&lt;/STRONG&gt;.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;QN9021 Reset line is held up ('1') by master MCU.&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Firmware&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;I can see, debugging the board that program is entering deep sleep mode (then, generating a interrupt in a GPIO will wake the device up).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Finally, the question is:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;How can I achieve the 2uA of current consumption in deep sleep mode?? Because, with settings mentioned above, I am getting around 60uA and I have tried different options (QN_32K_LOW_POWER_MODE_EN = TRUE and FALSE, &amp;nbsp;CFG_DC_DC defined and commented, etc) and can not decrease QN9021 power consumption.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 May 2017 20:03:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/QN9021-current-consumption-in-Deep-Sleep-mode/m-p/680378#M3131</guid>
      <dc:creator>rodri</dc:creator>
      <dc:date>2017-05-15T20:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: QN9021 current consumption in Deep Sleep mode?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/QN9021-current-consumption-in-Deep-Sleep-mode/m-p/680379#M3132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rodrigo Garbi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Achieving the lowest power can be a little tricky since it depends on a lot of factors like hardware and software. Since you are using a custom board, I can't be sure what is causing your excess current. I tested the demo with the &lt;A href="http://www.nxp.com/products/microcontrollers-and-processors/more-processors/application-specific-mcus-mpus/bluetooth-low-energy-ble/a-highly-extensible-platform-for-application-development-of-qn9020:QN9020DK"&gt;QN9020DK &lt;/A&gt;and measured ~2µA. The first thing that comes to mind is to remove&lt;STRONG&gt; #define CFG_DC_DC&lt;/STRONG&gt; because your power supply is configured without DC-to-DC converter as shown in &lt;STRONG&gt;Fig 9. QN9021 typical application schematic without DC-to-DC converter&lt;/STRONG&gt; in the &lt;A href="http://www.nxp.com/documents/data_sheet/QN902X.pdf"&gt;QN902x datasheet&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try configuring your used GPIOs as inputs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to run the sleep demo located in "&lt;EM&gt;C:\QBlue\QN9020\QBlue-1.3.9\Projects\Driver\sleep"&amp;nbsp;&lt;/EM&gt; and see if you get different results. You can set the following macros in &lt;EM&gt;sleep_example.c&lt;/EM&gt; to go to deep sleep:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#define TEST_SLEEP_CPU_CLK_OFF FALSE&lt;BR /&gt;#define TEST_SLEEP_NORMAL FALSE&lt;BR /&gt;#define TEST_SLEEP_DEEP TRUE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Run the demo and press BUTTON1 (P1.4) to go to deep sleep.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you managed to reduce your current.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 May 2017 22:08:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/QN9021-current-consumption-in-Deep-Sleep-mode/m-p/680379#M3132</guid>
      <dc:creator>gerardo_rodriguez</dc:creator>
      <dc:date>2017-05-25T22:08:03Z</dc:date>
    </item>
  </channel>
</rss>

