Nor Flash Forum Discussions
The datasheet for S25FL064L indicates that the S25FL064LABNFI043 option (USON) has an exposed center slug pad. Neither the connectivity diagrams nor signal descriptions indicate the presence or connectivity of this center slug pad, but the notes for the pad (002-12878 Rev. *F pp 138) suggest that this pad is to be used for heat sink purposes.
Is this pad NC, DNU, or is there an expected connection (eg. ground)?
Show LessWhen writing the norflash register, the value of the nonvolatile register CR2NV[7] is set to 1, the film does not come up, and there is no way to erase. Is there any way to solve it?
Show LessRegarding the WSON package, other than the different package dimensions (PCB change to accommodate the FL-L), would I need to change firmware, software or power supply to migrate to the FL-L? Are the FL-S and FL-L electrically and functionally equivalent? Besides package, they seem electrically and functionally the same.
Show LessHello, i have a board with some S25FS512S chips on it that i try to access through the SPI, but they dont reply.
I know i send the correct signals, because i send the same signals to a similar FLASH (S70FL01GS) and that one replies fine.
I attach you a screenshot of the signals and from bottom to top they are:
S25FS512S SO/IO1
SI/IO0
SCK
CS#
S70FL01GS SO/IO1
The signals from the first flash that is fed from a 3.3V domain, pass through level shifters and they have the correct voltage at the end.
i Use the following pin reference:
Please also note that all RFU,NC,DNU,IO3,IO2 are left open.
QUESTIONS:
1.i notice that RESET# and WP# are stuck at 0 in both flash types. Should't they be put to 1 as they are unconnected?
2.An important difference that i notice between the working and not working flashes is that in S70 while in standby SO is stuck at 1 while in the S25 is at 0. Is this important? What could this mean?
P.S. the exact number at the top of the chip is : fs512sAIF01 84100025 B
Thank you very much for you Help.
Show LessWe are designing a product using NorFlash(S29GL512N). As our product has a higher reliability requirement, considering the EMC design, could you provide the internal function and structure of Pin NC ? In order to improve the ability of interference tolerance , how to deal with PIN NC, using pull-up resistor or pull-down resistor ?
Show LessHello,
According to specification,
"When using DDR I/O commands with the DLP enabled, an LC that provides 5 or more dummy cycles should be selected to allow 1
cycle of additional time for the host to stop driving before the memory starts driving the 4-cycle DLP."
The following is the description of DDR latency cycle from specification:
"
During the latency cycles, the host keeps CS# low. The host may not drive the IO signals during these cycles. So that
there is sufficient time for the host drivers to turn off before the memory begins to drive. This prevents driver conflict between host
and memory when the signal direction changes. The memory has an option to drive all the IO signals with a Data Learning Pattern
(DLP) during the last four latency cycles. The DLP option should not be enabled when there are fewer than five latency cycles so
that there is at least one cycle of high impedance for turn around of the IO signals before the memory begins driving the DLP. When
there are more than four cycles of latency the memory does not drive the IO signals until the last four cycles of latency."
The question is what is the expected behavior when DDR QUAD Read (EDh, EEh) is issued while DLP is enabled and the configured latency cycles are fewer than five cycles.
Option A: The DDR QUAD Read command is ignored.
Option B: The command is executed but without DLP (as if DLP is disabled). The set latency cycles are preserved and following them data is output on IO signals. If latency cycles are zero, then data will be output directly after address.
Option C: The command is executed but without effective latency cycles. DLP in initiated directly after address. If latency cycles are four, then full DLP pattern is output. If latency is less than 4, partial DLP (partial data preamble) is output on I/O signals before data.
Option 😧 This is a hybrid option of option B and option C listed above. If latency is 4, DLP is initiated. If latency is less than 4, DLP is not initiated but latency will be fulfilled as dummy cycles preceding data . Following those cycles, data is output on I/O signals.
Option E: Assume that the default value for latency is 5 when DLP is enabled. So even if it is configured to a value less than 5, 5 cycles will be considered.
Thanks,
Mona
Show LessHi everybody,
I have an interesting case where a TSOP56 case S29GL064N (Spansion/ Cypress) was found to have Pin29 left open (not brazed on the PWB).
Pin 29 is "VIO" that powers the I/O buffers of the Flash memory.
The memory has pull-ups (3K32) on signals #BYTE (Pin 53) and I/O buffers (DQ0-DQ15) tied to the 3.3v power supply.
The Memory works fine even with VIO open circuit but found to fail at hot temperature (+85°C).
I Wonder why the Flash is working with the VIO left open and not tied to the 3.3V, except if the I/O buffers could be powered in some way through the pull-ups, and in this case a configuration where the I/Os are not meeting high speed transfer reducing drawn current from the 3.3V by the pull-ups that would maintain the I/Os at correct logic level...
Do you guys have any idea or experience on how the I/O buffers could be powered in my case (pull-ups on I/Os, pull-up on #BYTE, other, ...)?
Many thanks,
Pascal
Show LessI am using the S29GL-S nor flash, because the datasheet describle that WP pin has internal pull-up, when unconnected, WP is high level.
So I do not connect WP pin in my design circuit, but i measure WP in is low level , who can tell me why? I make sure that WP pin is not short with other pin.
Show Lesscould cypress has any suggestions on the connector part
Hello,
I am using the cypress linux driver found here: https://www.cypress.com/documentation/software-and-drivers/cypress-spi-flash-drivers-linux-kernel-4140
with the S70FS01GS NOR flash.
I have set the kernel configs for this driver and have changed the compatible property in my device tree to "cy-snor" but the driver probe is not getting called.
I am using NXP LS1088A processor and it uses the SPI Controller driver: "drivers/mtd/spi-nor/fsl-quadspi.c".
Is there anything else I need to do to get this driver working with the NXP fsl-quadspi driver?
Thanks,
Oliver
Show Less