<?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: LS1043 QSPI flash and AHB in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1584265#M11707</link>
    <description>Yes, lsdk-20.04</description>
    <pubDate>Wed, 18 Jan 2023 02:02:05 GMT</pubDate>
    <dc:creator>jiafang</dc:creator>
    <dc:date>2023-01-18T02:02:05Z</dc:date>
    <item>
      <title>LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1577812#M11615</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;&lt;P&gt;We are trying to use the QSPI flash on LS1043 board. Our kernel version is 5.2, flash is&amp;nbsp;&lt;SPAN&gt;mx66u1g45g.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We found that when we get the flash data which size is more then 0x80, then the data will be wrong.&lt;/P&gt;&lt;P&gt;Correct:&lt;/P&gt;&lt;P&gt;00000000 : &lt;STRONG&gt;31 31 20 30 31 3A 34 32&lt;/STRONG&gt; 30 30 30 30 30 30 30 30&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;Wrong:&lt;/P&gt;&lt;P&gt;00000000 : 30 30 30 30 30 30 30 30 49 50 4C 2D 52 4F 4D 33&lt;/P&gt;&lt;P&gt;It seems like the first 8 bytes is lost from the read result.&lt;/P&gt;&lt;P&gt;We found that the code will try to access the AHB to get the data.&lt;/P&gt;&lt;P&gt;1) Is there similar issue as in&amp;nbsp;&lt;A href="https://source.denx.de/u-boot/u-boot/-/commit/def88bce094e95939abf1e5d02a9b413b3627f6f" target="_blank" rel="noopener"&gt;https://source.denx.de/u-boot/u-boot/-/commit/def88bce094e95939abf1e5d02a9b413b3627f6f&lt;/A&gt;&amp;nbsp;on LS1043 ?&lt;/P&gt;&lt;P&gt;2) From ls1043 RM:&lt;/P&gt;&lt;P&gt;IP Command Read: For reading flash data into the RX Buffer the user must&lt;BR /&gt;provide the correct sequence ID in the QuadSPI_IPCR[SEQID] register. The&lt;BR /&gt;sequence ID points to a sequence in the LUT. It is the responsibility of the&lt;BR /&gt;software to ensure that &lt;STRONG&gt;a correct read sequence is programmed in the LUT&lt;/STRONG&gt; in&lt;BR /&gt;accordance with the serial flash device connected on board.&lt;/P&gt;&lt;P&gt;How do we know the&amp;nbsp;&lt;STRONG&gt;read sequence is correct&amp;nbsp;programmed in the LUT ? &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The correct read sequence should be like what seq ? Do you have some examples ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 02:51:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1577812#M11615</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-06T02:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1580389#M11648</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Can you let me know the details about the issue? I assume that the issue happens under Linux kernel 5.2, not on uboot, is that correct?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you dump the QSPI registers and all the data for 128 bytes and 160 bytes read?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A1, I do not think that we have a similar issue on LS1043a. At least it is not limited to 128 Bytes. It limits to the AHB buffer size to 1 KB.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A2. Do you use IP read or AHB read? Yes, it is the software's responsibility to ensure correct read sequence. The qSPI controller does not know or care about the read sequence. The read sequence is based on what is connected to the qSPI bus. The read/write sequences come from the qSPI slave device. The qSPI controller only follow what are in the LUT.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The section Serial Flash Devices in the LS1043ARM (30.9 in rev 5 ) has several Example Sequences. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 01:11:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1580389#M11648</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-01-11T01:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1580465#M11650</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;Yes, it is on kernel, not uboot&lt;/P&gt;&lt;P&gt;Which registers need to be dumped ?&lt;/P&gt;&lt;P&gt;We use mtd_debug() to read the flash data, it finally calls fsl_qspi_exec_op(). From where we can know it is IP read or AHB read ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 03:01:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1580465#M11650</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-11T03:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1581586#M11664</link>
      <description>Hi&lt;BR /&gt;We add some debug info, as following:&lt;BR /&gt;&lt;BR /&gt;Could you help to check if the reg and lut value is normal ?&lt;BR /&gt;&lt;BR /&gt;QUADSPI_BFGENCR is 0xf000&lt;BR /&gt;QUADSPI_SFAR is 0x40000000&lt;BR /&gt;lutval[0] is 0x10000413 for 0x10b80400 (base + QUADSPI_LUT_REG(0))&lt;BR /&gt;lutval[1] is 0x10001010 for 0x10b80404&lt;BR /&gt;lutval[2] is 0x1c001008 for 0x10b80408&lt;BR /&gt;lutval[3] is 0x0 for 0x10b8040c&lt;BR /&gt;&lt;BR /&gt;read from 100008 len is 0x80&lt;BR /&gt;[2023-01-12 13:54:12.400] ahb addr is 0x13800008, start is 0x100008, memmap_start is 0x100008, len is 128&lt;BR /&gt;[2023-01-12 13:54:12.409] 00000000 : 30 30 30 30 30 30 30 30 49 50 4C 2D 52 4F 4D 33 : 00000000IPL-ROM3&lt;BR /&gt;[2023-01-12 13:54:12.418] 00000010 : 33 36 2E 30 30 2E 30 30 00 00 00 00 00 00 00 00 : 36.00.00........&lt;BR /&gt;[2023-01-12 13:54:12.418] 00000020 : 30 30 30 30 30 30 30 30 E7 DC 1B 5D 00 3F FF C0 : 00000000...].?..&lt;BR /&gt;[2023-01-12 13:54:12.427] 00000030 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:12.439] 00000040 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:12.444] 00000050 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:12.444] 00000060 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:12.456] 00000070 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;&lt;BR /&gt;read from 100008 len is 0xa0&lt;BR /&gt;[2023-01-12 13:54:18.923] ahb addr is 0x13800008, start is 0x100008, memmap_start is 0x100008, len is 160&lt;BR /&gt;[2023-01-12 13:54:18.932] 00000000 : 30 30 30 30 30 30 30 30 49 50 4C 2D 52 4F 4D 33 : 00000000IPL-ROM3&lt;BR /&gt;[2023-01-12 13:54:18.932] 00000010 : 33 36 2E 30 30 2E 30 30 00 00 00 00 00 00 00 00 : 36.00.00........&lt;BR /&gt;[2023-01-12 13:54:18.942] 00000020 : 30 30 30 30 30 30 30 30 E7 DC 1B 5D 00 3F FF C0 : 00000000...].?..&lt;BR /&gt;[2023-01-12 13:54:18.951] 00000030 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.960] 00000040 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.960] 00000050 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.969] 00000060 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.978] 00000070 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.987] 00000080 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;[2023-01-12 13:54:18.987] 00000090 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF : ................&lt;BR /&gt;&lt;BR /&gt;Note:&lt;BR /&gt;After the patch, the reg value will be changed as:&lt;BR /&gt;QUADSPI_BFGENCR is 0xe000&lt;BR /&gt;QUADSPI_SFAR is 0x40100008 (0x40000000 + 100008)&lt;BR /&gt;lutval[0] is 0x8200413 for 0x10b80400 (base + QUADSPI_LUT_REG(0))&lt;BR /&gt;lutval[1] is 0x1c00 for 0x10b80404&lt;BR /&gt;lutval[2] is 0x0 for 0x10b80408&lt;BR /&gt;lutval[3] is 0x0 for 0x10b8040c&lt;BR /&gt;&lt;BR /&gt;lutval[0] is 0x8200413 for 0x10b803f0 (base + QUADSPI_AHB_LUT_REG(0))&lt;BR /&gt;lutval[1] is 0x1c00 for 0x10b803f4&lt;BR /&gt;lutval[2] is 0x0 for 0x10b803f8&lt;BR /&gt;lutval[3] is 0x0 for 0x10b803fc</description>
      <pubDate>Thu, 12 Jan 2023 09:20:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1581586#M11664</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-12T09:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1583564#M11691</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Can you let me know what patch? Is the issue get resolved after the patch?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 02:04:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1583564#M11691</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-01-17T02:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1583604#M11692</link>
      <description>This patch: &lt;A href="https://source.denx.de/u-boot/u-boot/-/commit/def88bce094e95939abf1e5d02a9b413b3627f6f" target="_blank"&gt;https://source.denx.de/u-boot/u-boot/-/commit/def88bce094e95939abf1e5d02a9b413b3627f6f&lt;/A&gt;&lt;BR /&gt;Could you help to check if the lut value is normal before and after the patch ?&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Jan 2023 02:54:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1583604#M11692</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-17T02:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1584250#M11706</link>
      <description>&lt;P&gt;&lt;SPAN&gt;One more question, do you use our LSDK release? if you do, which version do you use?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2023 01:41:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1584250#M11706</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-01-18T01:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1584265#M11707</link>
      <description>Yes, lsdk-20.04</description>
      <pubDate>Wed, 18 Jan 2023 02:02:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1584265#M11707</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-18T02:02:05Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1585077#M11721</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Just want to confirm whether the issue is resolved after the patch.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 00:34:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1585077#M11721</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-01-19T00:34:48Z</dc:date>
    </item>
    <item>
      <title>Re: LS1043 QSPI flash and AHB</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1585143#M11723</link>
      <description>Yes we backported to kernel, made some changes to match the kernel code.&lt;BR /&gt;We didn't do full test, but at least we can successfully get the 0x80 and 0xa0.</description>
      <pubDate>Thu, 19 Jan 2023 02:32:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1043-QSPI-flash-and-AHB/m-p/1585143#M11723</guid>
      <dc:creator>jiafang</dc:creator>
      <dc:date>2023-01-19T02:32:11Z</dc:date>
    </item>
  </channel>
</rss>

