Hi,

I am using  SPI Serial Flash Memory, 512Mbit, SO16 package in one of my design. I am finding many chips getting faulty in 5 to 6 months of operation in field as all access fail post that.

On analyzing one of the field return card. I am able to read device ID of this part but starting few sectors read/ write is not consistent and finding number of places data read not matching with data written.

We tried to reprogram multiple times but data integrity is not there in various sectors belong to first bank.

Device ID is getting detected by firmware always. Just printing one uboot print of processor log.

Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB, total 64 MiB

Since data is not consistent in various sectors and we are using this as processor boot memory, so processor gets stuck during bootup.

We are using  mostly first bank (16MB) location only for processor uboot. On faulty chip, we found read/write access to locations 4MB onwards (all 3 banks except first) is ok. Since it is processor boot memory, so would be read just once during processor boot and write only if any image upgrade needed which is rare.

Datasheet mentions 100,000 Program-Erase Cycles on any sector typical. These sites are not having power backup and almost gets power cycle on daily basis but it does not explain endurance of sectors.

We noticed that part S25FL512SAGMFIR11 used is with VIO option but this pin is kept NC in our design. Measured voltage at this pin is 3.3V but dips to 2.5V while doing any access in working chips too. Below is the measurement done in one of the working board. 

Host is operating at 3.3V  IO level which is the same supply of flash VCC.

Thanks

Anurag

Hello,

I am using S25FS512SAGNFI011 Nor Flash for the FPGA Arria 10 configuration. I generated .jic file from .sof file as described in the document AN229767 of Infineon. I get the successful result on the tool when I load the file to the flash, but the FPGA does not boot up after power cycle. 

My settings for the generating the file are below:

I'll be glad if you can help me.

Best regards!

While attempting to flash data onto the memory, we have encountered persistent problems with memory corruption and functionality. Specifically, we have observed that errors are consistently popping up within the address range of 0x00000000 to 0x00002800. 

 Also, while erasing memory errors are popping up in given images

We've tried troubleshooting but need urgent assistance to resolve this issue.

Thanks & Regards