<?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: DDR Controller data abort recovery? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/DDR-Controller-data-abort-recovery/m-p/224590#M15626</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;&amp;nbsp; According to the i.MX6 Reference Manual : &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;“The following registers in the MMDC define the DDR address space:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDMISC[DDR_4_BANK]—Defines either 4 or 8 banks in the DDR device&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[DSIZ]—Defines the DDR data bus width of x16, x32 or x64&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDMISC[BI]—Defines whether bank interleaving is on or off&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[COL]—Defines the column size of the DDR device&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[ROW]—Defines the row size of the DDR device”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;Also, “It is optional to configure the partition between the chip selects through&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;MDASP[CS0_END]”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;&amp;nbsp; Generally for an access to an address, which is not used (non-covered) by internal &lt;BR /&gt; i.MX6 modules, we can expect ARM data abort exception, but the following&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;statement (NOTE) may be considered as recommendation to avoid such accesses :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;“In cases where this is an access to a non-initialized or disconnected chip select, &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;behavior may be unexpected”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;If it is required to define memory size – it makes sense to test it without checking&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;addresses, that are out of range. It is enough to test (quite accessible) memory region &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;via writing and consequent reading data, assuming they are equal for real memory.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Oct 2013 09:15:07 GMT</pubDate>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2013-10-28T09:15:07Z</dc:date>
    <item>
      <title>DDR Controller data abort recovery?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR-Controller-data-abort-recovery/m-p/224589#M15625</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;is there anything I need to do with the DDR controller after it has caused a data abort through accessing non existent addresses?&amp;nbsp; It seems happy on writes, but seems to give a data abort on reads.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2013 18:10:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR-Controller-data-abort-recovery/m-p/224589#M15625</guid>
      <dc:creator>johnballance</dc:creator>
      <dc:date>2013-10-22T18:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: DDR Controller data abort recovery?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR-Controller-data-abort-recovery/m-p/224590#M15626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;&amp;nbsp; According to the i.MX6 Reference Manual : &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;“The following registers in the MMDC define the DDR address space:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDMISC[DDR_4_BANK]—Defines either 4 or 8 banks in the DDR device&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[DSIZ]—Defines the DDR data bus width of x16, x32 or x64&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDMISC[BI]—Defines whether bank interleaving is on or off&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[COL]—Defines the column size of the DDR device&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;• MDCTL[ROW]—Defines the row size of the DDR device”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;Also, “It is optional to configure the partition between the chip selects through&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;MDASP[CS0_END]”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;&amp;nbsp; Generally for an access to an address, which is not used (non-covered) by internal &lt;BR /&gt; i.MX6 modules, we can expect ARM data abort exception, but the following&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;statement (NOTE) may be considered as recommendation to avoid such accesses :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;“In cases where this is an access to a non-initialized or disconnected chip select, &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;behavior may be unexpected”.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;If it is required to define memory size – it makes sense to test it without checking&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;addresses, that are out of range. It is enough to test (quite accessible) memory region &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Verdana','sans-serif';"&gt;via writing and consequent reading data, assuming they are equal for real memory.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Oct 2013 09:15:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR-Controller-data-abort-recovery/m-p/224590#M15626</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2013-10-28T09:15:07Z</dc:date>
    </item>
  </channel>
</rss>

