<?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>topic Re: i.MXRT1021 ETM trace port size? in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939855#M4017</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-content-finding="Community" data-userid="344809" data-username="chris.eyre@emerson.com" href="https://community.nxp.com/people/chris.eyre@emerson.com"&gt;Chris Eyre&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and &lt;BR /&gt;for the opportunity to serve you.&lt;BR /&gt;I've also checked the value of &lt;STRONG&gt;TPIU_SSPSR (Supported Parallel Port Size Register)&lt;/STRONG&gt; for confirmation, it seems that the RT1020 only support the 1-bit trace port, however, I still need to confirm it with the AE team and inform you if I get some replies from them.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/81891iD525F5CC748C15B9/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&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 style="min- padding: 0px;"&gt;&amp;nbsp;&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>Fri, 19 Jul 2019 03:23:04 GMT</pubDate>
    <dc:creator>jeremyzhou</dc:creator>
    <dc:date>2019-07-19T03:23:04Z</dc:date>
    <item>
      <title>i.MXRT1021 ETM trace port size?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939854#M4016</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the supported ETM trace port size on the RT1021? The 1020 reference manual suggests that TRACEDATA can be 1, 2, or 4 bits&amp;nbsp;and 4-bit mode is recommended (see 7.2.2.2 CoreSight trace port interface). However, this seems to conflict with the actual behavior of the device. With a debug connection to the 1021 evaluation kit. I observed that the ARM TPIU Supported Port Size register is fixed to 1 (0xE0040000=0x00000001). If my understanding is correct, this register indicates that only PORT_SIZE=1 is supported by the device and this cannot be changed. My evaluation kit has been modified to support ETM trace and I was able to verify that 1-bit ETM trace is working, but not 2-bit or 4-bit mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are evaluating the 1021 as a possible migration&amp;nbsp;from the K24. With the k24 we are using 4-bit TRACEDATA&amp;nbsp; mode and this seems to meet our needs. On the k24 I confirmed that the Supported Port size register indicates 4-bit mode is supported. ETM trace is important for our applications so I am concerned with the apparent limit of 1-bit ETM Trace and at this point it is unclear whether this will cause some kind of trace data bottleneck.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jul 2019 17:01:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939854#M4016</guid>
      <dc:creator>chris_eyre</dc:creator>
      <dc:date>2019-07-18T17:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: i.MXRT1021 ETM trace port size?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939855#M4017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-content-finding="Community" data-userid="344809" data-username="chris.eyre@emerson.com" href="https://community.nxp.com/people/chris.eyre@emerson.com"&gt;Chris Eyre&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and &lt;BR /&gt;for the opportunity to serve you.&lt;BR /&gt;I've also checked the value of &lt;STRONG&gt;TPIU_SSPSR (Supported Parallel Port Size Register)&lt;/STRONG&gt; for confirmation, it seems that the RT1020 only support the 1-bit trace port, however, I still need to confirm it with the AE team and inform you if I get some replies from them.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/81891iD525F5CC748C15B9/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&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 style="min- padding: 0px;"&gt;&amp;nbsp;&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>Fri, 19 Jul 2019 03:23:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939855#M4017</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2019-07-19T03:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: i.MXRT1021 ETM trace port size?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939856#M4018</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;Strange, in the SDK you clearly see you have 4 TRACE pin:&lt;/P&gt;&lt;PRE class="language-c line-numbers"&gt;&lt;CODE&gt;Search &lt;SPAN class="string token"&gt;"trace"&lt;/SPAN&gt; &lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="number token"&gt;6&lt;/SPAN&gt; hits in &lt;SPAN class="number token"&gt;1&lt;/SPAN&gt; file&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
 C&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt;\Users\nxa22167\AppData\Local\Temp\&lt;SPAN class="number token"&gt;1&lt;/SPAN&gt;\Temp1_SDK_2&lt;SPAN class="number token"&gt;.6&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;1_EVK&lt;SPAN class="operator token"&gt;-&lt;/SPAN&gt;MIMXRT1020&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;zip\devices\MIMXRT1021\drivers\fsl_iomuxc&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;h &lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="number token"&gt;6&lt;/SPAN&gt; hits&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;466&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_10_ARM_CM7_TRACE_CLK &lt;SPAN class="number token"&gt;0x401F80E4U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F8258U&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;474&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_11_ARM_CM7_TRACE_SWO &lt;SPAN class="number token"&gt;0x401F80E8U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F825CU&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;482&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_12_ARM_CM7_TRACE00 &lt;SPAN class="number token"&gt;0x401F80ECU&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F8260U&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;491&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_13_ARM_CM7_TRACE01 &lt;SPAN class="number token"&gt;0x401F80F0U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F8264U&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;500&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_14_ARM_CM7_TRACE02 &lt;SPAN class="number token"&gt;0x401F80F4U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F8268U&lt;/SPAN&gt;
 Line &lt;SPAN class="number token"&gt;509&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt; #define IOMUXC_GPIO_AD_B0_15_ARM_CM7_TRACE03 &lt;SPAN class="number token"&gt;0x401F80F8U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x6U&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; &lt;SPAN class="number token"&gt;0x401F826CU&lt;/SPAN&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the i.MXRT1050 it is the same and the app note 12437 descritbe it page :&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN12437.pdf" rel="nofollow noopener noreferrer" title="https://www.nxp.com/docs/en/application-note/AN12437.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN12437.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;V.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Oct 2019 08:39:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939856#M4018</guid>
      <dc:creator>Aubineau_FAE</dc:creator>
      <dc:date>2019-10-04T08:39:19Z</dc:date>
    </item>
    <item>
      <title>Re: i.MXRT1021 ETM trace port size?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939857#M4019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN class=""&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="26921" data-username="vincent.aubineau" href="https://community.nxp.com/people/vincent.aubineau"&gt;vincent.aubineau&lt;/A&gt;&lt;/SPAN&gt;,&lt;/P&gt;&lt;P&gt;Thanks for your reply,&lt;BR /&gt;I think the post can answer your inquiry.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/511596"&gt;RT1052/RT1061 trace port width&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&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 style="min- padding: 0px;"&gt;&amp;nbsp;&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, 08 Oct 2019 03:17:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MXRT1021-ETM-trace-port-size/m-p/939857#M4019</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2019-10-08T03:17:39Z</dc:date>
    </item>
  </channel>
</rss>

