<?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>T-Series中的主题 Re: T2080 ATMU setup for PCIe1</title>
    <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2399036#M5464</link>
    <description>&lt;P&gt;I ran into something similar while working through a PCIe configuration, and checking the documentation carefully made a big difference. I also compared a few hardware reference details with &lt;A href="https://pinalcountyassessor.org" target="_self"&gt;Pinal Assessor Portal&lt;/A&gt; while organizing related information for another project. Hopefully your setup goes smoothly, and I'd be interested to hear what ended up resolving the issue. Thanks for bringing up this topic.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Jul 2026 05:17:31 GMT</pubDate>
    <dc:creator>jameswilson935</dc:creator>
    <dc:date>2026-07-27T05:17:31Z</dc:date>
    <item>
      <title>T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1462491#M4436</link>
      <description>&lt;P&gt;I have 2 T2080s attached to each other on PCIe. I have 1 setup as the RC and the other setup as the EP. I am only testing traffic (reads/writes) to the EP from the RC. When I run the test for connections between PCIe2 or PCIe4 the test functions correctly and data written to the EP is echoed back correctly on reads from the EP. The test is simply mapping to DRAM on the EP's T2080. So the ATMU registers, LAWs, TLBs are set up correctly.&lt;/P&gt;&lt;P&gt;However, the test fails when using PCIe1. The configuration is exactly the same for all three controller setups. The SW simply is compiled to change the bus from PCIe4 to PCIe1 with appropriate memory changes to the controllers. We have a PCIe analyzer on the bus. We see the writes and reads complete as expected. But the data read back does not represent the data written in the prior step by the RC. When we break in with an emulator from the RC and examine the memory space mapped to the EP DRAM (BAR1) through the PCIe bus, it appears to be a repeating pattern. When I break in to the T2080 EP processor and examine DRAM it is unchanged from the original values written during DRAM init. What is different about PCIe1. I realize that PCIe1 supports SR-IOV, but I do not have that enabled.&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 13:46:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1462491#M4436</guid>
      <dc:creator>scottgerhold</dc:creator>
      <dc:date>2022-05-23T13:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1465196#M4438</link>
      <description>&lt;DIV id="b0p1o74i0i2r1" class="fm-textarea iwps_edit_box -iwps_edit_box fm_object_74 -fm_object_74 v-has-width v-has-height fm-inactive"&gt;
&lt;DIV class="inner_border"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="b0p1o76i0i2r1" class="v-csslayout v-layout v-widget iwp-css-layout-common-style v-csslayout-iwp-css-layout-common-style iwps_group v-csslayout-iwps_group v-has-width v-has-height"&gt;
&lt;DIV id="b0p1o77i0i2r1" class="v-csslayout v-layout v-widget iwps_container v-csslayout-iwps_container hand-cursor v-csslayout-hand-cursor v-has-width v-has-height fm-inactive"&gt;
&lt;DIV class="v-ddwrapper v-widget inner_border v-ddwrapper-inner_border v-has-width v-has-height"&gt;
&lt;DIV class="v-csslayout v-layout v-widget iwp-css-layout-common-style v-csslayout-iwp-css-layout-common-style fm-cont-pos v-csslayout-fm-cont-pos v-has-width v-has-height"&gt;
&lt;DIV class="v-embedded v-widget"&gt;&lt;SPAN&gt;Please provide me the register dumps for PCIe interface, both RC and EP.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="b0p1o78i0i2r1" class="fm-textarea iwps_text_area -iwps_text_area fm_object_78 -fm_object_78 show-scrollbars -show-scrollbars v-has-width v-has-height fm-inactive"&gt;
&lt;DIV class="inner_border"&gt;
&lt;DIV class="text" tabindex="0"&gt;Provide the full console logs&lt;BR /&gt;PEX analyser dumps&lt;/DIV&gt;
&lt;DIV class="text" tabindex="0"&gt;
&lt;DIV id="b0p1o74i0i2r1" class="fm-textarea iwps_edit_box -iwps_edit_box fm_object_74 -fm_object_74 v-has-width v-has-height fm-inactive"&gt;
&lt;DIV class="inner_border"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="b0p1o78i0i2r1" class="fm-textarea iwps_text_area -iwps_text_area fm_object_78 -fm_object_78 show-scrollbars -show-scrollbars v-has-width v-has-height fm-inactive"&gt;
&lt;DIV class="inner_border"&gt;
&lt;DIV class="text" tabindex="0"&gt;&lt;SPAN&gt;Register dump of LAW registers is also required.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 27 May 2022 02:08:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1465196#M4438</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2022-05-27T02:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1468293#M4446</link>
      <description>&lt;P&gt;I can provide the RC and EP dumps along with the LAW registers. Do you have a specific address range you want for the PCIe interface dumps? Any hidden registers you want (I know they exist as NXP has told us to change a couple in the past). Are you asking for both the normal registers and the PCIe configuration memory space (that is a little harder to get, but I can dump the screen from Lauterbach – which is 98% correct).&lt;/P&gt;&lt;P&gt;I am not sure what exactly you are asking for with the PEX analyzer dumps. If you are just looking for proof that what I said is true (that reads don’t return what was written, I can show that).&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 15:37:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1468293#M4446</guid>
      <dc:creator>scottgerhold</dc:creator>
      <dc:date>2022-06-02T15:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1468294#M4447</link>
      <description>&lt;P&gt;I can provide the RC and EP dumps along with the LAW registers. Do you have a specific address range you want for the PCIe interface dumps? Any hidden registers you want (I know they exist as NXP has told us to change a couple in the past). Are you asking for both the normal registers and the PCIe configuration memory space (that is a little harder to get, but I can dump the screen from Lauterbach – which is 98% correct).&lt;/P&gt;&lt;P&gt;I am not sure what exactly you are asking for with the PEX analyzer dumps. If you are just looking for proof that what I said is true (that reads don’t return what was written, I can show that).&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 15:37:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1468294#M4447</guid>
      <dc:creator>scottgerhold</dc:creator>
      <dc:date>2022-06-02T15:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1474929#M4455</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I can provide the RC and EP dumps along with the LAW registers. Do you have a specific address range you want for the PCIe interface dumps? Any hidden registers you want (I know they exist as NXP has told us to change a couple in the past). Are you asking for both the normal registers and the PCIe configuration memory space (that is a little harder to get, but I can dump the screen from Lauterbach – which is 98% correct).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;[NXP] Yes. We want the dumps for the normal registers and the PCIe configuration space. Do this activity for both RC and EP. You may refer to Table 2-5. CCSR Block Base Address Map from T2080RM for PCIe offset. In addition, the register dump of LAW registers is also required. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am not sure what exactly you are asking for with the PEX analyzer dumps. If you are just looking for proof that what I said is true (that reads don’t return what was written, I can show that).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;[NXP] We need PEX analyzer dumps in the failing scenario, i.e., when reads don’t return the written data. It would be great if you also shared analyzer dumps in the passing case to compare. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2022 02:31:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/1474929#M4455</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2022-06-16T02:31:57Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2398956#M5461</link>
      <description>&lt;P&gt;The T2080 ATMU setup for PCIe1 looks like an interesting configuration topic, especially for those working with system hardware and performance tuning. It is useful to share detailed resources that help users find reliable technical and documentation related information. For additional reference I found &lt;A href="https://sedgwickcountycourts.org" target="_self"&gt;Sedgwick Court Hearings&lt;/A&gt; helpful for exploring organized public information resources. Clear explanations and shared experiences can make complex setups easier for others to follow and troubleshoot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jul 2026 07:34:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2398956#M5461</guid>
      <dc:creator>sophiaanderson</dc:creator>
      <dc:date>2026-07-26T07:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2398972#M5463</link>
      <description>&lt;P&gt;The details shared about the T2080 ATMU setup for PCIe1 provide useful information for anyone exploring hardware configuration and optimization. I found the discussion informative and more related information can be explored through&amp;nbsp;&lt;A href="https://dallascountyassessor.org" target="_self"&gt;Dallas Assessment Data&lt;/A&gt; for additional reference. Tracking configuration methods and technical updates can help improve understanding of system performance. Appreciate the insights shared here and look forward to more discussions on similar topics.&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jul 2026 09:55:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2398972#M5463</guid>
      <dc:creator>samuelwhite</dc:creator>
      <dc:date>2026-07-26T09:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2399036#M5464</link>
      <description>&lt;P&gt;I ran into something similar while working through a PCIe configuration, and checking the documentation carefully made a big difference. I also compared a few hardware reference details with &lt;A href="https://pinalcountyassessor.org" target="_self"&gt;Pinal Assessor Portal&lt;/A&gt; while organizing related information for another project. Hopefully your setup goes smoothly, and I'd be interested to hear what ended up resolving the issue. Thanks for bringing up this topic.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jul 2026 05:17:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2399036#M5464</guid>
      <dc:creator>jameswilson935</dc:creator>
      <dc:date>2026-07-27T05:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: T2080 ATMU setup for PCIe1</title>
      <link>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2401039#M5467</link>
      <description>&lt;P&gt;The T2080 ATMU setup for PCIe1 looks like an interesting configuration, especially for getting the interface working smoothly. I’d be curious to know if there are any specific settings or checks needed during the setup process. For readers researching related public information &lt;A href="https://monroecountycourt.org" target="_self"&gt;Monroe Court Archives&lt;/A&gt;&amp;nbsp;may also be worth reviewing. Overall, the setup details here are helpful for anyone working with this type of PCIe configuration.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2026 05:28:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T2080-ATMU-setup-for-PCIe1/m-p/2401039#M5467</guid>
      <dc:creator>hannahreed36</dc:creator>
      <dc:date>2026-08-01T05:28:09Z</dc:date>
    </item>
  </channel>
</rss>

