<?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: LS1046A IFC Async NAND interface</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1766727#M13715</link>
    <description>&lt;P&gt;Ha... yes the ordering within registers confused me as well originally, but it became apparent that the first bit reading left to right that was labeled bit0 was actually the MSb... I adjusted my thinking while reading the reference manual after that...&lt;/P&gt;&lt;P&gt;But more specifically, what I was referring to was the actual bus between the IFC and the NAND part, and that the reference manual shows the bitwise reversal in picture form.&amp;nbsp; There is nothing written with words that indicates the actual bus interface must be bitwise flipped.&amp;nbsp; On my first spin of the board, I connected b0 from the LS1046A to b0 on the NAND chip, and b1-b1, and so on...&amp;nbsp; This is exactly backwards.&amp;nbsp; On the second spin of my board, I connected b0 from the LS1046A to b7 on the NAND chip, b1-&amp;gt;b6, b2-&amp;gt;b5, and so on, and it works correctly...&lt;/P&gt;&lt;P&gt;This is what I was referring to... Still an important note for others.&lt;/P&gt;&lt;P&gt;-Dave&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Nov 2023 19:57:30 GMT</pubDate>
    <dc:creator>Daves_Garage</dc:creator>
    <dc:date>2023-11-30T19:57:30Z</dc:date>
    <item>
      <title>LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587376#M11753</link>
      <description>&lt;P&gt;Hi, I'm looking for an explanation for the base address of NAND being used in u-boot for both the RDB and FRWY development boards.&amp;nbsp; The base address is 0x7e800000, and I can't seem to figure out why this is the case.&lt;/P&gt;&lt;P&gt;If I added an additional NAND chip, using CS1 instead of CS0, would I increase this size by the size of the chip?&lt;/P&gt;&lt;P&gt;Would I use the same address?&lt;/P&gt;&lt;P&gt;How was this address derived?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any pointers are greatly appreciated.&amp;nbsp; Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 23:07:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587376#M11753</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-01-24T23:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587715#M11758</link>
      <description>&lt;P&gt;Ok, this address refers to the SRAM buffer being used by the IFC when you're talking to NAND.&amp;nbsp; It has a maximum size (I think it's 0x10000), and since the buffer (which is memory mapped I believe also) is used for all NAND devices (you can't access more than one at a time), the address is the same for all...&lt;/P&gt;&lt;P&gt;I still haven't figured out where the address came from... although, I have come to realize the reference manual is pretty big &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;Still looking for help understanding how this address is known...&lt;/P&gt;&lt;P&gt;Anyone?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 15:35:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587715#M11758</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-01-25T15:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587992#M11759</link>
      <description>&lt;P&gt;Hello Daves Garage,&lt;/P&gt;
&lt;P&gt;This post is to inform you that I'm working on your case,&lt;/P&gt;
&lt;P&gt;Kindly give some time and I will update you,&lt;/P&gt;
&lt;P&gt;I'll keep you informed of the progress.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Hector Villarruel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 20:37:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1587992#M11759</guid>
      <dc:creator>Hector_Villarruel</dc:creator>
      <dc:date>2023-01-25T20:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1588001#M11760</link>
      <description>&lt;P&gt;Hi Hector, I've done a bit more reading and experimenting by modifying the base address on a couple of chips on my custom board, and I think I understand the solution now, namely:&amp;nbsp; The address doesn't mean a thing... &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Regarding SRAM buffer for NAND devices&lt;/STRONG&gt;&lt;BR /&gt;see section 22.5.5 SRAM buffer of the LS1046A Reference Manual, Rev. 3, 08/2021&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Buffer RAM consists of 16KB (16,384 bytes) or 0x4000 bytes&lt;/LI&gt;&lt;LI&gt;This RAM is shared as read/write memory for ALL devices (since they can’t be accessed at the same time)&lt;/LI&gt;&lt;LI&gt;The base address for the device is simply a way to differentiate them from each other, however address spacing must account for the buffer size, since it is shared and merely remapped for each device.&lt;/LI&gt;&lt;LI&gt;Base address of 0x7E800000 is arbitrary&lt;BR /&gt;U-boot software works with NAND1 and NAND2 base addresses set as follows:&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="markup"&gt;#define CONFIG_SYS_NAND_BASE 0x60000000
#define CONFIG_SYS_NAND_BASE2 0x60004000&lt;/LI-CODE&gt;&lt;P&gt;What are your thoughts?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 20:50:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1588001#M11760</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-01-25T20:50:02Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1588594#M11765</link>
      <description>&lt;P&gt;SUPER IMPORTANT POINT ABOUT THIS INTERFACE...&lt;/P&gt;&lt;P&gt;The bus between the NAND chip and the LS1046A IFC is bitwise reversed... Yes, AD0 connects to AD7 on your NAND part, AD1 to AD6, and so on...&amp;nbsp; In the 2500+ page reference manual, there are actually 3 places that describe this bitwise reversal, and they are in picture form, not words.&lt;/P&gt;&lt;P&gt;(see figures 22-58, 22-59, and 22-60)&amp;nbsp; It looks like this:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Daves_Garage_0-1674776887525.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/208498iFEEBC700228509C7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Daves_Garage_0-1674776887525.png" alt="Daves_Garage_0-1674776887525.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Something you could easily over look, because lets face it; when I think about connecting address and data busses, I go with 0 goes to 0, 1 goes to 1, etc...&lt;/P&gt;&lt;P&gt;I'm thinking this was a mistake originally; wonder what the first edition of the reference manual looks like.&lt;/P&gt;&lt;P&gt;Anyway, be careful, or you'll find yourself trying to flip bits in software or respinning your board to get things to work correctly...&lt;/P&gt;&lt;P&gt;-Dave&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2023 23:51:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1588594#M11765</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-01-26T23:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1759963#M13676</link>
      <description>I don't believe this is correct... I'm still looking for answers...</description>
      <pubDate>Mon, 20 Nov 2023 15:47:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1759963#M13676</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-11-20T15:47:21Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1766616#M13714</link>
      <description>&lt;P&gt;This happens in multiple other places as well. E.g. SerDes lane A is RX3/TX3, lane D is RX0/TX0. The registers are numbered incorrectly too. That is, they are numbered from bit 0 to 31, but bit 0 is what you get by doing 1 &amp;lt;&amp;lt; 31... This is not due to byte-swapping either, since if you e.g. read a big-endian register with a little-endian read (byte swapped) the bits (as documented) go 24 .. 31, 16 .. 23, 8..15, 0..7 (instead of 7..0, 15..8, 23..16, 31..24 like usual). I think whoever wrote the manual just loved naming the most-significant bit 0 instead of the least-significant bit.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 16:13:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1766616#M13714</guid>
      <dc:creator>stadium_aquino</dc:creator>
      <dc:date>2023-11-30T16:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1766727#M13715</link>
      <description>&lt;P&gt;Ha... yes the ordering within registers confused me as well originally, but it became apparent that the first bit reading left to right that was labeled bit0 was actually the MSb... I adjusted my thinking while reading the reference manual after that...&lt;/P&gt;&lt;P&gt;But more specifically, what I was referring to was the actual bus between the IFC and the NAND part, and that the reference manual shows the bitwise reversal in picture form.&amp;nbsp; There is nothing written with words that indicates the actual bus interface must be bitwise flipped.&amp;nbsp; On my first spin of the board, I connected b0 from the LS1046A to b0 on the NAND chip, and b1-b1, and so on...&amp;nbsp; This is exactly backwards.&amp;nbsp; On the second spin of my board, I connected b0 from the LS1046A to b7 on the NAND chip, b1-&amp;gt;b6, b2-&amp;gt;b5, and so on, and it works correctly...&lt;/P&gt;&lt;P&gt;This is what I was referring to... Still an important note for others.&lt;/P&gt;&lt;P&gt;-Dave&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2023 19:57:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1766727#M13715</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2023-11-30T19:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A IFC Async NAND interface</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1919581#M14629</link>
      <description>&lt;P&gt;Well, this is officially the longest I've ever waited for a response from NXP (1.5 years to date so far)... Hoping still for a response to my original question... before the processor goes EOL anyway.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 16:04:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-IFC-Async-NAND-interface/m-p/1919581#M14629</guid>
      <dc:creator>Daves_Garage</dc:creator>
      <dc:date>2024-07-29T16:04:07Z</dc:date>
    </item>
  </channel>
</rss>

