M50FW016 16 Mbit (2Mb x8, Uniform Block) 3V Supply Firmware Hub Flash Memory PRELIMINARY DATA FEATURES SUMMARY ■ ■ ■ ■ ■ ■ ■ ■ SUPPLY VOLTAGE – VCC = 3 V to 3.6 V for Program, Erase and Read Operations – VPP = 12 V for Fast Program and Fast Erase TWO INTERFACES – Firmware Hub (FWH) Interface for embedded operation with PC Chipsets – Address/Address Multiplexed (A/A Mux) Interface for programming equipment compatibility FIRMWARE HUB (FWH) HARDWARE INTERFACE MODE – 5 Signal Communication Interface supporting Read and Write Operations – Hardware Write Protect Pins for Block Protection – Register Based Read and Write Protection – 5 Additional General Purpose Inputs for platform design flexibility – Multi-byte Read Operation (4/16/128byte) – Synchronized with 33 MHz PCI clock BYTE PROGRAMMING TIME – Single Byte Mode: 10µs (typical) – Quadruple Byte Mode: 2.5µs (typical) 32 UNIFORM 64 Kbyte MEMORY BLOCKS PROGRAM and ERASE SUSPEND – Read other Blocks during Program/Erase Suspend – Program other Blocks during Erase Suspend FOR USE in PC BIOS APPLICATIONS ELECTRONIC SIGNATURE – Manufacturer Code: 20h – Device Code: 2Eh July 2004 Figure 1. Package TSOP40 (N) 10 x 20mm 1/45 This is preliminary information on a new product now in development or undergoing evaluation. Details are subject to change without notice. M50FW016 TABLE OF CONTENTS FEATURES SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Figure 1. Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 SUMMARY DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Figure 2. Table 1. Figure 3. Table 2. Figure 4. Logic Diagram (FWH Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Signal Names (FWH Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Logic Diagram (A/A Mux Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Signal Names (A/A Mux Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 TSOP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 SIGNAL DESCRIPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Firmware Hub (FWH) Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Input/Output Communications (FWH0-FWH3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Input Communication Frame (FWH4).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Identification Inputs (ID0-ID3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 General Purpose Inputs (FGPI0-FGPI4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Interface Configuration (IC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Interface Reset (RP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 CPU Reset (INIT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Clock (CLK). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Top Block Lock (TBL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Write Protect (WP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Reserved for Future Use (RFU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Address/Address Multiplexed (A/A Mux) Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Address Inputs (A0-A10). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Data Inputs/Outputs (DQ0-DQ7). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Output Enable (G). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Write Enable (W). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Row/Column Address Select (RC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Ready/Busy Output (RB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supply Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 VCC Supply Voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 VPP Optional Supply Voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 VSS Ground. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Table 3. Block Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 BUS OPERATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Firmware Hub (FWH) Bus Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Bus Read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 FWH Bus Write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Bus Abort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Standby. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2/45 M50FW016 Block Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Address/Address Multiplexed (A/A Mux) Bus Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Bus Read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Bus Write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Output Disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Table 4. FWH Bus Read Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Figure 5. FWH Bus Read Waveforms (Single Byte Read) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 5. FWH Bus Write Field Definitions (Single Byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Figure 6. FWH Bus Write Waveforms (Single Byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Table 6. FWH Bus Write Field Definitions (Quadruple Byte Program) . . . . . . . . . . . . . . . . . . . . . 15 Figure 7. FWH Bus Write Waveforms (Quadruple Byte Program) . . . . . . . . . . . . . . . . . . . . . . . . . 15 Table 7. A/A Mux Bus Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Table 8. Manufacturer and Device Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 COMMAND INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Read Memory Array Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Read Status Register Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Read Electronic Signature Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Program Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Quadruple Byte Program Command (A/A Mux Mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Quadruple Byte Program Command (FWH Mode).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chip Erase Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Block Erase Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Clear Status Register Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Program/Erase Suspend Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Program/Erase Resume Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Table 9. Read Electronic Signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Table 10. Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 STATUS REGISTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Program/Erase Controller Status (Bit 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Erase Suspend Status (Bit 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Erase Status (Bit 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Program Status (Bit 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 VPP Status (Bit 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Program Suspend Status (Bit 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Block Protection Status (Bit 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Reserved (Bit 0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 11. Status Register Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 FIRMWARE HUB (FWH) INTERFACE CONFIGURATION REGISTERS . . . . . . . . . . . . . . . . . . . . . . 22 Lock Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Write Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Read Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Lock Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3/45 M50FW016 Firmware Hub (FWH) General Purpose Input Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Manufacturer Code Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Device Code Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Multi-Byte Read/Write Configuration Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 12. Firmware Hub Register Configuration Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 13. Lock Register Bit Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Table 14. General Purpose Input Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 PROGRAM AND ERASE TIMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Table 15. Program and Erase Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 MAXIMUM RATING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Table 16. Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 DC AND AC PARAMETERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 17. Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 18. FWH Interface AC Measurement Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 19. A/A Mux Interface AC Measurement Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 8. FWH Interface AC Testing Input Output Waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 9. A/A Mux Interface AC Testing Input Output Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Table 20. Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Table 21. DC Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 10.FWH Interface Clock Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 22. FWH Interface Clock Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 11.FWH Interface AC Signal Timing Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Table 23. FWH Interface AC Signal Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Figure 12.Reset AC Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Table 24. Reset AC Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Figure 13.A/A Mux Interface Read AC Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Table 25. A/A Mux Interface Read AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 14.A/A Mux Interface Write AC Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Table 26. A/A Mux Interface Write AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 PACKAGE MECHANICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Figure 15.TSOP40 – 40 lead Plastic Thin Small Outline, 10x20 mm, Package Outline . . . . . . . . . 35 Table 27. TSOP40 – 40 lead Plastic Thin Small Outline, 10x20 mm, Package Mechanical Data. . 35 PART NUMBERING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Table 28. Ordering Information Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 APPENDIX A.FLOWCHARTS AND PSEUDO CODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 16.Program Flowchart and Pseudo Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 17.Quadruple Byte Program Flowchart and Pseudo Code (A/A Mux Interface Only) . . . . . 38 Figure 18.Quadruple Byte Program Flowchart and Pseudo Code (FWH Interface Only) . . . . . . . . 39 Figure 19.Program Suspend and Resume Flowchart, and Pseudo Code. . . . . . . . . . . . . . . . . . . . 40 4/45 M50FW016 Figure 20.Chip Erase Flowchart and Pseudo Code (A/A Mux Interface Only) . . . . . . . . . . . . . . . . 41 Figure 21.Block Erase Flowchart and Pseudo Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Figure 22.Erase Suspend and Resume Flowchart, and Pseudo Code . . . . . . . . . . . . . . . . . . . . . . 43 REVISION HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Table 29. Document Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5/45 M50FW016 SUMMARY DESCRIPTION The M50FW016 is a 16 Mbit (2Mb x8) non-volatile memory that can be read, erased and reprogrammed. These operations can be performed using a single low voltage (3.0 to 3.6V) supply. For fast programming and fast erasing, an optional 12V power supply can be used to reduce the programming and the erasing times. The memory is divided into blocks that can be erased independently so it is possible to preserve valid data while old data is erased. Blocks can be protected individually to prevent accidental Program or Erase commands from modifying the memory. Program and Erase commands are written to the Command Interface of the memory. An on-chip Program/Erase Controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are required to update the memory contents. The end of a program or erase operation can be detected and any error conditions identified. The command set required to control the memory is consistent with JEDEC standards. Two different bus interfaces are supported by the memory. The primary interface, the Firmware Hub (or FWH) Interface, uses Intel’s proprietary FWH protocol. This has been designed to remove the need for the ISA bus in current PC Chipsets; the M50FW016 acts as the PC BIOS on the Low Pin Count bus for these PC Chipsets. The secondary interface, the Address/Address Multiplexed (or A/A Mux) Interface, is designed to be compatible with current Flash Programmers for production line programming prior to fitting to a PC Motherboard. The memory is offered in TSOP40 (10 x 20mm) package and it is supplied with all the bits erased (set to ’1’). Figure 2. Logic Diagram (FWH Interface) Table 1. Signal Names (FWH Interface) FWH0-FWH3 Input/Output Communications FWH4 Input Communication Frame ID0-ID3 Identification Inputs FGPI0-FGPI4 General Purpose Inputs IC Interface Configuration RP Interface Reset INIT CPU Reset CLK Clock CLK TBL Top Block Lock IC WP Write Protect RFU Reserved for Future Use. Leave disconnected. VCC Supply Voltage VPP Optional Supply Voltage for Fast Program and Fast Erase Operations VSS Ground NC Not Connected Internally RFU Reserved for Future Use VCC VPP 4 4 FWH0FWH3 ID0-ID3 5 FGPI0FGPI4 FWH4 WP M50FW016 TBL RP INIT VSS AI04462 6/45 M50FW016 Figure 3. Logic Diagram (A/A Mux Interface) VCC VPP 11 8 DQ0-DQ7 A0-A10 RC IC M50FW016 RB G Table 2. Signal Names (A/A Mux Interface) IC Interface Configuration A0-A10 Address Inputs DQ0-DQ7 Data Inputs/Outputs G Output Enable W Write Enable RC Row/Column Address Select RB Ready/Busy Output RP Interface Reset VCC Supply Voltage VPP Optional Supply Voltage for Fast Program and Fast Erase Operations VSS Ground NC Not Connected Internally RFU Reserved for Future Use W RP VSS AI04463 Figure 4. TSOP Connections A/A Mux NC IC (VIL) NC NC NC NC FGPI4 NC CLK VCC VPP RP NC NC FGPI3 FGPI2 FGPI1 FGPI0 WP TBL 1 10 11 20 40 M50FW016 31 30 21 VSS RFU FWH4 INIT RFU RFU RFU RFU RFU VCC VSS VSS FWH3 FWH2 FWH1 FWH0 ID0 ID1 ID2 ID3 VSS RFU W G RB DQ7 DQ6 DQ5 DQ4 VCC VSS VSS DQ3 DQ2 DQ1 DQ0 A0 A1 A2 A3 A/A Mux NC IC (VIH) NC NC NC NC A10 NC RC VCC VPP RP NC NC A9 A8 A7 A6 A5 A4 AI04464b 7/45 M50FW016 SIGNAL DESCRIPTIONS There are two different bus interfaces available on this part. The active interface is selected before power-up or during Reset using the Interface Configuration Pin, IC. The signals for each interface are discussed in the Firmware Hub (FWH) Signal Descriptions section and the Address/Address Multiplexed (A/A Mux) Signal Descriptions section below. The supply signals are discussed in the Supply Signal Descriptions section below. Firmware Hub (FWH) Signal Descriptions For the Firmware Hub (FWH) Interface see Figure 2., Logic Diagram (FWH Interface), and Table 1., Signal Names (FWH Interface). Input/Output Communications (FWH0-FWH3). All Input and Output Communication with the memory take place on these pins. Addresses and Data for Bus Read and Bus Write operations are encoded on these pins. Input Communication Frame (FWH4). The Input Communication Frame (FWH4) signals the start of a bus operation. When Input Communication Frame is Low, VIL, on the rising edge of the Clock a new bus operation is initiated. If Input Communication Frame is Low, VIL, during a bus operation then the operation is aborted. When Input Communication Frame is High, VIH, the current bus operation is proceeding or the bus is idle. Identification Inputs (ID0-ID3). The Identification Inputs select the address that the memory responds to. Up to 16 memories can be addressed on a bus. For an address bit to be ‘0’ the pin can be left floating or driven Low, VIL; an internal pull-down resistor is included with a value of RIL. For an address bit to be ‘1’ the pin must be driven High, VIH; there will be a leakage current of ILI2 through each pin when pulled to VIH; see Table 21. By convention the boot memory must have address ‘0000’ and all additional memories take sequential addresses starting from ‘0001’. By convention the boot memory must have ID0ID3 pins left floating or driven Low, VIL and a ‘1’ value on A21, A23-A25 and all additional memories take sequential ID0-ID3 configuration. General Purpose Inputs (FGPI0-FGPI4). The General Purpose Inputs can be used as digital inputs for the CPU to read. The General Purpose Input Register holds the values on these pins. The pins must have stable data from before the start of the cycle that reads the General Purpose Input Register until after the cycle is complete. These pins must not be left to float, they should be driven Low, VIL, or High, VIH. 8/45 Interface Configuration (IC). The Interface Configuration input selects whether the Firmware Hub (FWH) or the Address/Address Multiplexed (A/A Mux) Interface is used. The chosen interface must be selected before power-up or during a Reset and, thereafter, cannot be changed. The state of the Interface Configuration, IC, should not be changed during operation. To select the Firmware Hub (FWH) Interface the Interface Configuration pin should be left to float or driven Low, VIL; to select the Address/Address Multiplexed (A/A Mux) Interface the pin should be driven High, VIH. An internal pull-down resistor is included with a value of RIL; there will be a leakage current of ILI2 through each pin when pulled to VIH; see Table 21. Interface Reset (RP). The Interface Reset (RP) input is used to reset the memory. When Interface Reset (RP) is set Low, VIL, the memory is in Reset mode: the outputs are put to high impedance and the current consumption is minimized. When RP is set High, VIH, the memory is in normal operation. After exiting Reset mode, the memory enters Read mode. CPU Reset (INIT). The CPU Reset, INIT, pin is used to Reset the memory when the CPU is reset. It behaves identically to Interface Reset, RP, and the internal Reset line is the logical OR (electrical AND) of RP and INIT. Clock (CLK). The Clock, CLK, input is used to clock the signals in and out of the Input/Output Communication Pins, FWH0-FWH3. The Clock conforms to the PCI specification. Top Block Lock (TBL). The Top Block Lock input is used to prevent the Top Block (Block 31) from being changed. When Top Block Lock, TBL, is set Low, VIL, Program and Block Erase operations in the Top Block have no effect, regardless of the state of the Lock Register. When Top Block Lock, TBL, is set High, VIH, the protection of the Block is determined by the Lock Register. The state of Top Block Lock, TBL, does not affect the protection of the Main Blocks (Blocks 0 to 30). Top Block Lock, TBL, must be set prior to a Program or Block Erase operation is initiated and must not be changed until the operation completes or unpredictable results may occur. Care should be taken to avoid unpredictable behavior by changing TBL during Program or Erase Suspend. Write Protect (WP). The Write Protect input is used to prevent the Main Blocks (Blocks 0 to 30) from being changed. When Write Protect, WP, is set Low, VIL, Program and Block Erase operations in the Main Blocks have no effect, regardless of the state of the Lock Register. When Write Protect, M50FW016 WP, is set High, VIH, the protection of the Block determined by the Lock Register. The state of Write Protect, WP, does not affect the protection of the Top Block (Block 31). Write Protect, WP, must be set prior to a Program or Block Erase operation is initiated and must not be changed until the operation completes or unpredictable results may occur. Care should be taken to avoid unpredictable behavior by changing WP during Program or Erase Suspend. Reserved for Future Use (RFU). These pins do not have assigned functions in this revision of the part. They must be left disconnected. Address/Address Multiplexed (A/A Mux) Signal Descriptions For the Address/Address Multiplexed (A/A Mux) Interface see Figure 3., Logic Diagram (A/A Mux Interface), and Table 2., Signal Names (A/A Mux Interface). Address Inputs (A0-A10). The Address Inputs are used to set the Row Address bits (A0-A10) and the Column Address bits (A11-A20). They are latched during any bus operation by the Row/Column Address Select input, RC. Data Inputs/Outputs (DQ0-DQ7). The Data Inputs/Outputs hold the data that is written to or read from the memory. They output the data stored at the selected address during a Bus Read operation. During Bus Write operations they represent the commands sent to the Command Interface of the internal state machine. The Data Inputs/Outputs, DQ0-DQ7, are latched during a Bus Write operation. Output Enable (G). The Output Enable, G, controls the Bus Read operation of the memory. Write Enable (W). The Write Enable, W, controls the Bus Write operation of the memory’s Command Interface. Row/Column Address Select (RC). The Row/ Column Address Select input selects whether the Address Inputs should be latched into the Row Address bits (A0-A10) or the Column Address bits (A11-A20). The Row Address bits are latched on the falling edge of RC whereas the Column Address bits are latched on the rising edge. Ready/Busy Output (RB). The Ready/Busy pin gives the status of the memory’s Program/Erase Controller. When Ready/Busy is Low, VOL, the memory is busy with a Program or Erase operation and it will not accept any additional Program or Erase command except the Program/Erase Suspend command. When Ready/Busy is High, VOH, the memory is ready for any Read, Program or Erase operation. Supply Signal Descriptions The Supply Signals are the same for both interfaces. VCC Supply Voltage. The VCC Supply Voltage supplies the power for all operations (Read, Program, Erase etc.). The Command Interface is disabled when the VCC Supply Voltage is less than the Lockout Voltage, VLKO. This prevents Bus Write operations from accidentally damaging the data during power up, power down and power surges. If the Program/ Erase Controller is programming or erasing during this time then the operation aborts and the memory contents being altered will be invalid. After VCC becomes valid the Command Interface is reset to Read mode. A 0.1µF capacitor should be connected between the VCC Supply Voltage pins and the VSS Ground pin to decouple the current surges from the power supply. Both VCC Supply Voltage pins must be connected to the power supply. The PCB track widths must be sufficient to carry the currents required during program and erase operations. VPP Optional Supply Voltage. The VPP Optional Supply Voltage pin is used to select the Fast Program (see the Quadruple Byte Program Command description) and Fast Erase options of the memory and to protect the memory. When VPP < VPPLK Program and Erase operations cannot be performed and an error is reported in the Status Register if an attempt to change the memory contents is made. When VPP = VCC Program and Erase operations take place as normal. When VPP = VPPH Fast Program operations (using the Quadruple Byte Program command, 30h, from Table 10.) and Fast Erase operations are used. Any other voltage input to VPP will result in undefined behavior and should not be used. VPP should not be set to VPPH for more than 80 hours during the life of the memory. VSS Ground. VSS is the reference for all the voltage measurements. 9/45 M50FW016 Table 3. Block Addresses Size (Kbytes) Address Range 64 1F0000h-1FFFFFh 31 Top Block 64 1E0000h-1EFFFFh 30 Main Block 64 1D0000h-1DFFFFh 29 Main Block 64 1C0000h-1CFFFFh 28 Main Block 64 1B0000h-1BFFFFh 27 Main Block 64 1A0000h-1AFFFFh 26 Main Block 64 190000h-19FFFFh 25 Main Block 64 180000h-18FFFFh 24 Main Block 64 170000h-17FFFFh 23 Main Block 64 160000h-16FFFFh 22 Main Block 64 150000h-15FFFFh 21 Main Block 64 140000h-14FFFFh 20 Main Block 64 130000h-13FFFFh 19 Main Block 64 120000h-12FFFFh 18 Main Block 64 110000h-11FFFFh 17 Main Block 64 100000h-10FFFFh 16 Main Block 64 0F0000h-0FFFFFh 15 Main Block 64 0E0000h-0EFFFFh 14 Main Block 64 0D0000h-0DFFFFh 13 Main Block 64 0C0000h-0CFFFFh 12 Main Block 64 0B0000h-0BFFFFh 11 Main Block 64 0A0000h-0AFFFFh 10 Main Block 64 090000h-09FFFFh 9 Main Block 64 080000h-08FFFFh 8 Main Block 64 070000h-07FFFFh 7 Main Block 64 060000h-06FFFFh 6 Main Block 64 050000h-05FFFFh 5 Main Block 64 040000h-04FFFFh 4 Main Block 64 030000h-03FFFFh 3 Main Block 64 020000h-02FFFFh 2 Main Block 64 010000h-01FFFFh 1 Main Block 64 000000h-00FFFFh 0 Main Block 10/45 Block Block Type Number M50FW016 BUS OPERATIONS The two interfaces have similar bus operations but the signals and timings are completely different. The Firmware Hub (FWH) Interface is the usual interface and all of the functionality of the part is available through this interface. Only a subset of functions are available through the Address/ Address Multiplexed (A/A Mux) Interface. Follow the section Firmware Hub (FWH) Bus Operations below and the section Address/ Address Multiplexed (A/A Mux) Bus Operations below for a description of the bus operations on each interface. Firmware Hub (FWH) Bus Operations The Firmware Hub (FWH) Interface consists of four data signals (FWH0-FWH3), one control line (FWH4) and a clock (CLK). In addition protection against accidental or malicious data corruption can be achieved using two further signals (TBL and WP). Finally two reset signals (RP and INIT) are available to put the memory into a known state. The data signals, control signal and clock are designed to be compatible with PCI electrical specifications. The interface operates with clock speeds up to 33MHz. The following operations can be performed using the appropriate bus cycles: Bus Read, Bus Write, Standby, Reset and Block Protection. Bus Read. Bus Read operations read from the memory cells, specific registers in the Command Interface or Firmware Hub Registers. A valid Bus Read operation starts when Input Communication Frame, FWH4, is Low, VIL, as Clock rises and the correct Start cycle is on FWH0-FWH3. On the following clock cycles the Host will send the Memory ID Select, Address and other control bits on FWH0-FWH3. The memory responds by outputting Sync data until the wait-states have elapsed followed by Data0-Data3 and Data4Data7. Refer to Table 4., FWH Bus Read Field Definitions, and Figure 5., FWH Bus Read Waveforms (Single Byte Read), for a description of the Field definitions for each clock cycle of the transfer. See Table 23., FWH Interface AC Signal Timing Characteristics and Figure 11., FWH Interface AC Signal Timing Waveforms, for details on the timings of the signals. FWH Bus Write. Bus Write operations write to the Command Interface or Firmware Hub Registers. A valid Bus Write operation starts when Input Communication Frame, FWH4, is Low, VIL, as Clock rises and the correct Start cycle is on FWH0-FWH3. On the following Clock cycles the Host will send the Memory ID Select, Address, other control bits, Data0-Data3 and Data4-Data7 on FWH0-FWH3. The memory outputs Sync data until the wait-states have elapsed. Refer to Table 5., FWH Bus Write Field Definitions (Single Byte), and Figure 6., FWH Bus Write Waveforms (Single Byte), for a description of the Field definitions for each clock cycle of the transfer. See Table 23., FWH Interface AC Signal Timing Characteristics, and Figure 11., FWH Interface AC Signal Timing Waveforms, for details on the timings of the signals. Bus Abort. The Bus Abort operation can be used to immediately abort the current bus operation. A Bus Abort occurs when FWH4 is driven Low, VIL, during the bus operation; the memory will tri-state the Input/Output Communication pins, FWH0FWH3. Note that, during a Bus Write operation, the Command Interface starts executing the command as soon as the data is fully received; a Bus Abort during the final TAR cycles is not guaranteed to abort the command; the bus, however, will be released immediately. Standby. When FWH4 is High, VIH, the memory is put into Standby mode where FWH0-FWH3 are put into a high-impedance state and the Supply Current is reduced to the Standby level, ICC1. Reset. During Reset mode all internal circuits are switched off, the memory is deselected and the outputs are put in high-impedance. The memory is in Reset mode when Interface Reset, RP, or CPU Reset, INIT, is Low, VIL. RP or INIT must be held Low, VIL, for tPLPH. The memory resets to Read mode upon return from Reset mode and the Lock Registers return to their default states regardless of their state before Reset, see Table 13. If RP or INIT goes Low, VIL, during a Program or Erase operation, the operation is aborted and the memory cells affected no longer contain valid data; the memory can take up to tPLRH to abort a Program or Erase operation. Block Protection. Block Protection can be forced using the signals Top Block Lock, TBL, and Write Protect, WP, regardless of the state of the Lock Registers. Address/Address Multiplexed (A/A Mux) Bus Operations The Address/Address Multiplexed (A/A Mux) Interface has a more traditional style interface. The signals consist of a multiplexed address signals (A0-A10), data signals, (DQ0-DQ7) and three control signals (RC, G, W). An additional signal, RP, can be used to reset the memory. The Address/Address Multiplexed (A/A Mux) Interface is included for use by Flash Programming equipment for faster factory 11/45 M50FW016 programming. Only a subset of the features available to the Firmware Hub (FWH) Interface are available; these include all the Commands but exclude the Security features and other registers. The following operations can be performed using the appropriate bus cycles: Bus Read, Bus Write, Output Disable and Reset. When the Address/Address Multiplexed (A/A Mux) Interface is selected all the blocks are unprotected. It is not possible to protect any blocks through this interface. Bus Read. Bus Read operations are used to output the contents of the Memory Array, the Electronic Signature and the Status Register. A valid Bus Read operation begins by latching the Row Address and Column Address signals into the memory using the Address Inputs, A0-A10, and the Row/Column Address Select RC. Then Write Enable (W) and Interface Reset (RP) must be High, VIH, and Output Enable, G, Low, VIL, in order to perform a Bus Read operation. The Data Inputs/Outputs will output the value, see Figure 13., A/A Mux Interface Read AC Waveforms, and Table 25., A/A Mux Interface Read AC Characteristics, for details of when the output becomes valid. 12/45 Bus Write. Bus Write operations write to the Command Interface. A valid Bus Write operation begins by latching the Row Address and Column Address signals into the memory using the Address Inputs, A0-A10, and the Row/Column Address Select RC. The data should be set up on the Data Inputs/Outputs; Output Enable, G, and Interface Reset, RP, must be High, VIH and Write Enable, W, must be Low, VIL. The Data Inputs/ Outputs are latched on the rising edge of Write Enable, W. See Figure 14., A/A Mux Interface Write AC Waveforms, and Table 26., A/A Mux Interface Write AC Characteristics, for details of the timing requirements. Output Disable. The data outputs are high-impedance when the Output Enable, G, is at VIH. Reset. During Reset mode all internal circuits are switched off, the memory is deselected and the outputs are put in high-impedance. The memory is in Reset mode when RP is Low, VIL. RP must be held Low, VIL for tPLPH. If RP is goes Low, VIL, during a Program or Erase operation, the operation is aborted and the memory cells affected no longer contain valid data; the memory can take up to tPLRH to abort a Program or Erase operation. M50FW016 Table 4. FWH Bus Read Field Definitions Clock Cycle Number Clock Cycle Count Field FWH0FWH3 Memory I/O 1 1 START 1101b I On the rising edge of CLK with FWH4 Low, the contents of FWH0-FWH3 indicate the start of a FWH Read cycle. 2 1 IDSEL XXXX I Indicates which FWH Flash Memory is selected. The value on FWH0-FWH3 is compared to the IDSEL strapping on the FWH Flash Memory pins to select which FWH Flash Memory is being addressed. Description 3-9 7 ADDR XXXX I A 28-bit address phase is transferred starting with the most significant nibble first. For the multi-byte read operation, the least significant bits (MSIZE of them) are treated as Don't Care, and the read operation is started with each of these bits reset to 0. 10 1 MSIZE 0XXXb I This one clock cycle is driven by the host to determine how many bytes will be transferred. M50FW016 will support: single byte transfer (0000b), 4-byte transfer (0010b), 16-byte transfer (0100b) and 128-byte transfer (0111b). 11 1 TAR 1111b I The host drives FWH0-FWH3 to 1111b to indicate a turnaround cycle. 12 1 TAR 1111b (float) O The FWH Flash Memory takes control of FWH0-FWH3 during this cycle. 13-14 2 WSYNC 0101b O The FWH Flash Memory drives FWH0-FWH3 to 0101b (short wait-sync) for two clock cycles, indicating that the data is not yet available. Two wait-states are always included. 15 1 RSYNC 0000b O The FWH Flash Memory drives FWH0-FWH3 to 0000b, indicating that data will be available during the next clock cycle. 16-17 2 DATA XXXX O Data transfer is two CLK cycles, starting with the least significant nibble. If multi-byte read operation is enabled, repeat cycle 16-17 n times, where n = 2MSIZE – 1 Note 1 1 TAR 1111b O The FWH Flash Memory drives FWH0-FWH3 to 1111b to indicate a turnaround cycle. Note 2 1 TAR 1111b (float) N/A The FWH Flash Memory floats its outputs, the host takes control of FWH0-FWH3. Note: 1. Clock Cycle Number = (2MSIZE – 1) * 2 + 18 2. Clock Cycle Number = (2MSIZE – 1) * 2 + 19 Figure 5. FWH Bus Read Waveforms (Single Byte Read) CLK FWH4 FWH0-FWH3 Number of clock cycles START IDSEL ADDR MSIZE TAR SYNC DATA TAR 1 1 7 1 2 3 2 2 AI03437 13/45 M50FW016 Table 5. FWH Bus Write Field Definitions (Single Byte) Clock Cycle Number Clock Cycle Count Field FWH0FWH3 Memory I/O 1 1 START 1110b I On the rising edge of CLK with FWH4 Low, the contents of FWH0-FWH3 indicate the start of a FWH Write Cycle. 2 1 IDSEL XXXX I Indicates which FWH Flash Memory is selected. The value on FWH0-FWH3 is compared to the IDSEL strapping on the FWH Flash Memory pins to select which FWH Flash Memory is being addressed. 3-9 7 ADDR XXXX I A 28-bit address phase is transferred starting with the most significant nibble first. 10 1 MSIZE 0000b I Always 0000b (single byte transfer). 11-12 2 DATA XXXX I Data transfer is two cycles, starting with the least significant nibble. 13 1 TAR 1111b I The host drives FWH0-FWH3 to 1111b to indicate a turnaround cycle. 14 1 TAR 1111b (float) O The FWH Flash Memory takes control of FWH0-FWH3 during this cycle. 15 1 SYNC 0000b O The FWH Flash Memory drives FWH0-FWH3 to 0000b, indicating it has received data or a command. 16 1 TAR 1111b O The FWH Flash Memory drives FWH0-FWH3 to 1111b, indicating a turnaround cycle. 17 1 TAR 1111b (float) N/A Description The FWH Flash Memory floats its outputs and the host takes control of FWH0-FWH3. Figure 6. FWH Bus Write Waveforms (Single Byte) CLK FWH4 FWH0-FWH3 Number of clock cycles START IDSEL ADDR MSIZE DATA TAR SYNC TAR 1 1 7 1 2 2 1 2 AI03441 14/45 M50FW016 Table 6. FWH Bus Write Field Definitions (Quadruple Byte Program) Clock Cycle Number Clock Cycle Count Field FWH0FWH3 Memory I/O 1 1 START 1110b I On the rising edge of CLK with FWH4 Low, the contents of FWH0-FWH3 indicate the start of a FWH Write Cycle. 2 1 IDSEL XXXX I Indicates which FWH Flash Memory is selected. The value on FWH0-FWH3 is compared to the IDSEL strapping on the FWH Flash Memory pins to select which FWH Flash Memory is being addressed. 3-9 7 ADDR XXXX I A 28-bit address phase is transferred starting with the most significant nibble first. The A1-A0 lines are treated as Don't Care. 10 1 MSIZE 0010b I Always 0010b (quadruple byte transfer). Description 11-18 8 DATA XXXX I Data transfer is two cycles, starting with the least significant nibble. (The first pair of nibbles is that at the address with A1A0 set to 00, the second pair with A1-A0 set to 01, the third pair with A1-A0 set to 10, and the fourth pair with A1-A0 set to 11.) 19 1 TAR 1111b I The host drives FWH0-FWH3 to 1111b to indicate a turnaround cycle. 20 1 TAR 1111b (float) O The FWH Flash Memory takes control of FWH0-FWH3 during this cycle. 21 1 SYNC 0000b O The FWH Flash Memory drives FWH0-FWH3 to 0000b, indicating it has received data or a command. 22 1 TAR 1111b O The FWH Flash Memory drives FWH0-FWH3 to 1111b, indicating a turnaround cycle. 23 1 TAR 1111b (float) N/A The FWH Flash Memory floats its outputs and the host takes control of FWH0-FWH3. Figure 7. FWH Bus Write Waveforms (Quadruple Byte Program) CLK FWH4 FWH0-FWH3 Number of clock cycles START IDSEL ADDR MSIZE DATA TAR SYNC TAR 1 1 7 1 8 2 1 2 AI05784 15/45 M50FW016 Table 7. A/A Mux Bus Operations G W RP VPP DQ7-DQ0 Bus Read VIL VIH VIH Don't Care Data Output Bus Write VIH VIL VIH VCC or VPPH Data Input Output Disable VIH VIH VIH Don't Care Hi-Z VIL or VIH VIL or VIH VIL Don't Care Hi-Z Operation Reset Table 8. Manufacturer and Device Codes Operation G W RP A20-A1 A0 DQ7-DQ0 Manufacturer Code VIL VIH VIH VIL VIL 20h Device Code VIL VIH VIH VIL VIH 2Eh 16/45 M50FW016 COMMAND INTERFACE All Bus Write operations to the memory are interpreted by the Command Interface. Commands consist of one or more sequential Bus Write operations. After power-up or a Reset operation the memory enters Read mode. The commands are summarized in Table 10., Commands. Refer to Table 10. in conjunction with the text descriptions below. Read Memory Array Command. The Read Memory Array command returns the memory to its Read mode where it behaves like a ROM or EPROM. One Bus Write cycle is required to issue the Read Memory Array command and return the memory to Read mode. Once the command is issued the memory remains in Read mode until another command is issued. From Read mode Bus Read operations will access the memory array. While the Program/Erase Controller is executing a Program or Erase operation the memory will not accept the Read Memory Array command until the operation completes. Read Status Register Command. The Read Status Register command is used to read the Status Register. One Bus Write cycle is required to issue the Read Status Register command. Once the command is issued subsequent Bus Read operations read the Status Register until another command is issued. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. Read Electronic Signature Command. The Read Electronic Signature command is used to read the Manufacturer Code and the Device Code. One Bus Write cycle is required to issue the Read Electronic Signature command. Once the command is issued subsequent Bus Read operations read the Manufacturer Code or the Device Code until another command is issued. After the Read Electronic Signature Command is issued the Manufacturer Code and Device Code can be read using Bus Read operations using the addresses in Table 9. Program Command. The Program command can be used to program a value to one address in the memory array at a time. Two Bus Write operations are required to issue the command; the second Bus Write cycle latches the address and data in the internal state machine and starts the Program/Erase Controller. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. If the address falls in a protected block then the Program operation will abort, the data in the memory array will not be changed and the Status Register will output the error. During the Program operation the memory will only accept the Read Status Register command and the Program/Erase Suspend command. All other commands will be ignored. Typical Program times are given in Table 15. Note that the Program command cannot change a bit set at ‘0’ back to ‘1’ and attempting to do so will not cause any modification on its value. One of the Erase commands must be used to set all of the bits in the block to ‘1’. See Figure 16., Program Flowchart and Pseudo Code, for a suggested flowchart on using the Program command. Quadruple Byte Program Command (A/A Mux Mode). The Quadruple Byte Program Command can be used to program four adjacent bytes in the memory array at a time. The four bytes must differ only for the addresses A0 and A1. Programming should not be attempted when VPP is not at VPPH. Five Bus Write operations are required to issue the command. The second, the third and the fourth Bus Write cycle latches respectively the address and data of the first, the second and the third byte in the internal state machine. The fifth Bus Write cycle latches the address and data of the fourth byte in the internal state machine and starts the Program/Erase Controller. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. During the Quadruple Byte Program operation the memory will only accept the Read Status register command and the Program/Erase Suspend command. All other commands will be ignored. Typical Quadruple Byte Program times are given in Table 15.. Note that the Quadruple Byte Program command cannot change a bit set to ‘0’ back to ‘1’ and attempting to do so will not cause any modification on its value. One of the Erase commands must be used to set all of the bits in the block to ‘1’. See Figure 17., for a suggested flowchart on using the Quadruple Byte Program command. Quadruple Byte Program Command (FWH Mode). The Quadruple Byte Program Command can be used to program four adjacent bytes in the memory array at a time. The four bytes must differ only for the addresses A0 and A1. Programming should not be attempted when VPP is not at VPPH. Two Bus Write operations are required to issue the command. The second Bus Write cycle latches the 17/45 M50FW016 start address and four data bytes in the internal state machine and starts the Program/Erase Controller. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. During the Quadruple Byte Program operation the memory will only accept the Read Status register command and the Program/Erase Suspend command. All other commands will be ignored. Typical Quadruple Byte Program times are given in Table 15. Note that the Quadruple Byte Program command cannot change a bit set to ‘0’ back to ‘1’ and attempting to do so will not cause any modification on its value. One of the Erase commands must be used to set all of the bits in the block to ‘1’. See Figure 18., for a suggested flowchart on using the Quadruple Byte Program command. Chip Erase Command. The Chip Erase Command can be only used in A/A Mux mode to erase the entire chip at a time. Erasing should not be attempted when VPP is not at VPPH. The operation can also be executed if VPP is below VPPH, but result could be uncertain. Two Bus Write operations are required to issue the command and start the Program/Erase Controller. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. During the Chip Erase operation the memory will only accept the Read Status Register command. All other commands will be ignored. Typical Chip Erase times are given in Table 15. The Chip Erase command sets all of the bits in the memory to ‘1’. See Figure 20., Chip Erase Flowchart and Pseudo Code (A/A Mux Interface Only), for a suggested flowchart on using the Chip Erase command. Block Erase Command. The Block Erase command can be used to erase a block. Two Bus Write operations are required to issue the command; the second Bus Write cycle latches the block address in the internal state machine and starts the Program/Erase Controller. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the STATUS REGISTER for details on the definitions of the Status Register bits. If the block is protected then the Block Erase operation will abort, the data in the block will not be changed and the Status Register will output the error. During the Block Erase operation the memory will only accept the Read Status Register command and the Program/Erase Suspend command. All 18/45 other commands will be ignored. Typical Block Erase times are given in Table 15. The Block Erase command sets all of the bits in the block to ‘1’. All previous data in the block is lost. See Figure 21., Block Erase Flowchart and Pseudo Code, for a suggested flowchart on using the Erase command. Clear Status Register Command. The Clear Status Register command can be used to reset bits 1, 3, 4 and 5 in the Status Register to ‘0’. One Bus Write is required to issue the Clear Status Register command. Once the command is issued the memory returns to its previous mode, subsequent Bus Read operations continue to output the same data. The bits in the Status Register are sticky and do not automatically return to ‘0’ when a new Program or Erase command is issued. If an error occurs then it is essential to clear any error bits in the Status Register by issuing the Clear Status Register command before attempting a new Program or Erase command. Program/Erase Suspend Command. The Program/Erase Suspend command can be used to pause a Program or Block Erase operation. One Bus Write cycle is required to issue the Program/ Erase Suspend command and pause the Program/Erase Controller. Once the command is issued it is necessary to poll the Program/Erase Controller Status bit to find out when the Program/ Erase Controller has paused; no other commands will be accepted until the Program/Erase Controller has paused. After the Program/Erase Controller has paused, the memory will continue to output the Status Register until another command is issued. During the polling period between issuing the Program/Erase Suspend command and the Program/Erase Controller pausing it is possible for the operation to complete. Once Program/Erase Controller Status bit indicates that the Program/ Erase Controller is no longer active, the Program Suspend Status bit or the Erase Suspend Status bit can be used to determine if the operation has completed or is suspended. For timing on the delay between issuing the Program/Erase Suspend command and the Program/Erase Controller pausing see Table 15. During Program/Erase Suspend the Read Memory Array, Read Status Register, Read Electronic Signature and Program/Erase Resume commands will be accepted by the Command Interface. Additionally, if the suspended operation was Block Erase then the Program command will also be accepted; only the blocks not being erased may be read or programmed correctly. M50FW016 Resume command. Once the command is issued subsequent Bus Read operations read the Status Register. See Figure 19., Program Suspend and Resume Flowchart, and Pseudo Code, and Figure 22., Erase Suspend and Resume Flowchart, and Pseudo Code, for suggested flowcharts on using the Program/Erase Suspend command. Program/Erase Resume Command. The Program/Erase Resume command can be used to restart the Program/Erase Controller after a Program/Erase Suspend has paused it. One Bus Write cycle is required to issue the Program/Erase Table 9. Read Electronic Signature Code Address Data Manufacturer Code 00000h 20h Device Code 00001h 2Eh Table 10. Commands Read Memory Array Read Status Register Cycles Command Bus Write Operations Addr Data 1 X FFh 1st 2nd 3rd Addr Data 1 X 70h 1 X 90h 1 X 98h 2 X 40h PA PD 2 X 10h PA PD Quadruple Byte Program (A/A Mux Mode) 5 X 30h A1 PD Quadruple Byte Program (FWH Mode) 2 X 30h Aqbp PDqbp Chip Erase 2 X 80h X 10h Block Erase 2 X 20h BA D0h Clear Status Register 1 X 50h Program/Erase Suspend 1 X B0h Read Electronic Signature Program Program/Erase Resume Invalid/Reserved 1 X D0h 1 X 00h 1 X 01h 1 X 60h 1 X 2Fh 1 X C0h 4th 5th Addr Data Addr Data Addr Data A2 PD A3 PD A4 PD Note: X Don’t Care, PA Program Address, PD Program Data, A1,2,3,4 Consecutive Addresses, BA Any address in the Block. Read Memory Array. After a Read Memory Array command, read the memory as normal until another command is issued. Read Status Register. After a Read Status Register command, read the Status Register as normal until another command is issued. Read Electronic Signature. After a Read Electronic Signature command, read Manufacturer Code, Device Code until another command is issued. Block Erase, Program. After these commands read the Status Register until the command completes and another command is issued. Quadruple Byte Program (A/A Mux Mode). Addresses A1, A2, A3 and A4 must be consecutive addresses differing only for address bit A0 and A1. After this command, the user should repeatedly read the Status Register until the command has completed, at which point another command can be issued. Quadruple Byte Program (FWH Mode). Aqbp is the start address, A1 and A0 are treated as Don’t Care. The first data byte is programmed at the address that has A1-A0 at 00, the second at the address that has A1-A0 at 01, the third at the address that has A1A0 at 10, and the fourth at the address that has A1-A0 at 11. After this command, the user should repeatedly read the Status Register until the command has completed, at which point another command can be issued. Chip Erase. This command is only valid in A/A Mux mode. After this command read the Status Register until the command completes and another command is issued. Clear Status Register. After the Clear Status Register command bits 1, 3, 4 and 5 in the Status Register are reset to ‘0’. Program/Erase Suspend. After the Program/Erase Suspend command has been accepted, issue Read Memory Array, Read Status Register, Program (during Erase suspend) and Program/Erase resume commands. Program/Erase Resume. After the Program/Erase Resume command the suspended Program/Erase operation resumes, read the Status Register until the Program/Erase Controller completes and the memory returns to Read Mode. Invalid/Reserved. Do not use Invalid or Reserved commands. 19/45 M50FW016 STATUS REGISTER The Status Register provides information on the current or previous Program or Erase operation. Different bits in the Status Register convey different information and errors on the operation. To read the Status Register the Read Status Register command can be issued. The Status Register is automatically read after Program, Erase and Program/Erase Resume commands are issued. The Status Register can be read from any address. The Status Register bits are summarized in Table 11., Status Register Bits. Refer to Table 11. in conjunction with the text descriptions below. Program/Erase Controller Status (Bit 7). The Program/Erase Controller Status bit indicates whether the Program/Erase Controller is active or inactive. When the Program/Erase Controller Status bit is ‘0’, the Program/Erase Controller is active; when the bit is ‘1’, the Program/Erase Controller is inactive. The Program/Erase Controller Status is ‘0’ immediately after a Program/Erase Suspend command is issued until the Program/Erase Controller pauses. After the Program/Erase Controller pauses the bit is ‘1’. During Program and Erase operation the Program/Erase Controller Status bit can be polled to find the end of the operation. The other bits in the Status Register should not be tested until the Program/Erase Controller completes the operation and the bit is ‘1’. After the Program/Erase Controller completes its operation the Erase Status, Program Status, VPP Status and Block Protection Status bits should be tested for errors. Erase Suspend Status (Bit 6). The Erase Suspend Status bit indicates that a Block Erase operation has been suspended and is waiting to be resumed. The Erase Suspend Status should only be considered valid when the Program/Erase Controller Status bit is ‘1’ (Program/Erase Controller inactive); after a Program/Erase Suspend command is issued the memory may still complete the operation rather than entering the Suspend mode. When the Erase Suspend Status bit is ‘0’ the Program/Erase Controller is active or has completed its operation; when the bit is ‘1’ a Program/Erase Suspend command has been issued and the memory is waiting for a Program/Erase Resume command. When a Program/Erase Resume command is issued the Erase Suspend Status bit returns to ‘0’. Erase Status (Bit 5). The Erase Status bit can be used to identify if the memory has applied the maximum number of erase pulses to the block(s) 20/45 and still failed to verify that the block(s) has erased correctly. The Erase Status bit should be read once the Program/Erase Controller Status bit is ‘1’ (Program/Erase Controller inactive). When the Erase Status bit is ‘0’ the memory has successfully verified that the block(s) has erased correctly; when the Erase Status bit is ‘1’ the Program/Erase Controller has applied the maximum number of pulses to the block(s) and still failed to verify that the block(s) has erased correctly. Once the Erase Status bit is set to ‘1’ it can only be reset to ‘0’ by a Clear Status Register command or a hardware reset. If it is set to ‘1’ it should be reset before a new Program or Erase command is issued, otherwise the new command will appear to fail. (When Bit 4 and Bit 5 are set to ‘1’, a wrong command sequence has been attempted). Program Status (Bit 4). The Program Status bit can be used to identify if the memory has applied the maximum number of program pulses to the byte and still failed to verify that the byte has programmed correctly. The Program Status bit should be read once the Program/Erase Controller Status bit is ‘1’ (Program/Erase Controller inactive). When the Program Status bit is ‘0’ the memory has successfully verified that the byte has programmed correctly; when the Program Status bit is ‘1’ the Program/Erase Controller has applied the maximum number of pulses to the byte and still failed to verify that the byte has programmed correctly. Once the Program Status bit is set to ‘1’ it can only be reset to ‘0’ by a Clear Status Register command or a hardware reset. If it is set to ‘1’ it should be reset before a new Program or Erase command is issued, otherwise the new command will appear to fail. (When Bit 4 and Bit 5 are set to ‘1’, a wrong command sequence has been attempted). VPP Status (Bit 3). The VPP Status bit can be used to identify an invalid voltage on the VPP pin during Program and Erase operations. The VPP pin is only sampled at the beginning of a Program or Erase operation. Indeterminate results can occur if VPP becomes invalid during a Program or Erase operation. When the VPP Status bit is ‘0’ the voltage on the VPP pin was sampled at a valid voltage; when the VPP Status bit is ‘1’ the VPP pin has a voltage that is below the VPP Lockout Voltage, VPPLK, the memory is protected; Program and Erase operation cannot be performed. (The VPP status bit is ‘1’ if a Quadruple Byte Program command is issued and the VPP signal has a voltage less than VPPH applied to it.) Once the VPP Status bit set to ‘1’ it can only be reset to ‘0’ by a Clear Status Register command or a M50FW016 hardware reset. If it is set to ‘1’ it should be reset before a new Program or Erase command is issued, otherwise the new command will appear to fail. Program Suspend Status (Bit 2). The Program Suspend Status bit indicates that a Program operation has been suspended and is waiting to be resumed. The Program Suspend Status should only be considered valid when the Program/Erase Controller Status bit is ‘1’ (Program/Erase Controller inactive); after a Program/Erase Suspend command is issued the memory may still complete the operation rather than entering the Suspend mode. When the Program Suspend Status bit is ‘0’ the Program/Erase Controller is active or has completed its operation; when the bit is ‘1’ a Program/ Erase Suspend command has been issued and the memory is waiting for a Program/Erase Resume command. When a Program/Erase Resume command is issued the Program Suspend Status bit returns to ‘0’. Block Protection Status (Bit 1). The Block Protection Status bit can be used to identify if the Program or Block Erase operation has tried to modify the contents of a protected block. When the Block Protection Status bit is to ‘0’ no Program or Block Erase operations have been attempted to protected blocks since the last Clear Status Register command or hardware reset; when the Block Protection Status bit is ‘1’ a Program or Block Erase operation has been attempted on a protected block. Once it is set to ‘1’ the Block Protection Status bit can only be reset to ‘0’ by a Clear Status Register command or a hardware reset. If it is set to ‘1’ it should be reset before a new Program or Block Erase command is issued, otherwise the new command will appear to fail. Using the A/A Mux Interface the Block Protection Status bit is always ‘0’. Reserved (Bit 0). Bit 0 of the Status Register is reserved. Its value should be masked. Table 11. Status Register Bits Operation Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Program active ‘0’ X(1) ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ Program suspended ‘1 X(1) ‘0’ ‘0’ ‘0’ ‘1’ ‘0’ Program completed successfully ‘1’ X(1) ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ Program failure due to VPP Error ‘1’ X(1) ‘0’ ‘0’ ‘1’ ‘0’ ‘0’ Program failure due to Block Protection (FWH Interface only) ‘1’ X(1) ‘0’ ‘0’ ‘0’ ‘0’ ‘1’ Program failure due to cell failure ‘1’ X(1) ‘0’ ‘1’ ‘0’ ‘0’ ‘0’ Erase active ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ Block Erase suspended ‘1’ ‘1’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ Erase completed successfully ‘1’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ Erase failure due to VPP Error ‘1’ ‘0’ ‘0’ ‘0’ ‘1’ ‘0’ ‘0’ Block Erase failure due to Block Protection (FWH Interface only) ‘1’ ‘0’ ‘0’ ‘0’ ‘0’ ‘0’ ‘1’ Erase failure due to failed cell(s) ‘1’ ‘0’ ‘1’ ‘0’ ‘0’ ‘0’ ‘0’ Note: 1. For Program operations during Erase Suspend Bit 6 is ‘1’, otherwise Bit 6 is ‘0’. 21/45 M50FW016 FIRMWARE HUB (FWH) INTERFACE CONFIGURATION REGISTERS When the Firmware Hub Interface is selected several additional registers can be accessed. These registers control the protection status of the Blocks, read the General Purpose Input pins and identify the memory using the Electronic Signature codes. See Table 12. for the memory map of the Configuration Registers in the FWH Protocol. Lock Registers The Lock Registers control the protection status of the Blocks. Each Block has its own Lock Register. Three bits within each Lock Register control the protection of each block, the Write Lock Bit, the Read Lock Bit and the Lock Down Bit. The Lock Registers can be read and written, though care should be taken when writing as, once the Lock Down Bit is set, ‘1’, further modifications to the Lock Register cannot be made until cleared, to ‘0’, by a reset or power-up. See Table 13. for details on the bit definitions of the Lock Registers. Write Lock. The Write Lock Bit determines whether the contents of the Block can be modified (using the Program or Block Erase Command). When the Write Lock Bit is set, ‘1’, the block is write protected; any operations that attempt to change the data in the block will fail and the Status Register will report the error. When the Write Lock Bit is reset, ‘0’, the block is not write protected through the Lock Register and may be modified unless write protected through some other means. When VPP is less than VPPLK all blocks are protected and cannot be modified, regardless of the state of the Write Lock Bit. If Top Block Lock, TBL, is Low, VIL, then the Top Block (Block 31) is write protected and cannot be modified. Similarly, if Write Protect, WP, is Low, VIL, then the Main Blocks (Blocks 0 to 30) are write protected and cannot be modified. After power-up or reset the Write Lock Bit is always set to ‘1’ (write protected). Read Lock. The Read Lock bit determines whether the contents of the Block can be read (from Read mode). When the Read Lock Bit is set, ‘1’, the block is read protected; any operation that 22/45 attempts to read the contents of the block will read 00h instead. When the Read Lock Bit is reset, ‘0’, read operations in the Block return the data programmed into the block as expected. After power-up or reset the Read Lock Bit is always reset to ‘0’ (not read protected). Lock Down. The Lock Down Bit provides a mechanism for protecting software data from simple hacking and malicious attack. When the Lock Down Bit is set, ‘1’, further modification to the Write Lock, Read Lock and Lock Down Bits cannot be performed. A reset or power-up is required before changes to these bits can be made. When the Lock Down Bit is reset, ‘0’, the Write Lock, Read Lock and Lock Down Bits can be changed. Firmware Hub (FWH) General Purpose Input Register The Firmware Hub (FWH) General Purpose Input Register holds the state of the Firmware Hub Interface General Purpose Input pins, FGPI0-FGPI4. When this register is read, the state of these pins is returned. This register is read-only and writing to it has no effect. The signals on the Firmware Hub Interface General Purpose Input pins should remain constant throughout the whole Bus Read cycle in order to guarantee that the correct data is read. Manufacturer Code Register Reading the Manufacturer Code Register returns the manufacturer code for the memory. The manufacturer code for STMicroelectronics is 20h. This register is read-only and writing to it has no effect. Device Code Register Reading the Device Code Register returns the device code for the memory, 2Eh. This register is read-only and writing to it has no effect. Multi-Byte Read/Write Configuration Registers The Multi-Byte Read/Write Configuration Registers contain information as which multi-byte read and write access sizes will be accepted. The M50FW016 supports 4/16/128-byte reading and 4-byte writing. M50FW016 Table 12. Firmware Hub Register Configuration Map Memory Address Default Value Access Top Block Lock Register (Block 31) FBF0002h 01h R/W T_MINUS01_LK Top Block [-1] Lock Register (Block 30) FBE0002h 01h R/W T_MINUS02_LK Top Block [-2] Lock Register (Block 29) FBD0002h 01h R/W T_MINUS03_LK Top Block [-3] Lock Register (Block 28) FBC0002h 01h R/W T_MINUS04_LK Top Block [-4] Lock Register (Block 27) FBB0002h 01h R/W T_MINUS05_LK Top Block [-5] Lock Register (Block 26) FBA0002h 01h R/W T_MINUS06_LK Top Block [-6] Lock Register (Block 25) FB90002h 01h R/W T_MINUS07_LK Top Block [-7] Lock Register (Block 24) FB80002h 01h R/W T_MINUS08_LK Top Block [-8] Lock Register (Block 23) FB70002h 01h R/W T_MINUS09_LK Top Block [-9] Lock Register (Block 22) FB60002h 01h R/W T_MINUS10_LK Top Block [-10] Lock Register (Block 21) FB50002h 01h R/W T_MINUS11_LK Top Block [-11] Lock Register (Block 20) FB40002h 01h R/W T_MINUS12_LK Top Block [-12] Lock Register (Block 19) FB30002h 01h R/W T_MINUS13_LK Top Block [-13] Lock Register (Block 18) FB20002h 01h R/W T_MINUS14_LK Top Block [-14] Lock Register (Block 17) FB10002h 01h R/W T_MINUS15_LK Top Block [-15] Lock Register (Block 16) FB00002h 01h R/W T_MINUS16_LK Top Block [-16] Lock Register (Block 15) FAF0002h 01h R/W T_MINUS17_LK Top Block [-17] Lock Register (Block 14) FAE0002h 01h R/W T_MINUS18_LK Top Block [-18] Lock Register (Block 13) FAD0002h 01h R/W T_MINUS19_LK Top Block [-19] Lock Register (Block 12) FAC0002h 01h R/W T_MINUS20_LK Top Block [-20] Lock Register (Block 11) FAB0002h 01h R/W T_MINUS21_LK Top Block [-21] Lock Register (Block 10) FAA0002h 01h R/W T_MINUS22_LK Top Block [-22] Lock Register (Block 9) FA90002h 01h R/W T_MINUS23_LK Top Block [-23] Lock Register (Block 8) FA80002h 01h R/W T_MINUS24_LK Top Block [-24] Lock Register (Block 7) FA70002h 01h R/W T_MINUS25_LK Top Block [-25] Lock Register (Block 6) FA60002h 01h R/W T_MINUS26_LK Top Block [-26] Lock Register (Block 5) FA50002h 01h R/W T_MINUS27_LK Top Block [-27] Lock Register (Block 4) FA40002h 01h R/W T_MINUS28_LK Top Block [-28] Lock Register (Block 3) FA30002h 01h R/W T_MINUS29_LK Top Block [-29] Lock Register (Block 2) FA20002h 01h R/W T_MINUS30_LK Top Block [-30] Lock Register (Block 1) FA10002h 01h R/W T_MINUS31_LK Top Block [-31] Lock Register (Block 0) FA00002h 01h R/W Firmware Hub (FWH) General Purpose Input Register FBC0100h N/A R Manufacturer Code Register FBC0000h 20h R Mnemonic T_BLOCK_LK FGPI_REG MANUF_REG DEV_REG Register Name Device Code Register FBC0001h 2Eh R MBR_REG_LB Multi-Byte Read Configuration Register (Low Byte) FBC0005h 4Ah R MBR_REG_HB Multi-Byte Read Configuration Register (High Byte) FBC0006h 00h R MBW_REG_LB Multi-Byte Write Configuration Register (Low Byte) FBC0007h 02h R MBW_REG_HB Multi-Byte Write Configuration Register (High Byte) FBC0008h 00h R 23/45 M50FW016 Table 13. Lock Register Bit Definitions Bit Bit Name Value 7-3 2 1 0 Function Reserved ‘1’ Bus Read operations in this Block always return 00h. ‘0’ Bus read operations in this Block return the Memory Array contents. (Default value). ‘1’ Changes to the Read-Lock bit and the Write-Lock bit cannot be performed. Once a ‘1’ is written to the Lock-Down bit it cannot be cleared to ‘0’; the bit is always reset to ‘0’ following a Reset (using RP or INIT) or after power-up. ‘0’ Read-Lock and Write-Lock can be changed by writing new values to them. (Default value). ‘1’ Program and Block Erase operations in this Block will set an error in the Status Register. The memory contents will not be changed. (Default value). ‘0’ Program and Block Erase operations in this Block are executed and will modify the Block contents. Read-Lock Lock-Down Write-Lock Note: 1. Applies to Top Block Lock Register (T_BLOCK_LK) and Top Block [-1] Lock Register (T_MINUS01_LK) to Top Block [-31] Lock Register (T_MINUS31_LK). Table 14. General Purpose Input Register Definition Bit Bit Name Value 7-5 4 3 2 1 0 Function Reserved ‘1’ Input Pin FGPI4 is at VIH ‘0’ Input Pin FGPI4 is at VIL ‘1’ Input Pin FGPI3 is at VIH ‘0’ Input Pin FGPI3 is at VIL ‘1’ Input Pin FGPI2 is at VIH ‘0’ Input Pin FGPI2 is at VIL ‘1’ Input Pin FGPI1 is at VIH ‘0’ Input Pin FGPI1 is at VIL ‘1’ Input Pin FGPI0 is at VIH ‘0’ Input Pin FGPI0 is at VIL FGPI4 FGPI3 FGPI2 FGPI1 FGPI0 Note: 1. Applies to the General Purpose Input Register (FGPI_REG). 24/45 M50FW016 PROGRAM AND ERASE TIMES The Program and Erase times are shown in Table 15. Table 15. Program and Erase Times Typ (1) Max Unit 10 200 µs VPP = 12V ± 5% 10 (4) 200 µs A/A Mux VPP = 12V ± 5% 18 A/A Mux VPP = 12V ± 5% 0.1 (2) 5 s VPP = VCC 0.4 5 s VPP = 12V ± 5% 0.75 8 s VPP = VCC 1 10 s Program/Erase Suspend to Program pause (3) 5 µs Program/Erase Suspend to Block Erase pause (3) 30 µs Parameter Interface Test Condition Byte Program Quadruple Byte Program Chip Erase Block Program Block Erase Note: 1. 2. 3. 4. Min s TA = 25°C, VCC = 3.3V This time is obtained executing the Quadruple Byte Program Command. Sampled only, not 100% tested. Time to program four bytes. 25/45 M50FW016 MAXIMUM RATING Stressing the device above the rating listed in the Absolute Maximum Ratings table may cause permanent damage to the device. These are stress ratings only and operation of the device at these or any other conditions above those indicated in the Operating sections of this specification is not im- plied. Exposure to Absolute Maximum Rating conditions for extended periods may affect device reliability. Refer also to the STMicroelectronics SURE Program and other relevant quality documents. Table 16. Absolute Maximum Ratings Symbol Parameter Min Max Unit –65 150 °C TSTG Storage Temperature TLEAD Lead Temperature during Soldering VIO (2) Input or Output Voltage –0.6 VCC + 0.6 V VCC Supply Voltage –0.6 4 V VPP Program Voltage –0.6 13 V See note 1 Note: 1. Compliant with JEDEC Std J-STD-020B (for small body, Sn-Pb or Pb assembly), the ST ECOPACK ® 7191395 specification, and the European directive on Restrictions on Hazardous Substances (RoHS) 2002/95/EU. 2. Minimum Voltage may undershoot to –2V, for less than 20 ns, during transitions. Maximum Voltage may overshoot to VCC+2V, for less than 20 ns, during transitions. 26/45 M50FW016 DC AND AC PARAMETERS This section summarizes the operating measurement conditions, and the DC and AC characteristics of the device. The parameters in the DC and AC characteristics Tables that follow, are derived from tests performed under the Measurement Conditions summarized in Table 17., Table 18. and Table 19. Designers should check that the operating conditions in their circuit match the operating conditions when relying on the quoted parameters. Table 17. Operating Conditions Symbol TA VCC Parameter Min Max Unit Ambient Operating Temperature (Device Grade 1) 0 70 °C Ambient Operating Temperature (Device Grade 5) –20 85 °C 3 3.6 V Supply Voltage Table 18. FWH Interface AC Measurement Conditions Parameter Value Unit 10 pF ≤ 1.4 ns 0.2 VCC and 0.6 VCC V 0.4 VCC V Value Unit 30 pF Input Rise and Fall Times ≤ 10 ns Input Pulse Voltages 0 to 3 V 1.5 V Load Capacitance (CL) Input Rise and Fall Times Input Pulse Voltages Input and Output Timing Ref. Voltages Table 19. A/A Mux Interface AC Measurement Conditions Parameter Load Capacitance (CL) Input and Output Timing Ref. Voltages Figure 8. FWH Interface AC Testing Input Output Waveforms 0.6 VCC 0.4 VCC 0.2 VCC Input and Output AC Testing Waveform IO < ILO IO > ILO IO < ILO Output AC Tri-state Testing Waveform AI03404 27/45 M50FW016 Figure 9. A/A Mux Interface AC Testing Input Output Waveform 3V 1.5V 0V AI01417 Table 20. Impedance Symbol Parameter Test Condition CIN(1) Input Capacitance VIN = 0V CCLK(1) Clock Capacitance VIN = 0V LPIN(2) Recommended Pin Inductance Note: 1. Sampled only, not 100% tested. 2. See PCI Specification. 28/45 Min 3 Max Unit 13 pF 12 pF 20 nH M50FW016 Table 21. DC Characteristics Symbol VIH VIL Parameter Input High Voltage Input Low Voltage Interface Test Condition Min Max Unit FWH 0.5 VCC VCC + 0.5 V A/A Mux 0.7 VCC VCC + 0.3 V FWH –0.5 0.3 VCC V A/A Mux -0.5 0.8 V VIH(INIT) INIT Input High Voltage FWH 1.35 VCC + 0.5 V VIL(INIT) INIT Input Low Voltage FWH –0.5 0.2 VCC V ILI(2) Input Leakage Current 0V ≤ VIN ≤ VCC ±10 µA ILI2 IC, IDx Input Leakage Current IC, ID0, ID1, ID2, ID3 = VCC 200 µA RIL IC, IDx Input Pull Low Resistor 100 kΩ VOH Output High Voltage VOL ILO 20 FWH IOH = –500µA 0.9 VCC V A/A Mux IOH = –100µA VCC – 0.4 V FWH IOL = 1.5mA 0.1 VCC V A/A Mux IOL = 1.8mA 0.45 V 0V ≤ VOUT ≤ VCC ±10 µA 3 3.6 V 12.6 V Output Low Voltage Output Leakage Current VPP1 VPP Voltage VPPH VPP Voltage (Fast Program/Fast Erase) 11.4 VPPLK(1) VPP Lockout Voltage 1.5 VLKO(1) VCC Lockout Voltage 1.8 V 2.3 V ICC1 Supply Current (Standby) FWH FWH4 = 0.9 VCC, VPP = VCC All other inputs 0.9 VCC to 0.1 VCC VCC = 3.6V, f(CLK) = 33MHz 100 µA ICC2 Supply Current (Standby) FWH FWH4 = 0.1 VCC, VPP = VCC All other inputs 0.9 VCC to 0.1 VCC VCC = 3.6V, f(CLK) = 33MHz 10 mA ICC3 Supply Current (Any internal operation active) FWH VCC = VCC max, VPP = VCC f(CLK) = 33MHz IOUT = 0mA 60 mA ICC4 Supply Current (Read) A/A Mux G = VIH, f = 6MHz 20 mA Supply Current (Program/Erase) A/A Mux Program/Erase Controller Active 20 mA VPP Supply Current (Read/Standby) VPP > VCC 400 µA VPP Supply Current (Program/Erase active) VPP = VCC 5 µA VPP = 12V ± 5% 15 mA ICC5(1) IPP IPP1(1) Note: 1. Sampled only, not 100% tested. 2. Input leakage currents include High-Z output leakage for all bi-directional buffers with tri-state outputs. 29/45 M50FW016 Figure 10. FWH Interface Clock Waveform tCYC tHIGH tLOW 0.6 VCC 0.5 VCC 0.4 VCC, p-to-p 0.4 VCC (minimum) 0.3 VCC 0.2 VCC AI03403 Table 22. FWH Interface Clock Characteristics Symbol Parameter Test Condition Value Unit tCYC CLK Cycle Time(1) Min 30 ns tHIGH CLK High Time Min 11 ns tLOW CLK Low Time Min 11 ns Min 1 V/ns Max 4 V/ns CLK Slew Rate peak to peak Note: 1. Devices on the PCI Bus must work with any clock frequency between DC and 33MHz. Below 16MHz devices may be guaranteed by design rather than tested. Refer to PCI Specification. 30/45 M50FW016 Figure 11. FWH Interface AC Signal Timing Waveforms CLK tCHQV tCHQZ tDVCH tCHQX tCHDX FWH0-FWH3 VALID VALID OUTPUT DATA FLOAT OUTPUT DATA VALID INPUT DATA AI03405 Table 23. FWH Interface AC Signal Timing Characteristics Symbol PCI Symbol tCHQV tVAL CLK to Data Out tCHQX(1) tON tCHQZ Parameter Test Condition Value Unit Min 2 ns Max 11 ns CLK to Active (Float to Active Delay) Min 2 ns tOFF CLK to Inactive (Active to Float Delay) Max 28 ns tAVCH tDVCH tSU Input Set-up Time(2) Min 7 ns tCHAX tCHDX tH Input Hold Time(2) Min 0 ns Note: 1. The timing measurements for Active/Float transitions are defined when the current through the pin equals the leakage current specification. 2. Applies to all inputs except CLK. 31/45 M50FW016 Figure 12. Reset AC Waveforms RP, INIT tPLPH W, G, FWH4 tPHWL, tPHGL, tPHFL tPLRH RB AI03420 Table 24. Reset AC Characteristics Symbol Parameter tPLPH RP or INIT Reset Pulse Width tPLRH RP or INIT Low to Reset RP or INIT Slew Rate(1) tPHFL RP or INIT High to FWH4 Low tPHWL tPHGL RP High to Write Enable or Output Enable Low Note: 1. See Chapter 4 of the PCI Specification. 32/45 Test Condition Value Unit Min 100 ns Program/Erase Inactive Max 100 ns Program/Erase Active Max 30 µs Rising edge only Min 50 mV/ns FWH Interface only Min 30 µs A/A Mux Interface only Min 50 µs M50FW016 Figure 13. A/A Mux Interface Read AC Waveforms tAVAV ROW ADDR VALID A0-A10 NEXT ADDR VALID COLUMN ADDR VALID tAVCL tAVCH tCLAX tCHAX RC tCHQV G tGLQV tGHQZ tGLQX tGHQX DQ0-DQ7 VALID W tPHAV RP AI03406 Table 25. A/A Mux Interface Read AC Characteristics Symbol Parameter Test Condition Value Unit tAVAV Read Cycle Time Min 250 ns tAVCL Row Address Valid to RC Low Min 50 ns tCLAX RC Low to Row Address Transition Min 50 ns tAVCH Column Address Valid to RC high Min 50 ns tCHAX RC High to Column Address Transition Min 50 ns tCHQV(1) RC High to Output Valid Max 150 ns tGLQV(1) Output Enable Low to Output Valid Max 50 ns tPHAV RP High to Row Address Valid Min 1 µs tGLQX Output Enable Low to Output Transition Min 0 ns tGHQZ Output Enable High to Output Hi-Z Max 50 ns tGHQX Output Hold from Output Enable High Min 0 ns Note: 1. G may be delayed up to tCHQV – tGLQV after the rising edge of RC without impact on tCHQV. 33/45 M50FW016 Figure 14. A/A Mux Interface Write AC Waveforms Write erase or program setup A0-A10 R1 Write erase confirm or valid address and data C1 R2 tCLAX tAVCH tAVCL Automated erase or program delay Read Status Register Data Ready to write another command C2 tCHAX RC tWHWL tWLWH tCHWH W tVPHWH tWHGL G tWHRL RB tQVVPL VPP tDVWH DQ0-DQ7 DIN1 tWHDX DIN2 VALID SRD AI04194 Table 26. A/A Mux Interface Write AC Characteristics Symbol Parameter Test Condition Value Unit tWLWH Write Enable Low to Write Enable High Min 100 ns tDVWH Data Valid to Write Enable High Min 50 ns tWHDX Write Enable High to Data Transition Min 5 ns tAVCL Row Address Valid to RC Low Min 50 ns tCLAX RC Low to Row Address Transition Min 50 ns tAVCH Column Address Valid to RC High Min 50 ns tCHAX RC High to Column Address Transition Min 50 ns tWHWL Write Enable High to Write Enable Low Min 100 ns tCHWH RC High to Write Enable High Min 50 ns tVPHWH(1) VPP High to Write Enable High Min 100 ns tWHGL Write Enable High to Output Enable Low Min 30 ns tWHRL Write Enable High to RB Low Min 0 ns Output Valid, RB High to VPP Low Min 0 ns tQVVPL(1,2) Note: 1. Sampled only, not 100% tested. 2. Applicable if VPP is seen as a logic input (VPP < 3.6V). 34/45 M50FW016 PACKAGE MECHANICAL Figure 15. TSOP40 – 40 lead Plastic Thin Small Outline, 10x20 mm, Package Outline A2 N 1 e E B N/2 A D1 CP D DIE C A1 TSOP-a α L Note: Drawing is not to scale. Table 27. TSOP40 – 40 lead Plastic Thin Small Outline, 10x20 mm, Package Mechanical Data millimeters inches Symbol Typ Min A Max Typ Min 1.200 Max 0.0472 A1 0.050 0.150 0.0020 0.0059 A2 0.950 1.050 0.0374 0.0413 B 0.170 0.270 0.0067 0.0106 C 0.100 0.210 0.0039 0.0083 CP 0.100 0.0039 D 19.800 20.200 0.7795 0.7953 D1 18.300 18.500 0.7205 0.7283 – – – – E 9.900 10.100 0.3898 0.3976 L 0.500 0.700 0.0197 0.0276 α 0° 5° 0° 5° N 40 e 0.500 0.0197 40 35/45 M50FW016 PART NUMBERING Table 28. Ordering Information Scheme Example: M50FW016 N 1 T G Device Type M50 Architecture F = Firmware Hub Interface Operating Voltage W = 3.0 to 3.6V Device Function 016 = 16 Mbit (2Mb x8), Uniform Block Package N = TSOP40: 10 x 20 mm Device Grade 5 = Temperature range –20 to 85 °C. Device tested with standard test flow 1 = Temperature range 0 to 70 °C. Device tested with standard test flow Option blank = Standard Packing T = Tape & Reel Packing Plating Technology blank = Standard SnPb plating G = Lead-Free, RoHS compliant, Sb2O3-free and TBBA-free Devices are shipped from the factory with the memory content bits erased to ’1’. For a list of available options (Speed, Package, etc.) or for further information on any aspect of this device, please contact the ST Sales Office nearest to you. 36/45 M50FW016 APPENDIX A. FLOWCHARTS AND PSEUDO CODES Figure 16. Program Flowchart and Pseudo Code Start Program command: – write 40h or 10h – write Address & Data (memory enters read status state after the Program command) Write 40h or 10h Write Address & Data do: –read Status Register if Program/Erase Suspend command given execute suspend program loop NO Read Status Register Suspend b7 = 1 NO YES Suspend Loop while b7 = 1 YES b3 = 0 NO VPP Invalid Error (1, 2) If b3 = 1, VPP invalid error: – error handler NO Program Error (1, 2) If b4 = 1, Program error: – error handler NO Program to Protected Block Error (1, 2) YES b4 = 0 YES FWH Interface Only b1 = 0 If b1 = 1, Program to protected block error: – error handler YES End AI03407 Note: 1. A Status check of b1 (Protected Block), b3 (VPP invalid) and b4 (Program Error) can be made after each Program operation by following the correct command sequence. 2. If an error is found, the Status Register must be cleared before further Program/Erase Controller operations. 37/45 M50FW016 Figure 17. Quadruple Byte Program Flowchart and Pseudo Code (A/A Mux Interface Only) Start Write 30h Write Address 1 & Data 1 (3) Quadruple Byte Program command: – write 30h – write Address 1 & Data 1 (3) – write Address 2 & Data 2 (3) – write Address 3 & Data 3 (3) – write Address 4 & Data 4 (3) Write Address 2 & Data 2 (3) (memory enters read status state after the Quadruple Byte Program command) Write Address 3 & Data 3 (3) Write Address 4 & Data 4 (3) do: – read Status Register if Program/Erase Suspend command given execute suspend program loop NO Read Status Register Suspend b7 = 1 NO YES Suspend Loop while b7 = 1 YES b3 = 0 NO VPP Invalid Error (1, 2) If b3 = 1, VPP invalid error: – error handler NO Program Error (1, 2) If b4 = 1, Program error: – error handler YES b4 = 0 YES End AI03982 Note: 1. A Status check of b3 (VPP invalid) and b4 (Program Error) can be made after each Program operation by following the correct command sequence. 2. If an error is found, the Status Register must be cleared before further Program/Erase Controller operations. 3. Address 1, Address 2, Address 3 and Address 4 must be consecutive addresses differing only for address bits A0 and A1. 38/45 M50FW016 Figure 18. Quadruple Byte Program Flowchart and Pseudo Code (FWH Interface Only) Start Write 30h Write Start Address and 4 Data Bytes (3) Quadruple Byte Program command: – write 30h – write Start Address and 4 Data Bytes (3) (memory enters read status state after the Quadruple Byte Program command) do: – read Status Register if Program/Erase Suspend command given execute suspend program loop NO Read Status Register Suspend b7 = 1 NO YES Suspend Loop while b7 = 1 YES b3 = 0 NO VPP Invalid Error (1, 2) If b3 = 1, VPP invalid error: – error handler NO Program Error (1, 2) If b4 = 1, Program error: – error handler NO Program to Protected Block Error (1, 2) YES b4 = 0 YES b1 = 0 If b1 = 1, Program to protected block error: – error handler YES End AI05736B Note: 1. A Status check of b3 (VPP invalid) and b4 (Program Error) can be made after each Program operation by following the correct command sequence. 2. If an error is found, the Status Register must be cleared before further Program/Erase Controller operations. 3. A1 and A0 are treated as Don’t Care. Starting at the Start Address, the first data byte is programmed at the address that has A1A0 at 00, the second at the address that has A1-A0 at 01, the third at the address that has A1-A0 at 10, and the fourth at the address that has A1-A0 at 11. 39/45 M50FW016 Figure 19. Program Suspend and Resume Flowchart, and Pseudo Code Start Write B0h Program/Erase Suspend command: – write B0h – write 70h Write 70h do: – read Status Register Read Status Register b7 = 1 NO while b7 = 1 YES b2 = 1 NO Program Complete If b2 = 0 Program completed YES Write a read Command Read data from another address Write D0h Write FFh Program Continues Read Data Program/Erase Resume command: – write D0h to resume the program – if the Program operation completed then this is not necessary. The device returns to Read as normal (as if the Program/Erase suspend was not issued). AI03408 40/45 M50FW016 Figure 20. Chip Erase Flowchart and Pseudo Code (A/A Mux Interface Only) Start Chip Erase command: – write 80h – write 10h (memory enters read Status Register after the Chip Erase command) Write 80h Write 10h do: – read Status Register Read Status Register b7 = 1 NO while b7 = 1 YES b3 = 0 NO VPP Invalid Error (1) NO Command Sequence Error (1) If b3 = 1, VPP invalid error: – error handler YES b4, b5 = 0 If b4, b5 = 1, Command sequence error: – error handler YES b5 = 0 NO Erase Error (1) If b5 = 1, Erase error: – error handler YES End AI04195 Note: 1. If an error is found, the Status Register must be cleared before further Program/Erase Controller operations. 41/45 M50FW016 Figure 21. Block Erase Flowchart and Pseudo Code Start Block Erase command: – write 20h – write Block Address & D0h (memory enters read Status Register after the Block Erase command) Write 20h Write Block Address & D0h Suspend b7 = 1 do: – read Status Register – if Program/Erase Suspend command given execute suspend erase loop NO Read Status Register NO YES Suspend Loop while b7 = 1 YES b3 = 0 NO VPP Invalid Error (1) NO Command Sequence Error (1) If b3 = 1, VPP invalid error: – error handler YES b4, b5 = 0 If b4, b5 = 1, Command sequence error: – error handler YES b5 = 0 NO Erase Error (1) If b5 = 1, Erase error: – error handler YES FWH Interface Only b1 = 0 NO Erase to Protected Block Error (1) If b1 = 1, Erase to protected block error: – error handler YES End AI04196 Note: 1. If an error is found, the Status Register must be cleared before further Program/Erase Controller operations. 42/45 M50FW016 Figure 22. Erase Suspend and Resume Flowchart, and Pseudo Code Start Write B0h Program/Erase Suspend command: – write B0h – write 70h Write 70h do: – read Status Register Read Status Register b7 = 1 NO while b7 = 1 YES b6 = 1 NO Erase Complete If b6 = 0, Erase completed YES Read data from another block or Program Write D0h Write FFh Erase Continues Read Data Program/Erase Resume command: – write D0h to resume erase – if the Erase operation completed then this is not necessary. The device returns to Read as normal (as if the Program/Erase suspend was not issued). AI03410 43/45 M50FW016 REVISION HISTORY Table 29. Document Revision History Date Version May 2001 -01 First Issue October 2001 -02 Added LPC Bus Read and Bus Write cycles Added FWH 64 and 128 byte Bus Reading 21-Feb-2002 -03 Removed LPC Bus Read and Bus Write cycles 01-Mar-2002 -04 RFU pins must be left disconnected 30-Jul-2002 -05 Quadruple Byte Mode changed to 4/16/128 bytes 5.1 Revision numbering modified: a minor revision will be indicated by incrementing the digit after the dot, and a major revision, by incrementing the digit before the dot (revision version 05 equals 5.0) Datasheet promoted from Product Preview to Preliminary Data status. 6.0 Document imported in new template and reformatted. Temperature Range ordering information replaced by Device Grade, Standard packing option added and Plating Technology added to Table 28., Ordering Information Scheme. TLEAD parameter added to Table 16., Absolute Maximum Ratings and TBIAS parameter removed. Pin 39 changed from VCC to RFU in Figure 4., TSOP Connections. 13-Feb-2003 12-Jul-2004 44/45 Revision Details M50FW016 Information furnished is believed to be accurate and reliable. However, STMicroelectronics assumes no responsibility for the consequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of STMicroelectronics. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. STMicroelectronics products are not authorized for use as critical components in life support devices or systems without express written approval of STMicroelectronics. The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners. © 2004 STMicroelectronics - All rights reserved STMicroelectronics GROUP OF COMPANIES Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany Hong Kong - India - Israel - Italy - Japan - Malaysia - Malta - Morocco - Singapore Spain - Sweden - Switzerland - United Kingdom - United States www.st.com 45/45