Please provide the complete Ordering Part Number (OPN) of the Cypress FLASH memory device.
The Hardware RESET can be initiated at anytime during the execution of any embedded operation.
The increased time of ~150mS for sector erase and second programming, may be due to the pre-programming
sub-routine which occurs during the sector erase operation. The sector selected for erase is pre-programmed
to all ZERO's, then erase back to ONE's. The pre-programming sub-routine cannot be accessed by the user.
Therefore, the user cannot make any edits or changes to the pre-programming sub-routine.
However, as mentioned earlier, please provide the complete Ordering Part Number (OPN) of the the FLASH
Thank you in advance...
ENGLISH TRANSLATION :
With flash rewriting program created by customer
A hardware reset is applied (unintentionally) during the sector erase operation,
Execution of sector erase + write a second time after returning to reset, the execution time has been extended.
(644 ms -> 792 ms as measured values)
[Question 1] What are the possible reasons for extending the execution time?
[Question 2] When the state where resetting occurs during the erase operation is repeated, the flash
Will it get damaged and the subsequent writing time gradually increases and worsens?
the Ordering Part Number is S29GL128S90TFI020.
The sector erase time for a 128 KB sector is typically 275ms. The effective 128KB Sector Programming time (using full 512-byte buffer)
is 108mS. Therefore, Sector Erase time + Sector Program time equals 383mS.
The maximum Sector Erase time for 128KB sector is 1,100mS, and the effective 128KB Sector Programming time (using full 512-byte buffer)
is 192mS, then the Sector Erase time + Sector Program time equals 1,292mS, Therefore a combined sector erase and program (write) os
792mS is well below and within limits of the maximum combined time of 1,292mS.
No damage to the FLASH will occur during H/W RESET. However, sector erase time and programming time may increase over time,
if sector or chip erase and re-programming occurs frequently
Hope this helps...
Cypress Applications Support