<?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: NAND Flash Boot Process Question in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576308#M4128</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply Pavel, would you happen to know if the MPC-5125 NFC&amp;nbsp;power on reset logic uses the RB (ready/busy) signal from the NAND flash part to determine when it is ok to send the reset command (0xFF) to the flash and start the power up read of the bootloader code? The microcontroller reference manual (section 23, Nand Flash Controller) is pretty thin on details of how the boot process and timing works. It does&amp;nbsp;mention sending the flash reset command and&amp;nbsp;the 4 separate reads from 4 different flash&amp;nbsp;locations, but that's about it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Sep 2016 17:26:08 GMT</pubDate>
    <dc:creator>Tim562</dc:creator>
    <dc:date>2016-09-06T17:26:08Z</dc:date>
    <item>
      <title>NAND Flash Boot Process Question</title>
      <link>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576306#M4126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm troubleshooting an intermittent boot problem on an MPC-5125 processor&amp;nbsp;booting from&amp;nbsp;a Micron NAND flash part. The processor manual states that the&amp;nbsp;processor&amp;nbsp;boot logic attempts to read the bootstrap utility from row address 0 at the start of the flash device (Block_0, Page_0, Column_0). At this address it does a burst read of 4 pages (about 4K of data). If no ECC failures, the boot read is considered successful and the process terminates. BUT, if an ECC failure is detected, the manual states that additional reads will be conducted at row address 256, 512 and 768. Here's my question, "what address is being referred to when the words "row address" are used?" My understanding of "row address" is that it represents the combined Column, page, block and LUN values. Since the&amp;nbsp;bottom 16 bits of the full 5 byte row address represent the column&amp;nbsp;address(&lt;EM&gt;byte within a page&lt;/EM&gt;), is this implying 4K reads are made&amp;nbsp;from&amp;nbsp;columns 0, 256, 512 or 768 of the first page, block, LUN? If that's the case it's not very useful for redundancy&amp;nbsp;since the 256 bytes between row addresses doesn't allow the storage of a complete bootstrap utility (remember 4k is read from each start address).&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would make more sense if the term "row address" referred to the starting block for a 4 page&amp;nbsp;read. Can anybody help clarify this for me? Thanks in advance! ~Tim&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Here's how the 5 byte flash address spec is divided up for the Micron flash part I'm using&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="color: #008000;"&gt;+--+----------&amp;gt; Bits[15-0] specify the column address (0-4319)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="color: #008000;"&gt;|&amp;nbsp; |&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;0x00&lt;SPAN style="color: #0000ff;"&gt;00&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000;"&gt;00&lt;/SPAN&gt;&lt;SPAN style="color: #008000;"&gt;0000&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;||&lt;SPAN style="color: #0000ff;"&gt;|&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000;"&gt;&lt;SPAN style="color: #0000ff;"&gt;|&lt;/SPAN&gt;||&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;||&lt;SPAN style="color: #0000ff;"&gt;|&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000;"&gt;&lt;SPAN style="color: #0000ff;"&gt;|&lt;/SPAN&gt;++--------------&amp;gt; Bits[22-16] Page address (0-127)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;||&lt;SPAN style="color: #0000ff;"&gt;||&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="color: #ff0000;"&gt;Bit [23] Plane select bit&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;||&lt;SPAN style="color: #0000ff;"&gt;||&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;||&lt;SPAN style="color: #0000ff;"&gt;++----------------&amp;gt; Bits[31-24] Block select bits&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp; ||&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp; ++------------------&amp;gt; Bits[34-32] Block select bits&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier,monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Bit [35] LUN spec bit&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Aug 2016 23:54:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576306#M4126</guid>
      <dc:creator>Tim562</dc:creator>
      <dc:date>2016-08-31T23:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: NAND Flash Boot Process Question</title>
      <link>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576307#M4127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;The page address and the block address, collectively, constitute the row address.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;The column address identifies the byte or word within a page to access.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;See the following documents:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.ece.umd.edu%2F%7Eblj%2FCS-590.26%2Fmicron-tn2919.pdf" rel="nofollow" target="_blank"&gt;https://www.ece.umd.edu/~blj/CS-590.26/micron-tn2919.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww2.lauterbach.com%2Fpdf%2Fnandflash.pdf" rel="nofollow" target="_blank"&gt;http://www2.lauterbach.com/pdf/nandflash.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;If an ECC failure is detected, additional reads will be conducted at row address 256, 512 and 768 (256, 512 and 768 pages).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2016 05:09:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576307#M4127</guid>
      <dc:creator>Pavel</dc:creator>
      <dc:date>2016-09-02T05:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: NAND Flash Boot Process Question</title>
      <link>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576308#M4128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply Pavel, would you happen to know if the MPC-5125 NFC&amp;nbsp;power on reset logic uses the RB (ready/busy) signal from the NAND flash part to determine when it is ok to send the reset command (0xFF) to the flash and start the power up read of the bootloader code? The microcontroller reference manual (section 23, Nand Flash Controller) is pretty thin on details of how the boot process and timing works. It does&amp;nbsp;mention sending the flash reset command and&amp;nbsp;the 4 separate reads from 4 different flash&amp;nbsp;locations, but that's about it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2016 17:26:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/NAND-Flash-Boot-Process-Question/m-p/576308#M4128</guid>
      <dc:creator>Tim562</dc:creator>
      <dc:date>2016-09-06T17:26:08Z</dc:date>
    </item>
  </channel>
</rss>

