<?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>LayerscapeのトピックRe: Clarification on erratum</title>
    <link>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2186072#M16205</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;There isn't a public description of the register available.&lt;/P&gt;
&lt;P&gt;Wording of the erratum A-008822 describes the issue in detail.&lt;BR /&gt;As stated, that workaround changes AXI slave response for all error scenarios on non-posted requests from default OKAY to ERROR.&lt;/P&gt;
&lt;P&gt;Additional details cannot be provided to the customer because the PCIe IP internals are confidential.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
    <pubDate>Tue, 14 Oct 2025 22:21:16 GMT</pubDate>
    <dc:creator>Oswalag</dc:creator>
    <dc:date>2025-10-14T22:21:16Z</dc:date>
    <item>
      <title>Clarification on erratum</title>
      <link>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2183979#M16182</link>
      <description>&lt;P&gt;I have been reviewing A-008822 in the LS1028A errata (LS1028ACE, Rev2, 2/2023). In A-008822, the workaround asks for a write to the PCIe configurations space offset 8D0h to occur.&lt;/P&gt;&lt;P&gt;I looked in the LS1028A TRM and I was not able to find this register listed.&lt;/P&gt;&lt;P&gt;Is it possible to get the definition of this register. I would like to understand the workaround; in case someone asks.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Oct 2025 15:55:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2183979#M16182</guid>
      <dc:creator>rhaas</dc:creator>
      <dc:date>2025-10-10T15:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on erratum</title>
      <link>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2186072#M16205</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;There isn't a public description of the register available.&lt;/P&gt;
&lt;P&gt;Wording of the erratum A-008822 describes the issue in detail.&lt;BR /&gt;As stated, that workaround changes AXI slave response for all error scenarios on non-posted requests from default OKAY to ERROR.&lt;/P&gt;
&lt;P&gt;Additional details cannot be provided to the customer because the PCIe IP internals are confidential.&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Oct 2025 22:21:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2186072#M16205</guid>
      <dc:creator>Oswalag</dc:creator>
      <dc:date>2025-10-14T22:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on erratum</title>
      <link>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2187551#M16211</link>
      <description>&lt;P&gt;Thank you for the information.&lt;BR /&gt;&lt;BR /&gt;I was wondering if any 'write enable' bit needs to be set before writing this data, similar to MISC_CONTROL_1_OFF.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 16 Oct 2025 13:01:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Clarification-on-erratum/m-p/2187551#M16211</guid>
      <dc:creator>rhaas</dc:creator>
      <dc:date>2025-10-16T13:01:11Z</dc:date>
    </item>
  </channel>
</rss>

