<?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>i.MX ProcessorsのトピックRe: About MMDC Profiling Tool for i.MX6</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664122#M102012</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/yuuki"&gt;yuuki&lt;/A&gt;‌ Have you found how to fix the strange result? May be it is a normal, but I am not sure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jun 2020 18:53:19 GMT</pubDate>
    <dc:creator>sergkot</dc:creator>
    <dc:date>2020-06-11T18:53:19Z</dc:date>
    <item>
      <title>About MMDC Profiling Tool for i.MX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664120#M102010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We want to check a operating rate of CPU and GPU.&lt;BR /&gt;We used mmdc2 command.&lt;/P&gt;&lt;P&gt;We have some questions about MMDC Profiling.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;Q1&amp;gt;&lt;BR /&gt;About the result of the following command.&lt;BR /&gt;What does Utilization mean?&lt;BR /&gt;Is it the average of the operation rate of CPU#0 and CPU#2?&lt;/P&gt;&lt;P&gt;================================================&lt;BR /&gt;root@imx6qdlsolo:/unit_tests# ./mmdc2&lt;BR /&gt;i.MX6DL detected.&lt;BR /&gt;MMDC SUM&lt;/P&gt;&lt;P&gt;MMDC new Profiling results:&lt;BR /&gt;***********************&lt;BR /&gt;Measure time: 500ms&lt;BR /&gt;Total cycles count: 198076320&lt;BR /&gt;Busy cycles count: 30948398&lt;BR /&gt;Read accesses count: 739442&lt;BR /&gt;Write accesses count: 955&lt;BR /&gt;Read bytes count: 47310392&lt;BR /&gt;Write bytes count: 30560&lt;BR /&gt;Avg. Read burst size: 63&lt;BR /&gt;Avg. Write burst size: 32&lt;BR /&gt;Read: 90.24 MB/s / Write: 0.06 MB/s Total: 90.30 MB/s&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;Utilization: 9%&lt;/SPAN&gt;&lt;BR /&gt;Overall Bus Load: 15%&lt;BR /&gt;Bytes Access: 63&lt;BR /&gt;================================================&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Furthermore, we tried the following command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;Q2&amp;gt;&lt;BR /&gt;About the result of the following command.&lt;BR /&gt;Does this show a profiling result of CPU#0?&lt;/P&gt;&lt;P&gt;================================================&lt;BR /&gt;root@imx6qdlsolo:/unit_tests# ./mmdc2 ARM&lt;BR /&gt;i.MX6DL detected.&lt;BR /&gt;MMDC ARM&lt;/P&gt;&lt;P&gt;MMDC new Profiling results:&lt;BR /&gt;***********************&lt;BR /&gt;Measure time: 500ms&lt;BR /&gt;Total cycles count: 198083214&lt;BR /&gt;Busy cycles count: 30898478&lt;BR /&gt;Read accesses count: 3738&lt;BR /&gt;Write accesses count: 552&lt;BR /&gt;Read bytes count: 228288&lt;BR /&gt;Write bytes count: 17664&lt;BR /&gt;Avg. Read burst size: 61&lt;BR /&gt;Avg. Write burst size: 32&lt;BR /&gt;Read: 0.44 MB/s / Write: 0.03 MB/s Total: 0.47 MB/s&lt;BR /&gt;&lt;SPAN style="color: #ff0000;"&gt;Utilization: 0%&lt;/SPAN&gt;&lt;BR /&gt;Overall Bus Load: 15%&lt;BR /&gt;Bytes Access: 57&lt;BR /&gt;================================================&lt;/P&gt;&lt;P&gt;&amp;lt;Q3&amp;gt;&lt;BR /&gt;If &amp;lt;Q2&amp;gt; is Yes,&lt;BR /&gt;Can we check Profiling of CPU#0 and CPU#1 separately?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&amp;lt;Q4&amp;gt;&lt;BR /&gt;According to the source code of the mmdc command, it seems to refer to AXI_ID&lt;BR /&gt;We referred to a reference manual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMX6SDLRM Rev. 2, 04/2015: &lt;BR /&gt; - "Table 45-10. i.MX 6Solo/6DualLite AXI ID" (P.3930)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, AXI_ID for GPU3D1, GPU3D2 and VPU is not explained.&lt;BR /&gt;Would you tell me these AXI_ID?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May I have advice?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Yuuki&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2017 06:08:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664120#M102010</guid>
      <dc:creator>yuuki</dc:creator>
      <dc:date>2017-02-03T06:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: About MMDC Profiling Tool for i.MX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664121#M102011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; The MMDC Profiling tool uses the Profiling Control Registers. Please refer to &lt;BR /&gt;section 45.7 (MMDC Profiling) of i.MX 6Solo/6DualLite Applications Processor &lt;BR /&gt;Reference Manual, Rev. 2, 04/2015. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; MMDC source code may be found in the tests package. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;&amp;lt; &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Flgfiles%2FNMG%2FMAD%2FYOCTO%2Fimx-test-5.7.tar.gz" rel="nofollow" target="_blank"&gt;http://www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-test-5.7.tar.gz&lt;/A&gt;&lt;SPAN&gt; &amp;gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Hope the sources help to clarify parameters, provided by the Profiling tool.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Yuri&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Mar 2017 08:29:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664121#M102011</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2017-03-01T08:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: About MMDC Profiling Tool for i.MX6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664122#M102012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/yuuki"&gt;yuuki&lt;/A&gt;‌ Have you found how to fix the strange result? May be it is a normal, but I am not sure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2020 18:53:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/About-MMDC-Profiling-Tool-for-i-MX6/m-p/664122#M102012</guid>
      <dc:creator>sergkot</dc:creator>
      <dc:date>2020-06-11T18:53:19Z</dc:date>
    </item>
  </channel>
</rss>

