Hi Venkatesh, Thanks for such a fast response.
Running ‘sf probe’ gives: Flash: SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 128 MiB To be correct we use 2x MT25QL256ABA1EW9 [1, 2] which is basically the same as the n25q256a reported by sf. In defconfig I’ve specified CONFIG_ENV_SECT_SIZE=0x00040000 which is divided by 2 in parallel memories logic [3], resulting in the 128 KiB per Flash chip. If you need any further information, please let me know. [1] https://www.micron.com/products/storage/nor-flash/serial-nor/part-catalog/part-detail/mt25ql256aba1ew9-0sit [2] https://xonstorage.blob.core.windows.net/pdf/micron_mt25ql256aba1ew90sit_apr22_xonlink.pdf [3] https://lore.kernel.org/all/[email protected]/ BR Dominik From: Abbarapu, Venkatesh <[email protected]> Sent: Tuesday, December 3, 2024 1:01 PM To: Wernberger Dominik (1GS4) <[email protected]> Cc: git (AMD-Xilinx) <[email protected]>; [email protected]; Simek, Michal <[email protected]>; [email protected]; [email protected]; [email protected] Subject: *EXT* RE: [PATCH] mtd: spi-nor: Fix the qspi parallel memory issues Hi Dominik, Could you please let me know the details of the flash? I will check from my side. Thanks Venkatesh From: Dominik Wernberger <[email protected]<mailto:[email protected]>> Sent: Tuesday, December 3, 2024 5:21 PM To: Abbarapu, Venkatesh <[email protected]<mailto:[email protected]>> Cc: git (AMD-Xilinx) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Simek, Michal <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [PATCH] mtd: spi-nor: Fix the qspi parallel memory issues Hello Venkatesh, Is there any news on the status of this patch? I'm working with a Zynq 7z020 system where 2 Flashes operate in parallel QSPI mode. This patch is essential for the correct Flash erase in U-Boot v2025.01-rc3. Without this patch Flash erase fails on every second multiple of Flash erase section size (FESS). Failing means that the Flash erase is not initiated or successful. I.e., the Flash section is not altered. For example, lets assume a FESS with 0x20000 (128 kiB). sf test 00000 20000 # Works sf test 20000 20000 # Fails sf test 40000 20000 # Works sf test 60000 20000 # Fails # ... Note that executing sf erase 20000 20000 SF: 131072 bytes @ 0x20000 Erased: OK shows OK even though the Flash sector were not erased. In case you have any new/rebased patches you want me to test, I would be happy to do so. I'm looking forward getting this patch into mainline U-Boot. Best Regards, Dominik Content provided within this e-mail including any attachments, is for the use of the intended recipients and may contain Rohde & Schwarz company restricted information. Any unauthorized use, disclosure, or distribution of this communication in whole or in part is strictly prohibited. If you are not the intended recipient, please notify the sender by reply email or by telephone and delete the communication in its entirety. Content provided within this e-mail including any attachments, is for the use of the intended recipients and may contain Rohde & Schwarz company restricted information. Any unauthorized use, disclosure, or distribution of this communication in whole or in part is strictly prohibited. If you are not the intended recipient, please notify the sender by reply email or by telephone and delete the communication in its entirety.
