<?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のトピックProblems with the meaning of Flash Clock and Bus Clock</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605357#M35673</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, just got my first lovely FRDM-KV10Z board.&lt;/P&gt;&lt;P&gt;I have some question about the clocks. Hope you guys don't mind this is my first time using Cortex MX.&lt;/P&gt;&lt;P&gt;The maximal allowed settings:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Core Clock = System Clock = 75Mhz.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Flash/Bus clock&amp;nbsp;(the same here in KV10Z) = 25MHz&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This seems to be wired for me.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does that mean the arm core can run in 75MHz,&amp;nbsp;but&amp;nbsp;the instruction fetching speed is only up to 25MHz??&lt;/P&gt;&lt;P&gt;Or at least the core is in wait state most of the time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I made a simple test, using system tick module to count how many&amp;nbsp;system ticks past during some instruction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, 50 __NOP() &amp;nbsp;instructions took about 80 system ticks.&lt;/P&gt;&lt;P&gt;This made me even more confused, I suppose 3 system ticks will execute one instruction.&lt;/P&gt;&lt;P&gt;However, this is good news for I originally supposed that it would take about 150 system ticks due to the core/bus clock ration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone make some explanation about this?&lt;/P&gt;&lt;P&gt;How can I estimate the instruction fetching speed, and make sure that the core is not in wait state?&lt;/P&gt;&lt;P&gt;Do I misunderstand something about this?&lt;/P&gt;&lt;P&gt;Thanks for reading this post!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Mar 2017 01:15:51 GMT</pubDate>
    <dc:creator>zhitailiu</dc:creator>
    <dc:date>2017-03-22T01:15:51Z</dc:date>
    <item>
      <title>Problems with the meaning of Flash Clock and Bus Clock</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605357#M35673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, just got my first lovely FRDM-KV10Z board.&lt;/P&gt;&lt;P&gt;I have some question about the clocks. Hope you guys don't mind this is my first time using Cortex MX.&lt;/P&gt;&lt;P&gt;The maximal allowed settings:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Core Clock = System Clock = 75Mhz.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Flash/Bus clock&amp;nbsp;(the same here in KV10Z) = 25MHz&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This seems to be wired for me.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does that mean the arm core can run in 75MHz,&amp;nbsp;but&amp;nbsp;the instruction fetching speed is only up to 25MHz??&lt;/P&gt;&lt;P&gt;Or at least the core is in wait state most of the time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I made a simple test, using system tick module to count how many&amp;nbsp;system ticks past during some instruction.&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, 50 __NOP() &amp;nbsp;instructions took about 80 system ticks.&lt;/P&gt;&lt;P&gt;This made me even more confused, I suppose 3 system ticks will execute one instruction.&lt;/P&gt;&lt;P&gt;However, this is good news for I originally supposed that it would take about 150 system ticks due to the core/bus clock ration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone make some explanation about this?&lt;/P&gt;&lt;P&gt;How can I estimate the instruction fetching speed, and make sure that the core is not in wait state?&lt;/P&gt;&lt;P&gt;Do I misunderstand something about this?&lt;/P&gt;&lt;P&gt;Thanks for reading this post!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2017 01:15:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605357#M35673</guid>
      <dc:creator>zhitailiu</dc:creator>
      <dc:date>2017-03-22T01:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with the meaning of Flash Clock and Bus Clock</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605358#M35674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First and foremost the flash is 2 instructions wide.&amp;nbsp; For this particular test, 50 instructions is 25 fetches, or 1us.&amp;nbsp; In said 1us are 75 core-ticks.&amp;nbsp; Cortex-M is 'Thumb instruction set', optimized at 16bits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The flash-interface-system also has some fetch/'cache' helpers to improve flash-execute performance.&amp;nbsp; Many instructions will involve access-cycles to 'non Flash', like RAM/Stack and peripherals, so 'real work' will better-fill the CPU time than a linear sequence of NOPs.&amp;nbsp; That all being said, for truly 'execution speed critical' operations you might benefit running those routines in RAM (look for the best RAM-block to put that in, maybe with consideration for where your stack is).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2017 02:54:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605358#M35674</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2017-03-22T02:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with the meaning of Flash Clock and Bus Clock</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605359#M35675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great thanks!&lt;BR /&gt;Now I got it!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2017 05:08:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Problems-with-the-meaning-of-Flash-Clock-and-Bus-Clock/m-p/605359#M35675</guid>
      <dc:creator>zhitailiu</dc:creator>
      <dc:date>2017-03-22T05:08:55Z</dc:date>
    </item>
  </channel>
</rss>

