3 Replies Latest reply on Mar 7, 2018 1:09 PM by MatthiasRick

    S25FL512S Recovery after Block Protection?

    maximilian.kasparek_2974266

      Hi

       

      In our system several Xilinx Zynq SoCs are booting from S25FL512S flash.

      Two weeks ago one of these Zynqs failed to boot after power-cycling, which could be recovered by re-programming the flash memory.

      Last week three more SoCs failed to boot, but re-programming of the flash wasn't possible.

       

      The S25FL512S's registers indicate that Block Protection was somehow activated:

      Status1: 0x9C

      Status2: 0x00

      Config1: 0xEA

       

      Having three devices failing on the same power-cycling feels systematic, however we have about 20 devices in the system which makes it a 3 out of 20 ratio.

      The data sheet says TBPROT and BPNV are OTP, which makes me believe the flash is in some kind of "fatal error data recovery" mode.

      Further more I think WRITE and ERASE protection shouldn't prevent devices from reading the flash for booting.

       

      Could someone please give me a hint at what led to this state, or even if it can be recovered?

       

      Max

        • 1. Re: S25FL512S Recovery after Block Protection?
          gsns

          Hello Max,

           

          One of the possible reasons could be power loss during write register operation when you boot up.

          Please refer to the KB article from the link given below which explains about the recovery if incorrect  write register operation has been performed.

          Power Loss During the Write Register (WRR) Operation in Serial NOR Flash Devices – KBA221246

           

          Thanks,

          Krishna.

          • 2. Re: S25FL512S Recovery after Block Protection?
            maximilian.kasparek_2974266

            Hello Krishna,

             

            thank you for the answer.

             

            We are not issuing WRR in our code, but I found "XQSPIPS_FLASH_OPCODE_WRSR    0x01 /* Write status register */" in the Xilinx qspi driver used by the first-stage bootloader. So perhapse the QUAD bit is indeed set during boot, as mentioned in the KBA.

            Power-cycling during boot is something that could have happened to the system.

             

            So w.r.t. my acute problem:

            As far as I understand I won't be able to reset the OTP Bit for BPNV to zero. Hence BP0-2 will default to 1, leaving the flash locked after power on.

            But if I could reset SRWD to zero (don't know about the WP# state), there could at least be the chance to reset the volatile bits?

             

            Max

            • 3. Re: S25FL512S Recovery after Block Protection?
              MatthiasRick

              Hello Max and Krishna,

               

              I'm facing the same issue. I'm also working with a Zynq SoC device and faced some problems reading the partition header within my FSBL. After adding QSPI-support the problem was gone, but I found another problem which currently lead to bricked devices.

               

              The datasheet says for Quad Ouptut Read: "The QUAD bit of Configuration Register must be set (CR Bit1=1) to enable the Quad mode capability." That is why I added the WRR command to enable the QSPI-bit mode which is basically working and solved my mentioned problem. But now I have another much more critical problem!

               

              After a power loss during startup the S25FL512S device got in to an undefined state. The status register values are similiar to the values Max already posted (SR1: 0x9C, CR1: 0xEA). After executing the WRR command again the flash I wasn't even able to read out the device id.

               

              After removing the WRR command in my FSBL and testing with another hardware I got the same issue caused by u-boot. I found the function spi_flash_set_qeb() is also performing a WRR command. The linux kernel may also perform a WRR command.  

               

              Until now I'm not able to get my broken flash devices working again. The best practice recommendation to maintain a stable power supply condition cannot be guaranteed in my application. 

               

              So my question is: Is there any chance to get the flash device back to a working state?

               

              Thanks,

              Matthias