Nor Flash Forum Discussions
Hello:
I am migrating a design from S25FL127S to S25HL512T NOR flash. Couple of questions / issues:
- Is the data interface any different in the QSPI mode?
- How do I get a complete datasheet with the interface information? I have applied for the "early access" program and not received any response.
- Is there a separate data interface document?
I am trying to work on this today and I am disappointed that I cannot find any data interface information on the S25HLT devices on the web.
Thanks for your help !!!
Steve D
Show LessHi,
Can you suggest alternate QSPI flash of size 128Mb and temperature grade -40 to 105C or -40 to 125C and supports dual parallel x8 configuration wit zynq 7000. Please provide part that is in stock. Does S25FL128LAGNFB010 support dual parallel x8 configuration with zynq 7000?
Thanks.
Show LessHi All,
I am looking to use a S70FS01GS NOR flash as the configuration memory for a Xilinx Ultrascale Plus FPGA.
Is the S70 range supported by the FPGA/iMPACT programming tools?
Thanks in advance.
Show LessHi, there
I am using the device of S29JL032J70TFI010.
The program operation to this Flash ROM is monitored by Data# Polling processing, and the data is read after completion.
However, an event occurred in which valid data could not be read.
It is interpreted that this event can be avoided by reading twice from the corresponding part below in the data sheet.
*002-00857 Rev. *J Page37
Even if the device has completed the program or erase operation and DQ7 has valid data,
the data outputs on DQ15–DQ0 may be still invalid. Valid data on DQ15–DQ0 (or DQ7–DQ0 for x8-only device) will appear on successive read cycles.
This is a question for this sentence.
1. What kind of event do you want to call attention to in this sentence in the data sheet?
2. Can you tell me why this sentence was written?
Best Regards,
Kumada
I am using the memory verilog model in S29VS-R_VERILOG.zip. When I polling Status[7] after issuing "Buffer to Flash" in Secure Silicon Region, the model always feedback SSR array value instead of Status after programing done (current_state back to "SecSi_ENTRY"). I want to know if this is the expected behavior or something wrong there.
Verilog pieces (Line# 2434~2460)
SecSi_ENTRY:
begin
if (falling_edge_WRITE)
...
if (oe) // No status read branch here
begin
if (SecAddr == SA_SecSi)
begin
READMEM(ReturnAddr(Addr,SecAddr),SecAddr,SS_T);
Dout_zd = OutputD;
end
else
begin
READMEM(Addr,SecAddr,Mem_T);
Dout_zd = OutputD;
end
end
end
Hello
We have been using S29GL064N90TF103 for a while without issue and I have just tested three boards with the newer/faster replacement, Cypress S29GL064S70TF103, and the S29GL-S parts are not reporting the CFI Query string.
With the code below, both devices (the S29GL-N and S29GL-S) properly return these values as expected:
FlashCFI.mfgCode =0001h
FlashCFI.deviceCode[0]=227Eh
FlashCFI.deviceCode[1]=2210h
FlashCFI.deviceCode[3]=2201h
But the boards with the newer S29GL-S parts are returning these incorrect results:
query[0]=0x0001 //Error - Should be 'Q'
query[1]=0x227E //Error - Should be 'R'
query[2]=0x0000 //Error - Should be 'Y'
All 3 failing FLASH devices are marked:
S29GL064S70TF103
749BB481 A
(c) 13 SPANSION
I'm at a loss... Any suggestions?
Thanks!
// Send the AutoSelect command
FLASH_CMD_WR(NOR_UNLOCK_ADDR1, NOR_UNLOCK_DATA1); // 1st Cycle
FLASH_CMD_WR(NOR_UNLOCK_ADDR2, NOR_UNLOCK_DATA2); // 2nd Cycle
FLASH_CMD_WR(NOR_UNLOCK_ADDR1, NOR_AUTOSELECT_CMD); // 3rd Cycle
// Read the Manufacturer Code
FlashCFI.mfgCode = FLASH_CMD_RD(NOR_MFG_CODE_ADDRESS);
// Read the Device ID(s)
FlashCFI.deviceCode[0] = FLASH_CMD_RD(NOR_DEVICE_CODE1_ADDR);
FlashCFI.deviceCode[1] = FLASH_CMD_RD(NOR_DEVICE_CODE2_ADDR);
FlashCFI.deviceCode[2] = FLASH_CMD_RD(NOR_DEVICE_CODE3_ADDR);
// Get CFI data (valid in AutoSelect mode)
// Read CFI QUERY
FLASH_CMD_WR(NOR_CFI_ADDR_QUERY, NOR_CFI_QUERY_CMD);
// Get QUERY Response
query[0] = FLASH_CMD_RD(NOR_CFI1_ADDRESS);
query[1] = FLASH_CMD_RD(NOR_CFI2_ADDRESS);
query[2] = FLASH_CMD_RD(NOR_CFI3_ADDRESS);
Target SNOR series: S25FL064L , S25FL128L
I would like to protect the area of 256KB with a password lock.
Therefore, the capacity will be insufficient only in security area 2 and area 3.
It seems that the pointer area can also be password locked.
When I use the pointer area, can the size of 256KB be password-locked?
Show Less
hello Everyone,
The footprint for S25HS01GTDPBHM03 component is not available in it's Datasheet. Please Let me know where can i get the footprint of it. Expecting a quick reply.
Thanks in Advance!
Show LessDatasheet Rev L,
In table 8 the size of CFI data and the byte address range are not consistent. Range 00020h~000CEh (Here is also a typo in the table) means the size = 206d - 32d + 1d = 175 but the table scribed 174 which is confusing.
Also, is the ID/CFI ASO support Continuous & Linear Synchronous Read? The datasheet mentions SSR support both async/sync read but doesn't tell if ID/CFI supports it or not.
Thank you.
Regards,
Keter
Show Less