Datasheet
Table 21. Flash command timing specifications (continued)
Symbol Description
1
Min. Typ. Max. Unit Notes
t
eewr16b64k
• 48 KB EEPROM backup
• 64 KB EEPROM backup
— 475 2000 μs
t
eewr32bers
32-bit write to erased FlexRAM location
execution time
— 360 2000 µs
t
eewr32b32k
t
eewr32b48k
t
eewr32b64k
32-bit write to FlexRAM execution time:
• 32 KB EEPROM backup
• 48 KB EEPROM backup
• 64 KB EEPROM backup
—
—
—
630
720
810
2000
2125
2250
μs
μs
μs
3, 4
t
quickwr
32-bit Quick Write execution time : Time from CCIF clearing (start the write) until CCIF setting (32-bit write
complete, ready for next 32-bit write)
• 1st 32-bit write
• 2nd through Next to Last (Nth-1) 32-bit
write
• Last (Nth) 32-bit write (time for write only,
not cleanup)
—
—
—
200
150
200
550
550
550
μs
μs
μs
5, 6
t
quickwrClnup
Quick Write Cleanup execution time — — (Number
of Quick
Writes) *
2.0
ms 7
1. All command times assumes 25 MHz or greater flash clock frequency (for synchronization time between internal/external
clocks).
2. Maximum times for erase parameters based on expectations at cycling end-of-life.
3. For all EEPROM Emulation terms, the specified timing shown assumes previous record clean up has occurred. This may
be verified by executing FCCOB Command 0x77, and checking FCCOB number 5 contents show 0x00 - No EEPROM
issues detected.
4. 'First time' EERAM writes after a Reset or SETRAM may incur additional overhead for EEE cleanup, resulting in up to 2x
the times shown.
5. For 'Typ.', only after the Nth write completes will any data will be valid. Emulated EEPROM record scheme cleanup
overhead may occur after this point even after a brownout or reset. If power or reset occurs before the Nth write
completes, the last valid record set will still be valid and the new records will be discarded.
6. Quick Write may take up to 550 μs as additional cleanup may occur when crossing sector boundaries.
7. Time for emulated EEPROM record scheme overhead cleanup. Automatically done after last (Nth) write completes,
assuming still powered. Or via SETRAM cleanup execution command is requested at a later point.
NOTE
Under certain circumstances FlexMEM maximum times may be
exceeded. In this case the user or application may wait, or assert
reset to the FTFC macro to stop the operation.
6.3.1.2
Reliability specifications
Table 22. NVM reliability specifications
Symbol Description Min. Typ. Max. Unit Notes
When using as Program and Data Flash
Table continues on the next page...
Memory and memory interfaces
S32K1xx Data Sheet, Rev. 4, 06/2017
NXP Semiconductors
Preliminary
29