<?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: PCIE error PEX_ERR_DR[CRST] in P-Series</title>
    <link>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319232#M1302</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The value of LTSSM State Status Register is 0x16 (state L0) which means link training is successful. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does it mean that communication with the target is fine ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it seems when we start configuration space access then the target does not reply. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Jun 2014 08:48:08 GMT</pubDate>
    <dc:creator>t_alex</dc:creator>
    <dc:date>2014-06-17T08:48:08Z</dc:date>
    <item>
      <title>PCIE error PEX_ERR_DR[CRST]</title>
      <link>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319230#M1300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We configured our custom P3041 board as root complex mode, and connect via PCB to another PCIe device. &lt;/P&gt;&lt;P&gt;From u-boot, when we do enumeration, we can see another bus appear (bus 1). &lt;/P&gt;&lt;P&gt;Trying to read from configuration space of the other device will result in 0xffffffff no matter which address.&lt;/P&gt;&lt;P&gt;And error PEX_ERR_DR[CRST]&amp;nbsp; is detected. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What should I do to know more about the error details to troubleshoot the problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jun 2014 05:11:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319230#M1300</guid>
      <dc:creator>t_alex</dc:creator>
      <dc:date>2014-06-16T05:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: PCIE error PEX_ERR_DR[CRST]</title>
      <link>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319231#M1301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Quote from the chip reference manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="jiveImage" height="145" src="https://community.nxp.com/thread/325339" width="650" /&gt;&lt;/P&gt;&lt;P&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42972i2856A8EAEC35CBB5/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The controller always retries the transaction as soon as possible until a status other than CRS is returned. However, if a CRS status is returned after the configuration retry timeout(PEXCONF_RTY_TOR) timer expires, then the controller aborts the transaction and sends all 1s (0xFFFF_FFFF) data back to requester.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I think you need to determine that something is wrong with the target of the request&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jun 2014 08:16:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319231#M1301</guid>
      <dc:creator>lunminliang</dc:creator>
      <dc:date>2014-06-17T08:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: PCIE error PEX_ERR_DR[CRST]</title>
      <link>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319232#M1302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The value of LTSSM State Status Register is 0x16 (state L0) which means link training is successful. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does it mean that communication with the target is fine ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it seems when we start configuration space access then the target does not reply. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jun 2014 08:48:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319232#M1302</guid>
      <dc:creator>t_alex</dc:creator>
      <dc:date>2014-06-17T08:48:08Z</dc:date>
    </item>
    <item>
      <title>Re: PCIE error PEX_ERR_DR[CRST]</title>
      <link>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319233#M1303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the specification, "L0 is the normal operational state where data and control packets can be transmitted and received. All power management states are entered from this state."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not expert on PCIE, IMHO, this indicates the physical commnication is fine. Your request target (EP) should has problem. You may send your complete U-boot log to look into.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jun 2014 07:35:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/PCIE-error-PEX-ERR-DR-CRST/m-p/319233#M1303</guid>
      <dc:creator>lunminliang</dc:creator>
      <dc:date>2014-06-20T07:35:21Z</dc:date>
    </item>
  </channel>
</rss>

