Hi James, This issue has been caught when we are updating the Linux OS from older kernel version to newer version. In older version, there wasn't logic to check SFDP and SMPT param and hence this issue was never been caught. But with newer Linux kernel OS version, we have hit this issue. Also, presently in u-boot bootloader there is no check for SFDP and SMPT param for this flash and hence not been caught there. But, we have hit this same issue when trying to update UEFI bootloader. New UEFI bootloader is parsing SFDP param and SMPT table. IMO, as this issue is SPI-NOR flash issue, thus this would be independent of the target. We have observed this on older LS family target(LS1046ARDB) as well as on LX2 on which this flash is connected. -- Regards Yogesh Gaur > -----Original Message----- > From: James Tomasetta [mailto:James.Tomasetta@xxxxxxxxxxx] > Sent: Thursday, December 6, 2018 10:00 PM > To: Boris Brezillon <boris.brezillon@xxxxxxxxxxx>; Yong Qin > <Yong.Qin@xxxxxxxxxxx> > Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@xxxxxxx>; Tudor Ambarus > <tudor.ambarus@xxxxxxxxxxxxx>; cyrille.pitchen@xxxxxxxxxx; Jimmy Zhao > <jimmy.zhao@xxxxxxx>; linux-mtd@xxxxxxxxxxxxxxxxxxx > Subject: RE: SPI-NOR FS512S incorrect CR3NV[1] value > > Boris, > > Is there an issue with updating the software? Is the issue that there is a ROM > bootloader checking this? Is this for the LX2 or the old LS family? > > James > > -----Original Message----- > From: Boris Brezillon <boris.brezillon@xxxxxxxxxxx> > Sent: Wednesday, December 5, 2018 1:28 PM > To: Yong Qin <Yong.Qin@xxxxxxxxxxx> > Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@xxxxxxx>; Tudor Ambarus > <tudor.ambarus@xxxxxxxxxxxxx>; cyrille.pitchen@xxxxxxxxxx; James > Tomasetta <James.Tomasetta@xxxxxxxxxxx>; Jimmy Zhao > <jimmy.zhao@xxxxxxx>; linux-mtd@xxxxxxxxxxxxxxxxxxx > Subject: Re: SPI-NOR FS512S incorrect CR3NV[1] value > > On Wed, 5 Dec 2018 19:21:51 +0000 > Yong Qin <Yong.Qin@xxxxxxxxxxx> wrote: > > > Hi Boris, > > > > Thanks for pointing this out. > > > > Confirmed with our product team, this is the part of datasheet > > discrepancy. Since FS512S only has 256KB sector size option, CR3NV[1] > > is don't care in FS512S and default value is set as 0 in factory. > > > > Column 3 (CR3NV[1]) of table 70 in datasheet will be removed. > > > > For software implementation, if identified the device is FS512S, then > > checking the combination of CR3NV[3] & CR1NV[2] is sufficient to > > decide if the device has top/bottom 4KB sectors, or uniform 256KB > > sectors. > > Again, fixing the datasheet is not enough, the SMPT section on the flash needs > to be fixed too. > > This message and any attachments may contain confidential information from > Cypress or its subsidiaries. If it has been received in error, please advise the > sender and immediately delete this message. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/