S25FL512 vs S25FS512

S25FL512 vs S25FS512

[Barbier, Renaud]

Hello,
I bought a NXP ls1046ard evaluation board and saw some issues erasing the SPI NOR from my boot loader or ICE.
The boot loader reported the flash as being a S25FL512 which is a uniform (256KiB) sector SPI NOR as per manufacturing ID 1 and device id 2

The eval board has in fact a S25FS512 SPI NOR which is by default a bottom boot flash. This can be disabled through a configuration register in the SPI NOR.

I also see that Linux describes both the S25FL512 and S25FS512 as uniform sector flash:
{ "s25fl512s",  INFO6(0x010220, 0x4d0080, 256 * 1024, 256,
			      SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
			      SPI_NOR_HAS_LOCK | USE_CLSR) },

{ "s25fs512s",  INFO6(0x010220, 0x4d0081, 256 * 1024, 256,
			      SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR)



According to Cypress PDF https://www.cypress.com/file/177971/download, this SPI NOR S25FL512 is indeed a uniform sector flash but with a device ID of 0x19.
While the Spansion documentation I found (https://datasheetspdf.com/pdf-file/831993/SPANSION/S25FL512S/1 ) described it with a Device ID of 0x2.

The S25FS512S has Device ID 0x2 according to Cypress documentation https://www.cypress.com/file/216376/download  and is a bottom boot flash.

Is the SPI support for S25FS512 in Linux 5.14 disabling the bottom boot feature? I have not found it in the code. Only something related to page size.

Cheers,
Renaud



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Re: S25FL512 vs S25FS512

[Michael Walle]

Hi Renaud,

Am 2021-09-01 18:51, schrieb Barbier, Renaud:
> Hello,
> I bought a NXP ls1046ard evaluation board and saw some issues erasing
> the SPI NOR from my boot loader or ICE.
> The boot loader reported the flash as being a S25FL512 which is a
> uniform (256KiB) sector SPI NOR as per manufacturing ID 1 and device
> id 2
> 
> The eval board has in fact a S25FS512 SPI NOR which is by default a
> bottom boot flash. This can be disabled through a configuration
> register in the SPI NOR.

So you're saying the bootloader is wrong by reporting a S25FL512?

> I also see that Linux describes both the S25FL512 and S25FS512 as
> uniform sector flash:
> { "s25fl512s",  INFO6(0x010220, 0x4d0080, 256 * 1024, 256,
> 			      SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ |
> 			      SPI_NOR_HAS_LOCK | USE_CLSR) },
> 
> { "s25fs512s",  INFO6(0x010220, 0x4d0081, 256 * 1024, 256,
> 			      SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ | USE_CLSR)
> 
> 
> 
> According to Cypress PDF https://www.cypress.com/file/177971/download,
> this SPI NOR S25FL512 is indeed a uniform sector flash but with a
> device ID of 0x19.

You lost me here. According to Table 52. The device id is 02h.

> While the Spansion documentation I found
> (https://datasheetspdf.com/pdf-file/831993/SPANSION/S25FL512S/1 )
> described it with a Device ID of 0x2.

Likewise.

> The S25FS512S has Device ID 0x2 according to Cypress documentation
> https://www.cypress.com/file/216376/download  and is a bottom boot
> flash.

And also for this flash, the device id is 02h. But the family code
at offset 05h is 81h here (instead of 80h for the s25fl512s).

> Is the SPI support for S25FS512 in Linux 5.14 disabling the bottom
> boot feature? I have not found it in the code. Only something related
> to page size.

What is a bottom boot feature? Are you talking about locking?

-michael

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

RE: S25FL512 vs S25FS512

[Barbier, Renaud]

>You lost me here. According to Table 52. The device id is 02h.
I was looking at Table 40 page 68. Hence, the confusion.


>> Is the SPI support for S25FS512 in Linux 5.14 disabling the bottom 
>> boot feature? I have not found it in the code. Only something related 
>> to page size.

>What is a bottom boot feature? Are you talking about locking?
This flash S25FS512 is configured by default  to have the first 256KiB sector divided into 8*4KiB + 224KiB.
This could be the top sector or disable with the configuration register.
Erasing 8 4KiB sectors requires a different command than erasing the 256KiB sectors.

I have now found the code in U-boot supporting those 8 sectors. 

Thanks for your answer.




-michael

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/