<?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>Wireless MCUのトピックRe: [KW36] Which low power mode supports RTC_CLKOUT?</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1572140#M14186</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P lang="es-MX"&gt;RTC remains functional in all low power modes, but please consider that PTB3 is connected to LED3 and this LED is used by BLE demos as indicator for some application states. The code may be configuring PTB3 as GPIO for this purpose and continuously modifying the state of the pin.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Please, take a look at LED_Init() function, inside ApplMain.c, this function configures pin routing for LED pins.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Dec 2022 23:16:00 GMT</pubDate>
    <dc:creator>EduardoZamora</dc:creator>
    <dc:date>2022-12-19T23:16:00Z</dc:date>
    <item>
      <title>[KW36] Which low power mode supports RTC_CLKOUT?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1570865#M14164</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Dear NXP support,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When I checked RTC_CLKOUT with FRDM-KW36 board, it did not work normally in low power mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The test environment and results are as follows.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Board : FRDM-KW36&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Source : frdmkw36_wireless_examples_bluetooth_hrs_freertos&amp;nbsp;+ frdmkw36_driver_examples_rtc&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Modified Source:&amp;nbsp;&lt;BR /&gt;#define mNoOfPinsDisabledInLowPower_c (15) //Modify&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;const gpioPinId_t maPinsDisabledInLowPower[mNoOfPinsDisabledInLowPower_c]={&lt;BR /&gt;{gpioPort_A_c, 16},&lt;BR /&gt;{gpioPort_A_c, 17},&lt;BR /&gt;{gpioPort_B_c, 1},&lt;BR /&gt;{gpioPort_B_c, 2},&lt;BR /&gt;//{gpioPort_B_c, 3}, //Modify&lt;BR /&gt;{gpioPort_C_c, 0},&lt;BR /&gt;{gpioPort_C_c, 1},&lt;BR /&gt;{gpioPort_C_c, 3},&lt;BR /&gt;{gpioPort_C_c, 6},&lt;BR /&gt;{gpioPort_C_c, 7},&lt;BR /&gt;{gpioPort_C_c, 16},&lt;BR /&gt;{gpioPort_C_c, 17},&lt;BR /&gt;{gpioPort_C_c, 18},&lt;BR /&gt;{gpioPort_C_c, 19},&lt;BR /&gt;{gpioPort_A_c, 0},&lt;BR /&gt;{gpioPort_A_c, 1}&lt;BR /&gt;};&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;void BOARD_InitPins(void) {&lt;BR /&gt;CLOCK_EnableClock(kCLOCK_PortB); /* Port B Clock Gate Control: Clock enabled */&lt;BR /&gt;PORT_SetPinMux(PORTB, PIN3_IDX, kPORT_MuxAlt7); /* PORTB3 (pin 19) is configured as PTB3 */&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&lt;BR /&gt;void BOARD_ReInitPins(void)&lt;BR /&gt;{&lt;BR /&gt;BOARD_InitPins();&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&lt;BR /&gt;void BOARD_WarmbootCb()&lt;BR /&gt;{&lt;BR /&gt;...&lt;BR /&gt;BOARD_ReInitPins();&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;void BOARD_RTCInit(void)&lt;BR /&gt;{&lt;BR /&gt;rtc_datetime_t date;&lt;BR /&gt;rtc_config_t rtcConfig;&lt;BR /&gt;&lt;BR /&gt;BOARD_InitPins();&lt;BR /&gt;RTC_GetDefaultConfig(&amp;amp;rtcConfig);&lt;BR /&gt;RTC_Init(RTC, &amp;amp;rtcConfig);&lt;BR /&gt;#if (defined(EXAMPLE_CAP_LOAD_VALUE) &amp;amp;&amp;amp; EXAMPLE_CAP_LOAD_VALUE)&lt;BR /&gt;#if (defined(FSL_FEATURE_RTC_HAS_OSC_SCXP) &amp;amp;&amp;amp; FSL_FEATURE_RTC_HAS_OSC_SCXP)&lt;BR /&gt;/* Change the RTC oscillator capacity load value. */&lt;BR /&gt;RTC_SetOscCapLoad(RTC, EXAMPLE_CAP_LOAD_VALUE);&lt;BR /&gt;#endif /* FSL_FEATURE_RTC_HAS_OSC_SCXP */&lt;BR /&gt;#endif /* EXAMPLE_CAP_LOAD_VALUE */&lt;/P&gt;&lt;P&gt;/* Select RTC clock source */&lt;BR /&gt;RTC_SetClockSource(RTC);&lt;/P&gt;&lt;P&gt;/* Set a start date time and start RT */&lt;BR /&gt;date.year = 2014U;&lt;BR /&gt;date.month = 12U;&lt;BR /&gt;date.day = 25U;&lt;BR /&gt;date.hour = 19U;&lt;BR /&gt;date.minute = 0;&lt;BR /&gt;date.second = 0;&lt;/P&gt;&lt;P&gt;/* RTC time counter has to be stopped before setting the date &amp;amp; time in the TSR register */&lt;BR /&gt;RTC_StopTimer(RTC);&lt;/P&gt;&lt;P&gt;/* Set RTC time to default */&lt;BR /&gt;RTC_SetDatetime(RTC, &amp;amp;date);&lt;/P&gt;&lt;P&gt;/* Enable RTC alarm interrupt */&lt;BR /&gt;RTC_EnableInterrupts(RTC, kRTC_AlarmInterruptEnable);&lt;/P&gt;&lt;P&gt;/* Enable at the NVIC */&lt;BR /&gt;EnableIRQ(RTC_IRQn);&lt;/P&gt;&lt;P&gt;/* Start the RTC time counter */&lt;BR /&gt;RTC_StartTimer(RTC);&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;void main_task(uint32_t param)&lt;BR /&gt;{&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;...&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;LED_Init();&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;BOARD_RTCInit();&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;}&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;1) cPWR_DeepSleepMode 4/5/8&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;=&amp;gt;&amp;nbsp;Not working&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;2)&amp;nbsp;cPWR_DeepSleepMode 3&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;2-1) Idle state&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;=&amp;gt; 1Hz output&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="llvs_idle.PNG" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/204657iA10640100F3F6B66/image-size/medium?v=v2&amp;amp;px=400" role="button" title="llvs_idle.PNG" alt="llvs_idle.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;2-2) Advertising state&lt;/P&gt;&lt;P&gt;==&amp;gt;&amp;nbsp;&lt;SPAN&gt;1 Hz output, square wave not normal&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="llvs_advertising.PNG" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/204658i61283AAE1679C351/image-size/medium?v=v2&amp;amp;px=400" role="button" title="llvs_advertising.PNG" alt="llvs_advertising.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please check if 1Hz square wave can be used through RTC_CLKOUT in low power mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Ayden Hong&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2022 01:49:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1570865#M14164</guid>
      <dc:creator>ayden</dc:creator>
      <dc:date>2022-12-16T01:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: [KW36] Which low power mode supports RTC_CLKOUT?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1571385#M14166</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/138907"&gt;@ayden&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Hope you are doing well.&lt;/P&gt;
&lt;P lang="es-MX"&gt;According to the Bluetooth Low Energy Demo Applications User Guide (inside KW36 SDK documentation folder &amp;gt; docs &amp;gt; wireless &amp;gt; Bluetooth), the application should switch between LLS and VLLS power modes by default.&lt;/P&gt;
&lt;P lang="es-MX"&gt;KW38 Reference Manual, Section 8.5 Module Operation in Low Power Modes describes modules/clocks availability depending on the power mode.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="EduardoZamora_0-1671221744174.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/204756iF5AD53433990F891/image-size/large?v=v2&amp;amp;px=999" role="button" title="EduardoZamora_0-1671221744174.png" alt="EduardoZamora_0-1671221744174.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P lang="es-MX"&gt;In LLS and VLLS power modes, RTC should be fully functional with alternate clock source, provided the selected clock source remains enabled:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="EduardoZamora_1-1671221744176.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/204757iA09A4DE16BC14B4A/image-size/large?v=v2&amp;amp;px=999" role="button" title="EduardoZamora_1-1671221744176.png" alt="EduardoZamora_1-1671221744176.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Could you please take a look at &lt;A href="https://community.nxp.com/t5/Wireless-Connectivity-Knowledge/KW36-Trimming-adjust-of-32kHz-RTC-external-oscillator/ta-p/1099520" target="_blank" rel="noopener"&gt;KW36 - Trimming adjust of 32kHz RTC external oscillator&lt;/A&gt; and confirm if this is helpful for your application? Also, please consult &lt;A href="https://www.nxp.com/docs/en/application-note/AN12180.pdf" target="_blank" rel="noopener"&gt;Kinetis MKW36 Power Consumption Analysis&lt;/A&gt;, here you can find how the hardware is designed and optimized for low-power operation and the expected behavior of BLE applications and the device under low-power modes (Section 4.2.2 shows a partial scenario using HRS demo and describes the main events and phases).&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2022 20:32:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1571385#M14166</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2022-12-16T20:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: [KW36] Which low power mode supports RTC_CLKOUT?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1571561#M14168</link>
      <description>&lt;P&gt;Hello Eduardo Zamora,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I've already read all the documents you told me.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What I want to know is whether RTC_CLKOUT is not available in VLLS[1/2/3] mode.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And is there a way to prevent the signal of RTC_CLKOUT from shaking when switching to the wake-up state?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ayden.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 00:29:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1571561#M14168</guid>
      <dc:creator>ayden</dc:creator>
      <dc:date>2022-12-19T00:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: [KW36] Which low power mode supports RTC_CLKOUT?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1572140#M14186</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P lang="es-MX"&gt;RTC remains functional in all low power modes, but please consider that PTB3 is connected to LED3 and this LED is used by BLE demos as indicator for some application states. The code may be configuring PTB3 as GPIO for this purpose and continuously modifying the state of the pin.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Please, take a look at LED_Init() function, inside ApplMain.c, this function configures pin routing for LED pins.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 23:16:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/KW36-Which-low-power-mode-supports-RTC-CLKOUT/m-p/1572140#M14186</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2022-12-19T23:16:00Z</dc:date>
    </item>
  </channel>
</rss>

