<?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 LX2160a: NOR flash sector protect in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1758791#M13668</link>
    <description>&lt;P&gt;&lt;BR /&gt;We have micron NOR flash mt25qu02g on lx2160a based custom design.&lt;BR /&gt;I'm using below command from u-boot to protect the data sector of the flash memory.&lt;BR /&gt;However, it seems flash protect is not working as, I'm able to erase flash memory even after protect command.&lt;/P&gt;&lt;P&gt;=&amp;gt; sf protect lock 0x500000 0x10000&lt;BR /&gt;=&amp;gt; sf erase 0x500000 0x10000&lt;BR /&gt;SF: 65536 bytes @ 0x500000 Erased: OK&lt;/P&gt;&lt;P&gt;Does current nxp_fspi/spi-nor driver has a support for ASP/Section protection for micron NOR flash mt25qu02g ?&lt;/P&gt;&lt;P&gt;Below is the status register for mt25q nor flash family. As per my initial investigation it has BP3 (bit6) and I don't see &lt;SPAN&gt;SR_BP3 bit is used in u-boot spi-nor driver.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please let me know your thoughts on this, thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rsc202_0-1700199990277.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/250334i748B73B3EFDFB6E0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="rsc202_0-1700199990277.png" alt="rsc202_0-1700199990277.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;rsc202_0-1700199990277.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Nov 2023 14:10:11 GMT</pubDate>
    <dc:creator>csr202</dc:creator>
    <dc:date>2023-11-17T14:10:11Z</dc:date>
    <item>
      <title>LX2160a: NOR flash sector protect</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1758791#M13668</link>
      <description>&lt;P&gt;&lt;BR /&gt;We have micron NOR flash mt25qu02g on lx2160a based custom design.&lt;BR /&gt;I'm using below command from u-boot to protect the data sector of the flash memory.&lt;BR /&gt;However, it seems flash protect is not working as, I'm able to erase flash memory even after protect command.&lt;/P&gt;&lt;P&gt;=&amp;gt; sf protect lock 0x500000 0x10000&lt;BR /&gt;=&amp;gt; sf erase 0x500000 0x10000&lt;BR /&gt;SF: 65536 bytes @ 0x500000 Erased: OK&lt;/P&gt;&lt;P&gt;Does current nxp_fspi/spi-nor driver has a support for ASP/Section protection for micron NOR flash mt25qu02g ?&lt;/P&gt;&lt;P&gt;Below is the status register for mt25q nor flash family. As per my initial investigation it has BP3 (bit6) and I don't see &lt;SPAN&gt;SR_BP3 bit is used in u-boot spi-nor driver.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please let me know your thoughts on this, thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rsc202_0-1700199990277.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/250334i748B73B3EFDFB6E0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="rsc202_0-1700199990277.png" alt="rsc202_0-1700199990277.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;rsc202_0-1700199990277.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 14:10:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1758791#M13668</guid>
      <dc:creator>csr202</dc:creator>
      <dc:date>2023-11-17T14:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160a: NOR flash sector protect</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1759225#M13672</link>
      <description>&lt;P&gt;It seems flash protection doesn't work on&amp;nbsp;LX2160ARDB either. I've verified using "protect" and "sf protect" commands from u-boot (U-Boot 2019.04-gce862bb2d), but it doesn't seem to be working as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if I'm missing any other configuration here?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 21:43:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1759225#M13672</guid>
      <dc:creator>csr202</dc:creator>
      <dc:date>2023-11-17T21:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160a: NOR flash sector protect</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1763353#M13692</link>
      <description>&lt;P&gt;I verified this function in 2023.04 u-boot provided in NXP latest released LSDK, it worked.&lt;/P&gt;
&lt;P&gt;NOTICE: BL2: v2.8(release):android-13.0.0_2.0.0-rc1-1-g99195a23d-dirty&lt;BR /&gt;NOTICE: BL2: Built : 06:14:17, Jun 2 2023&lt;BR /&gt;NOTICE: UDIMM 18ADF2G72AZ-3G2E1&lt;BR /&gt;NOTICE: DDR4 UDIMM with 2-rank 64-bit bus (x8)&lt;/P&gt;
&lt;P&gt;NOTICE: 32 GB DDR4, 64-bit, CL=22, ECC on, 256B, CS0+CS1&lt;BR /&gt;NOTICE: BL2: Booting BL31&lt;BR /&gt;NOTICE: BL31: v2.8(release):android-13.0.0_2.0.0-rc1-1-g99195a23d-dirty&lt;BR /&gt;NOTICE: BL31: Built : 06:14:17, Jun 2 2023&lt;BR /&gt;NOTICE: Welcome to lx2160ardb BL31 Phase&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;U-Boot 2023.04+fsl+g1e5b6c6bf2 (Sep 05 2023 - 06:13:49 +0000)&lt;/P&gt;
&lt;P&gt;SoC: LX2160ACE Rev2.0 (0x87360020)&lt;BR /&gt;Clock Configuration:&lt;BR /&gt;CPU0(A72):2200 MHz CPU1(A72):2200 MHz CPU2(A72):2200 MHz&lt;BR /&gt;CPU3(A72):2200 MHz CPU4(A72):2200 MHz CPU5(A72):2200 MHz&lt;BR /&gt;CPU6(A72):2200 MHz CPU7(A72):2200 MHz CPU8(A72):2200 MHz&lt;BR /&gt;CPU9(A72):2200 MHz CPU10(A72):2200 MHz CPU11(A72):2200 MHz&lt;BR /&gt;CPU12(A72):2200 MHz CPU13(A72):2200 MHz CPU14(A72):2200 MHz&lt;BR /&gt;CPU15(A72):2200 MHz&lt;BR /&gt;Bus: 750 MHz DDR: 3200 MT/s&lt;BR /&gt;Reset Configuration Word (RCW):&lt;BR /&gt;00000000: 5883833c 24580058 00000000 00000000&lt;BR /&gt;00000010: 00000000 0c010000 00000000 00000000&lt;BR /&gt;00000020: 390001a0 00002580 00000000 00000096&lt;BR /&gt;00000030: 00000000 00000000 00000000 00000000&lt;BR /&gt;00000040: 00000000 00000000 00000000 00000000&lt;BR /&gt;00000050: 00000000 00000000 00000000 00000000&lt;BR /&gt;00000060: 00000000 00000000 00027000 00000000&lt;BR /&gt;00000070: 08b30010 00150020&lt;BR /&gt;Model: NXP Layerscape LX2160ARDB Board&lt;BR /&gt;Board: LX2160ACE Rev2.0-RDB, Board version: C, boot from FlexSPI DEV#0&lt;BR /&gt;FPGA: v9.0&lt;BR /&gt;SERDES1 Reference: Clock1 = 161.13MHz Clock2 = 161.13MHz&lt;BR /&gt;SERDES2 Reference: Clock1 = 100MHz Clock2 = 100MHz&lt;BR /&gt;SERDES3 Reference: Clock1 = 100MHz Clock2 = 100MHz&lt;BR /&gt;VID: Core voltage after adjustment is at 826 mV&lt;BR /&gt;DRAM: 31.9 GiB&lt;BR /&gt;DDR 31.9 GiB (DDR4, 64-bit, CL=22, ECC on)&lt;BR /&gt;DDR Controller Interleaving Mode: 256B&lt;BR /&gt;DDR Chip-Select Interleaving Mode: CS0+CS1&lt;BR /&gt;optee optee: OP-TEE api uid mismatch&lt;BR /&gt;QSFP: detected Fiberstore QSFP-SR4-40G s/n: G1804130068 mfgdt: 20/18/05&lt;BR /&gt;Using SERDES1 Protocol: 19 (0x13)&lt;BR /&gt;Using SERDES2 Protocol: 5 (0x5)&lt;BR /&gt;Using SERDES3 Protocol: 2 (0x2)&lt;BR /&gt;PCIe1: pcie@3400000 disabled&lt;BR /&gt;PCIe2: pcie@3500000 disabled&lt;BR /&gt;PCIe3: pcie@3600000 Root Complex: x1 gen1&lt;BR /&gt;PCIe4: pcie@3700000 disabled&lt;BR /&gt;PCIe5: pcie@3800000 Root Complex: x4 gen3&lt;BR /&gt;PCIe6: pcie@3900000 disabled&lt;BR /&gt;Core: 70 devices, 25 uclasses, devicetree: separate&lt;BR /&gt;WDT: Started watchdog@23a0000 with servicing every 1000ms (30s timeout)&lt;BR /&gt;MMC: FSL_SDHC: 0, FSL_SDHC: 1&lt;BR /&gt;Loading Environment from SPIFlash... SF: Detected mt35xu512aba with page size 256 Bytes, erase size 128 KiB, total 64 MiB&lt;BR /&gt;*** Warning - bad CRC, using default environment&lt;/P&gt;
&lt;P&gt;EEPROM: NXID v1&lt;BR /&gt;In: serial_pl01x&lt;BR /&gt;Out: serial_pl01x&lt;BR /&gt;Err: serial_pl01x&lt;BR /&gt;SEC0: RNG instantiated&lt;BR /&gt;Net: mdio@8b97000:0 is connected to DPMAC5@25g-aui. Reconnecting to DPMAC6@25g-aui&lt;BR /&gt;e1000: 00:15:17:be:d7:83&lt;BR /&gt;eth0: DPMAC2@xlaui4, eth1: DPMAC3@usxgmii, eth2: DPMAC4@usxgmii, eth3: DPMAC5@25g-aui, eth4: DPMAC6@25g-aui, eth5: DPMAC17@rgmii-id, eth6: DPMAC18@rgmii-id, eth7: e1000#0&lt;BR /&gt;SF: Detected mt35xu512aba with page size 256 Bytes, erase size 128 KiB, total 64 MiB&lt;BR /&gt;device 0 offset 0x640000, size 0x80000&lt;BR /&gt;SF: 524288 bytes @ 0x640000 Read: OK&lt;BR /&gt;device 0 offset 0xf00000, size 0x100000&lt;BR /&gt;SF: 1048576 bytes @ 0xf00000 Read: OK&lt;BR /&gt;device 0 offset 0xa00000, size 0x300000&lt;BR /&gt;SF: 3145728 bytes @ 0xa00000 Read: OK&lt;BR /&gt;device 0 offset 0xe00000, size 0x100000&lt;BR /&gt;SF: 1048576 bytes @ 0xe00000 Read: OK&lt;BR /&gt;crc32+ MC firmware version 10.37.0&lt;/P&gt;
&lt;P&gt;fsl-mc: Booting Management Complex ... SUCCESS&lt;BR /&gt;fsl-mc: Management Complex booted (version: 10.37.0, boot status: 0x1)&lt;BR /&gt;Hit any key to stop autoboot: 0&lt;BR /&gt;=&amp;gt;&lt;BR /&gt;=&amp;gt;&lt;BR /&gt;=&amp;gt; sf protect lock 0x1000000 0x10000&lt;BR /&gt;=&amp;gt; sf erase 0x1000000 0x10000&lt;BR /&gt;SF: 65536 bytes @ 0x1000000 Erased: ERROR -22&lt;BR /&gt;=&amp;gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 11:54:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160a-NOR-flash-sector-protect/m-p/1763353#M13692</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-11-24T11:54:01Z</dc:date>
    </item>
  </channel>
</rss>

