<?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: ETB access within the processor</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031496#M56529</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks in advance, Diego!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to clarify that it turns out the even through ETB registers, I cannot read the ETB RAM. Actually, I can only access a limited number of ETB registers. After checking the manual, BIT 2 of ETB control registers controls whether access via AHB is allowed. It is 0 which only allows JATG access.&lt;/P&gt;&lt;P&gt;Moreover, I found that the NXP ETB is not fully consistent with the ARM document. For example, the&amp;nbsp;RAM width register is 0 while it should be&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;b100000 or&amp;nbsp;b011000. Can you point me to the appropriate document to get more details of NXP ETB implementation?&lt;/P&gt;&lt;P class=""&gt;&lt;/P&gt;&lt;P class=""&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Feb 2020 23:39:34 GMT</pubDate>
    <dc:creator>leguan1</dc:creator>
    <dc:date>2020-02-06T23:39:34Z</dc:date>
    <item>
      <title>ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031494#M56527</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 writing a program to read the ETB memory from a task on a frdm-k64f board. I can achieve this by using the AHB interface to read the ETB data registers indirectly. However, it seems to be&amp;nbsp;inefficient because I can only access 1 word once. Based on the ARM ETB manual (&lt;A class="link-titled" href="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0242b/index.html" title="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0242b/index.html"&gt;ARM Information Center&lt;/A&gt;&amp;nbsp;), the ETB trace&amp;nbsp;RAM is also aliased directly into the system memory space. The base addresses of the ETB registers and the trace RAM are defined by the AHB decoder. While I can find the base address of the ETB&amp;nbsp;registers easily, I cannot find the base address of the trace RAM. I searched both the ARM documents and the&amp;nbsp;K64 Sub-Family Reference Manual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any clue is appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Feb 2020 19:05:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031494#M56527</guid>
      <dc:creator>leguan1</dc:creator>
      <dc:date>2020-02-02T19:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031495#M56528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, Leguan&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I´m currently working to provide you an answer, as soon I get useful information I' let you know.&amp;nbsp;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Diego&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Feb 2020 23:17:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031495#M56528</guid>
      <dc:creator>diego_charles</dc:creator>
      <dc:date>2020-02-04T23:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031496#M56529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks in advance, Diego!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to clarify that it turns out the even through ETB registers, I cannot read the ETB RAM. Actually, I can only access a limited number of ETB registers. After checking the manual, BIT 2 of ETB control registers controls whether access via AHB is allowed. It is 0 which only allows JATG access.&lt;/P&gt;&lt;P&gt;Moreover, I found that the NXP ETB is not fully consistent with the ARM document. For example, the&amp;nbsp;RAM width register is 0 while it should be&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;b100000 or&amp;nbsp;b011000. Can you point me to the appropriate document to get more details of NXP ETB implementation?&lt;/P&gt;&lt;P class=""&gt;&lt;/P&gt;&lt;P class=""&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Feb 2020 23:39:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031496#M56529</guid>
      <dc:creator>leguan1</dc:creator>
      <dc:date>2020-02-06T23:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031497#M56530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Hello&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Leguan,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Sorry for my late response.&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Currently, there are no software examples and low-level implementations that I could provide you that match your application.&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Besides the reference manual, by this point, I´m not sure if you are aware of the &amp;nbsp;&amp;nbsp;NXP´s MCUxpresso guide offers &lt;A href="https://www.nxp.com/docs/en/quick-reference-guide/MCUXpresso_IDE_Instruction_Trace.pdf"&gt;MCUXpresso IDE Instruction Trace Guide&lt;/A&gt;.&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Chapter&amp;nbsp;&lt;A href="https://www.nxp.com/docs/en/quick-reference-guide/MCUXpresso_IDE_Instruction_Trace.pdf#page=14"&gt;3.3 Embedded Trace Buffer (ETB)&lt;/A&gt; provides more details in the ETB, including techniques to configure the buffer, but not for a specific MCU.&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;I have to mention that the read of the trace data from the ETB &amp;nbsp;is made trough a &amp;nbsp;LinkServer connection I&amp;nbsp; (including many other CMSIS-DAP probes,&amp;nbsp; OpenSDA circuits) &amp;nbsp;during a debug session in MCUXpresso, which&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;differs from reading the ETB during a task.&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;About the differences that you notice among the ARM documentation, you are right,&amp;nbsp; since the implementation of ETM and ETB is vendor-specific. &amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;&lt;/P&gt;&lt;P style="margin: 0in; margin-bottom: .0001pt;"&gt;Best regards, Diego.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2020 22:07:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031497#M56530</guid>
      <dc:creator>diego_charles</dc:creator>
      <dc:date>2020-02-11T22:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031498#M56531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Diego,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response. I know the MCUXpresso IDE Instruction Trace Guide and it works perfectly with the hardware debugger.&amp;nbsp; It seems there is no way to read the buffer directly from inside the target.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2020 22:37:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031498#M56531</guid>
      <dc:creator>leguan1</dc:creator>
      <dc:date>2020-02-11T22:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: ETB access within the processor</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031499#M56532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, Leguan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I could help in something else, please let me know,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, Diego.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2020 20:55:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/ETB-access-within-the-processor/m-p/1031499#M56532</guid>
      <dc:creator>diego_charles</dc:creator>
      <dc:date>2020-02-12T20:55:22Z</dc:date>
    </item>
  </channel>
</rss>

