Nor Flash Forum Discussions
Hello,
About the output drive capability of Flash ROM, the data sheet conditions are as follows.
Vol (Output Low Voltage) : Iol=100uA for DQ15-DQ0
Voh (Output High Voltage) : Ioh=100uA
I would like to know the graph that shows the relation ship between voltage and current. (I attach a sample picture )
MPN: S29GL512S11DHV010
Best Regards,
Naoaki Morimoto
Show LessXilinx p/n XCF04SVOG20C is obsolete. Do you have an option available that wouldn't require a change to the PCB? XCF04SVOG20C uses 3.3V I/O, 4Mb, and is in a 20 pin TSSOP package. In our application its used to configure a Spartan 6 FPGA using a JTAG interface.
Thanks,
-Britt
Show Less
Hello,
Could you provide the Maximum word programming time and the Maximum buffer programming time for S29GL256P ?
MPN: S29GL256P90TFCR20
CFI flash manufacture ID : xx01h/1h
CFI flash device ID : 227Eh/7Eh
CFI flash extended device ID : 2222h/22h
Typical word programming time : 60us
Maximum word programming time : ?
Typical buffer programming time : 15us/word
Maximum buffer programming time : ?
Customer need to use this specification for FPGA boot configuration.
I can find a typical time for single and buffer programming in the datasheet, but can't find a max value.
Best Regards,
Naoaki Morimoto
Show LessI tried to custom SQI Flash driver from the MpLAB Harmony framework but it does not work.
I can get the ID of the S25FL256SAGNFI003 using RDID cmd, but cannot write data to it using 4QPP cmd.
After erase and write data to flash, I use DMA mode to read data from flash but all data return is 0x00.
I check the signal of the IO2 and IO3 line and notice the IDLE state of these lines are high level, IO0 and IO1 are low levels. Does it affect communication?
I attached the code and schematic here for reference.
Show LessDear Sir/Madam,
I am Cora, Nora’s colleague, and I will be following up on the data requests from now on.
Please see the attached Excel, and it is pre-populated with the parts included in this request. For these parts, we will need the following: REACH SVHC 211 and 209,REACH ANNEX XIV,REACH ANNEX XVII,IEC 62474 Declaration of Compliance (DoC),FMD, Persistent Organic Pollutant (EU POP) , Part Weight for the parts.
Show Less
Please advise which CY part can be the replacement for MX25U12832FZNI02.
After attempting a flash sector erase, we read back a 0xff44 from the sector and from the flash bank the sector is in, not 0xffff. After rebooting, we read back 0xffff from just the flash sector we erased, so the erase is working. We just can't verify it without rebooting.
Anyone know why we are reading back a 0xff44? We suspect it is getting into erase suspend mode.
Thanks, Jeff
Show LessI am using a Cypress S25FL512S with a Xilinx Zynq 7Z020. This particular flash has a flash block protection method where a one time programmable bit in the flash Config Register forces the chip, upon reset, to boot up with all of flash protected from erase and programming. You can disable Block Protection in the flash by clearing three Block Protection bits in the Status Register. I have verified that this all works as designed.
The problem I have bumped into is that once the flash chip is (permanently) in this block protect mode, the Xilinx Zynq BootROM can no longer properly read the flash on reset. I have little visibility into the precise nature of the BootROM failure. The BootROM puts a code of 0x0C into the REBOOT_STATUS register - indicating "Quad-SPI boot mode. The BootROM is unable to find a valid header within the image search range." It may well be that while the BootROM has support for this flash chip, it does not have support for the flash chip in this mode.
I am able to load code into the Zynq via the Xilinx IDE and run diagnostics to verify that the boot images are properly programmed into flash. There is nothing wrong with the boot images. People on my project have been building and programming boot images into flash for over a year. This is a known and solid process.
I either need someone to tell me how we can get the Zynq BootROM to work with the S25FL512S with Block Protection enabled OR someone that can tell me that this cannot work, i.e. it is not supported by the Zynq BootROM.
Show Less