<?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>Kinetis MicrocontrollersのトピックRe: Divided RTC to drive 120Hz display while MCU in low power or stop mode</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Divided-RTC-to-drive-120Hz-display-while-MCU-in-low-power-or/m-p/1416181#M62476</link>
    <description>&lt;P&gt;Looks like this is not possible with Kinetis. Now opting for the display to have its own clock generator - basically a 32K oscillator and an 8-stage flip-flop. It'll consume 1-2uA, so is within the IoT energy budget.&amp;nbsp; Downside is that it adds $2 to the per-board cost.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Feb 2022 20:20:17 GMT</pubDate>
    <dc:creator>deniscollis</dc:creator>
    <dc:date>2022-02-18T20:20:17Z</dc:date>
    <item>
      <title>Divided RTC to drive 120Hz display while MCU in low power or stop mode</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Divided-RTC-to-drive-120Hz-display-while-MCU-in-low-power-or/m-p/1415555#M62457</link>
      <description>&lt;P&gt;Looking for inspiration...&lt;/P&gt;&lt;P&gt;IoT application. I have a K81/K82 that drives a JDI display.&amp;nbsp; The display has pixel memory, and so will hold the display image as long as&amp;nbsp; a nominal 120Hz signal is present on its clock-in pin. Currently the plan is for the display clock to be generated by a FreeRTOS 8ms periodic task pulsing a GPIO pin. I'd like relieve the RTOS of this task, instead driving the 120Hz (or 128Hz, probably) from the TPM.&amp;nbsp; In addition, I want to clock the TPM from the RTC Oscillator.&amp;nbsp; This way I hope to stop the K8x core, but leave the TMP peripheral running.&lt;/P&gt;&lt;P&gt;Is this doable?&lt;/P&gt;&lt;P&gt;(The ultimate goal is the minimum energy consumption)&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Denis&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 19:52:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Divided-RTC-to-drive-120Hz-display-while-MCU-in-low-power-or/m-p/1415555#M62457</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2022-02-17T19:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Divided RTC to drive 120Hz display while MCU in low power or stop mode</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Divided-RTC-to-drive-120Hz-display-while-MCU-in-low-power-or/m-p/1416181#M62476</link>
      <description>&lt;P&gt;Looks like this is not possible with Kinetis. Now opting for the display to have its own clock generator - basically a 32K oscillator and an 8-stage flip-flop. It'll consume 1-2uA, so is within the IoT energy budget.&amp;nbsp; Downside is that it adds $2 to the per-board cost.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2022 20:20:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Divided-RTC-to-drive-120Hz-display-while-MCU-in-low-power-or/m-p/1416181#M62476</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2022-02-18T20:20:17Z</dc:date>
    </item>
  </channel>
</rss>

