AT45DB161E-SHD-T

AT45DB161E 16-Mbit DataFlash (with Extra 512-Kbits), 2.3V or 2.5V Minimum SPI Serial Flash Memory DATASHEET Features  Single 2.3V - 3.6V or 2.5V - 3.6V supply  Serial Peripheral Interface (SPI) compatible   Supports SPI modes 0 and 3 Supports RapidS™ operation  Continuous read capability through entire array    Up to 85MHz Low-power read option up to 15MHz Clock-to-output time (tV) of 6ns maximum  User configurable page size    512 bytes per page 528 bytes per page (default) Page size can be factory pre-configured for 512 bytes  Two fully independent SRAM data buffers (512/528 bytes)  Allows receiving data while reprogramming the main memory array  Flexible programming options    Byte/Page Program (1 to 512/528 bytes) directly into main memory Buffer Write Buffer to Main Memory Page Program  Flexible erase options     Page Erase (512/528 bytes) Block Erase (4KB) Sector Erase (128KB) Chip Erase (16-Mbits)  Program and Erase Suspend/Resume  Advanced hardware and software data protection features   Individual sector protection Individual sector lockdown to make any sector permanently read-only  128-byte, One-Time Programmable (OTP) Security Register   64 bytes factory programmed with a unique identifier 64 bytes user programmable  Hardware and software controlled reset options  JEDEC Standard Manufacturer and Device ID Read  Low-power dissipation     400nA Ultra-Deep Power-Down current (typical) 3µA Deep Power-Down current (typical) 25µA Standby current (typical at 20MHz) 11mA Active Read current (typical)  Endurance: 100,000 program/erase cycles per page minimum  Data retention: 20 years  Complies with full industrial temperature range  Green (Pb/Halide-free/RoHS compliant) packaging options     8-lead SOIC (0.150" wide and 0.208" wide) 8-pad Ultra-thin DFN (5 x 6 x 0.6mm) 9-ball Ultra-thin UBGA (6 x 6 x 0.6mm) Die in Wafer Form 8782H–DFLASH–7/2015 Description The Adesto® AT45DB161E is a 2.3V or 2.5V minimum, serial-interface sequential access Flash memory ideally suited for a wide variety of digital voice, image, program code, and data storage applications. The AT45DB161E also supports the RapidS serial interface for applications requiring very high speed operation. Its 17,301,504 bits of memory are organized as 4,096 pages of 512 bytes or 528 bytes each. In addition to the main memory, the AT45DB161E also contains two SRAM buffers of 512/528 bytes each. The buffers allow receiving of data while a page in the main memory is being reprogrammed. Interleaving between both buffers can dramatically increase a system's ability to write a continuous data stream. In addition, the SRAM buffers can be used as additional system scratch pad memory, and E2PROM emulation (bit or byte alterability) can be easily handled with a self-contained three step read-modify-write operation. Unlike conventional Flash memories that are accessed randomly with multiple address lines and a parallel interface, the Adesto DataFlash® uses a serial interface to sequentially access its data. The simple sequential access dramatically reduces active pin count, facilitates simplified hardware layout, increases system reliability, minimizes switching noise, and reduces package size. The device is optimized for use in many commercial and industrial applications where high-density, low-pin count, low-voltage, and low-power are essential. To allow for simple in-system re-programmability, the AT45DB161E does not require high input voltages for programming. The device operates from a single 2.3V to 3.6V or 2.5V to 3.6V power supply for the erase and program and read operations. The AT45DB161E is enabled through the Chip Select pin (CS) and accessed via a 3-wire interface consisting of the Serial Input (SI), Serial Output (SO), and the Serial Clock (SCK). All programming and erase cycles are self-timed. 1. Pin Configurations and Pinouts Figure 1-1. Pinouts 8-lead SOIC Top View SI SCK RESET CS Note: 1 2 3 4 1. 8 7 6 5 SO GND VCC WP 8-pad UDFN Top View 9-ball UBGA Top View (through package) (through package) SI SCK RESET CS SO GND 6 VCC 5 WP 1 8 2 7 3 4 SCK GND VCC CS NC WP SO SI RST The metal pad on the bottom of the UDFN package is not internally connected to a voltage potential. This pad can be a “no connect” or connected to GND. AT45DB161E 8782H–DFLASH–7/2015 2 Table 1-1. Pin Configurations Asserted State Type Low Input SCK Serial Clock: This pin is used to provide a clock to the device and is used to control the flow of data to and from the device. Command, address, and input data present on the SI pin is always latched on the rising edge of SCK, while output data on the SO pin is always clocked out on the falling edge of SCK. — Input SI Serial Input: The SI pin is used to shift data into the device. The SI pin is used for all data input including command and address sequences. Data on the SI pin is always latched on the rising edge of SCK. Data present on the SI pin will be ignored whenever the device is deselected (CS is deasserted). — Input SO Serial Output: The SO pin is used to shift data out from the device. Data on the SO pin is always clocked out on the falling edge of SCK. The SO pin will be in a high-impedance state whenever the device is deselected (CS is deasserted). — Output Low Input Low Input Symbol CS Name and Function Chip Select: Asserting the CS pin selects the device. When the CS pin is deasserted, the device will be deselected and normally be placed in the standby mode (not Deep Power-Down mode) and the output pin (SO) will be in a high-impedance state. When the device is deselected, data will not be accepted on the input pin (SI). A high-to-low transition on the CS pin is required to start an operation and a low-to-high transition is required to end an operation. When ending an internally self-timed operation such as a program or erase cycle, the device will not enter the standby mode until the completion of the operation. Write Protect: When the WP pin is asserted, all sectors specified for protection by the Sector Protection Register will be protected against program and erase operations regardless of whether the Enable Sector Protection command has been issued or not. The WP pin functions independently of the software controlled protection method. After the WP pin goes low, the contents of the Sector Protection Register cannot be modified. WP If a program or erase command is issued to the device while the WP pin is asserted, the device will simply ignore the command and perform no operation. The device will return to the idle state once the CS pin has been deasserted. The Enable Sector Protection command and the Sector Lockdown command, however, will be recognized by the device when the WP pin is asserted. The WP pin is internally pulled-high and may be left floating if hardware controlled protection will not be used. However, it is recommended that the WP pin also be externally connected to VCC whenever possible. RESET Reset: A low state on the reset pin (RESET) will terminate the operation in progress and reset the internal state machine to an idle state. The device will remain in the reset condition as long as a low level is present on the RESET pin. Normal operation can resume once the RESET pin is brought back to a high level. The device incorporates an internal power-on reset circuit, so there are no restrictions on the RESET pin during power-on sequences. If this pin and feature is not utilized, then it is recommended that the RESET pin be driven high externally. VCC Device Power Supply: The VCC pin is used to supply the source voltage to the device. Operations at invalid VCC voltages may produce spurious results and should not be attempted. — Power GND Ground: The ground reference for the power supply. GND should be connected to the system ground. — Ground AT45DB161E 8782H–DFLASH–7/2015 3 2. Block Diagram Figure 2-1. Block Diagram Flash Memory Array WP Page (512/528 bytes) Buffer 1 (512/528 bytes) SCK CS RESET VCC GND Buffer 2 (512/528 bytes) I/O Interface SI SO AT45DB161E 8782H–DFLASH–7/2015 4 Memory Array To provide optimal flexibility, the AT45DB161E memory array is divided into three levels of granularity comprising of sectors, blocks, and pages. Figure 3-1, Memory Architecture Diagram illustrates the breakdown of each level and details the number of pages per sector and block. Program operations to the DataFlash can be done at the full page level or at the byte level (a variable number of bytes). The erase operations can be performed at the chip, sector, block, or page level. Figure 3-1. Memory Architecture Diagram Sector Architecture Block 0 Page 0 Block 1 Sector 0b Block 2 Sector 0b = 248 pages 126,976/130,944 bytes Page Architecture 8 Pages Page 1 Block 0 Sector 0a = 8 pages 4,096/4,224 bytes Block Architecture Sector 0a Page 6 Page 7 Block 30 Sector 1 = 256 pages 131,072 /135,168 bytes Sector 14 = 256 pages 131,072/135,168 bytes Sector 15 = 256 pages 131,072/135,168 bytes Sector 1 Block 33 Page 9 Block 1 Block 32 Sector 2 = 256 pages 131,072/135,168 bytes Page 8 Block 31 Page 14 Page 15 Block 62 Page 16 Block 63 Page 17 Block 64 Page 18 Block 65 Sector 2 3. Block 510 Block 511 Block = 4,096/4,224 bytes Page 4,094 Page 4,095 Page = 512/528 bytes AT45DB161E 8782H–DFLASH–7/2015 5 4. Device Operation The device operation is controlled by instructions from the host processor. The list of instructions and their associated opcodes are contained in Table 15-1 on page 39 through Table 15-4 on page 40. A valid instruction starts with the falling edge of CS followed by the appropriate 8-bit opcode and the desired buffer or main memory address location. While the CS pin is low, toggling the SCK pin controls the loading of the opcode and the desired buffer or main memory address location through the SI (Serial Input) pin. All instructions, addresses, and data are transferred with the Most Significant Bit (MSB) first. Three address bytes are used to address memory locations in either the main memory array or in one of the SRAM buffers. The three address bytes will be comprised of a number of dummy bits and a number of actual device address bits, with the number of dummy bits varying depending on the operation being performed and the selected device page size. Buffer addressing for the standard DataFlash page size (528 bytes) is referenced in the datasheet using the terminology BFA9 - BFA0 to denote the 10 address bits required to designate a byte address within a buffer. The main memory addressing is referenced using the terminology PA11 - PA0 and BA9 - BA0, where PA11 - PA0 denotes the 12 address bits required to designate a page address, and BA9 - BA0 denotes the 10 address bits required to designate a byte address within the page. Therefore, when using the standard DataFlash page size, a total of 22 address bits are used. For the “power of 2” binary page size (512 bytes), the buffer addressing is referenced in the datasheet using the conventional terminology BFA8 - BFA0 to denote the nine address bits required to designate a byte address within a buffer. Main memory addressing is referenced using the terminology A20 - A0, where A20 - A9 denotes the 12 address bits required to designate a page address, and A8 - A0 denotes the nine address bits required to designate a byte address within a page. Therefore, when using the binary page size, a total of 21 address bits are used. 5. Read Commands By specifying the appropriate opcode, data can be read from the main memory or from either one of the two SRAM data buffers. The DataFlash supports RapidS protocols for Mode 0 and Mode 3. Please see Section 25., Detailed Bit-level Read Waveforms: RapidS Mode 0/Mode 3 diagrams in this datasheet for details on the clock cycle sequences for each mode. 5.1 Continuous Array Read (Legacy Command: E8h Opcode) By supplying an initial starting address for the main memory array, the Continuous Array Read command can be utilized to sequentially read a continuous stream of data from the device by simply providing a clock signal; no additional addressing information or control signals need to be provided. The DataFlash incorporates an internal address counter that will automatically increment on every clock cycle, allowing one continuous read from memory to be performed without the need for additional address sequences. To perform a Continuous Array Read using the standard DataFlash page size (528 bytes), an opcode of E8h must be clocked into the device followed by three address bytes (which comprise the 22-bit page and byte address sequence) and four dummy bytes. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify which page of the main memory array to read and the last 10 bits (BA9 - BA0) of the 22-bit address sequence specify the starting byte address within the page. To perform a Continuous Array Read using the binary page size (512 bytes), an opcode of E8h must be clocked into the device followed by three address bytes and four dummy bytes. The first 12 bits (A20 - A9) of the 21-bit address sequence specify which page of the main memory array to read and the last nine bits (A8 - A0) of the 21-bit address sequence specify the starting byte address within the page. The dummy bytes that follow the address bytes are needed to initialize the read operation. Following the dummy bytes, additional clock pulses on the SCK pin will result in data being output on the SO (serial output) pin. The CS pin must remain low during the loading of the opcode, the address bytes, the dummy bytes, and the reading of data. When the end of a page in the main memory is reached during a Continuous Array Read, the device will continue reading at the beginning of the next page with no delays incurred during the page boundary crossover (the crossover from the end of one page to the beginning of the next page). When the last bit in the main memory array has been read, AT45DB161E 8782H–DFLASH–7/2015 6 the device will continue reading back at the beginning of the first page of memory. As with crossing over page boundaries, no delays will be incurred when wrapping around from the end of the array to the beginning of the array. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Continuous Array Read is defined by the fCAR1 specification. The Continuous Array Read bypasses the data buffers and leaves the contents of the buffers unchanged. Warning: 5.2 This command is not recommended for new designs. Continuous Array Read (High Frequency Mode: 1Bh Opcode) This command can be used to read the main memory array sequentially at the highest possible operating clock frequency up to the maximum specified by fCAR4. To perform a Continuous Array Read using the standard DataFlash page size (528 bytes), the CS pin must first be asserted, and then an opcode of 1Bh must be clocked into the device followed by three address bytes and two dummy bytes. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify which page of the main memory array to read and the last 10 bits (BA9 - BA0) of the 22-bit address sequence specify the starting byte address within the page. To perform a Continuous Array Read using the binary page size (512 bytes), the opcode 1Bh must be clocked into the device followed by three address bytes (A20 - A0) and two dummy bytes. Following the dummy bytes, additional clock pulses on the SCK pin will result in data being output on the SO (Serial Output) pin. The CS pin must remain low during the loading of the opcode, the address bytes, the dummy bytes, and the reading of data. When the end of a page in the main memory is reached during a Continuous Array Read, the device will continue reading at the beginning of the next page with no delays incurred during the page boundary crossover (the crossover from the end of one page to the beginning of the next page). When the last bit in the main memory array has been read, the device will continue reading back at the beginning of the first page of memory. As with crossing over page boundaries, no delays will be incurred when wrapping around from the end of the array to the beginning of the array. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Continuous Array Read is defined by the fCAR1 specification. The Continuous Array Read bypasses both data buffers and leaves the contents of the buffers unchanged. 5.3 Continuous Array Read (High Frequency Mode: 0Bh Opcode) This command can be used to read the main memory array sequentially at higher clock frequencies up to the maximum specified by fCAR1. To perform a Continuous Array Read using the standard DataFlash page size (528 bytes), the CS pin must first be asserted, and then an opcode of 0Bh must be clocked into the device followed by three address bytes and one dummy byte. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify which page of the main memory array to read and the last 10 bits (BA9 - BA0) of the 22-bit address sequence specify the starting byte address within the page. To perform a Continuous Array Read using the binary page size (512 bytes), the opcode 0Bh must be clocked into the device followed by three address bytes (A20 - A0) and one dummy byte. Following the dummy byte, additional clock pulses on the SCK pin will result in data being output on the SO pin. The CS pin must remain low during the loading of the opcode, the address bytes, the dummy byte, and the reading of data. When the end of a page in the main memory is reached during a Continuous Array Read, the device will continue reading at the beginning of the next page with no delays incurred during the page boundary crossover (the crossover from the end of one page to the beginning of the next page). When the last bit in the main memory array has been read, the device will continue reading back at the beginning of the first page of memory. As with crossing over page boundaries, no delays will be incurred when wrapping around from the end of the array to the beginning of the array. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Continuous Array Read is defined by the fCAR1 specification. The Continuous Array Read bypasses both data buffers and leaves the contents of the buffers unchanged. 5.4 Continuous Array Read (Low Frequency Mode: 03h Opcode) This command can be used to read the main memory array sequentially at lower clock frequencies up to maximum specified by fCAR2. Unlike the previously described read commands, this Continuous Array Read command for the lower AT45DB161E 8782H–DFLASH–7/2015 7 clock frequencies does not require the clocking in of dummy bytes after the address byte sequence. To perform a Continuous Array Read using the standard DataFlash page size (528 bytes), the CS pin must first be asserted, and then an opcode of 03h must be clocked into the device followed by three address bytes. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify which page of the main memory array to read and the last 10 bits (BA9 - BA0) of the 22bit address sequence specify the starting byte address within the page. To perform a Continuous Array Read using the binary page size (512 bytes), the opcode 03h must be clocked into the device followed by three address bytes (A20 A0). Following the address bytes, additional clock pulses on the SCK pin will result in data being output on the SO pin. The CS pin must remain low during the loading of the opcode, the address bytes, and the reading of data. When the end of a page in the main memory is reached during a Continuous Array Read, the device will continue reading at the beginning of the next page with no delays incurred during the page boundary crossover (the crossover from the end of one page to the beginning of the next page). When the last bit in the main memory array has been read, the device will continue reading back at the beginning of the first page of memory. As with crossing over page boundaries, no delays will be incurred when wrapping around from the end of the array to the beginning of the array. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Continuous Array Read is defined by the fCAR2 specification. The Continuous Array Read bypasses both data buffers and leaves the contents of the buffers unchanged. 5.5 Continuous Array Read (Low Power Mode: 01h Opcode) This command is ideal for applications that want to minimize power consumption and do not need to read the memory array at high frequencies. Like the 03h opcode, this Continuous Array Read command allows reading the main memory array sequentially without the need for dummy bytes to be clocked in after the address byte sequence. The memory can be read at clock frequencies up to maximum specified by fCAR3. To perform a Continuous Array Read using the standard DataFlash page size (528 bytes), the CS pin must first be asserted, and then an opcode of 01h must be clocked into the device followed by three address bytes. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify which page of the main memory array to read and the last 10 bits (BA9 - BA0) of the 22-bit address sequence specify the starting byte address within the page. To perform a Continuous Array Read using the binary page size (512 bytes), the opcode 01h must be clocked into the device followed by three address bytes (A20 - A0). Following the address bytes, additional clock pulses on the SCK pin will result in data being output on the SO pin. The CS pin must remain low during the loading of the opcode, the address bytes, and the reading of data. When the end of a page in the main memory is reached during a Continuous Array Read, the device will continue reading at the beginning of the next page with no delays incurred during the page boundary crossover (the crossover from the end of one page to the beginning of the next page). When the last bit in the main memory array has been read, the device will continue reading back at the beginning of the first page of memory. As with crossing over page boundaries, no delays will be incurred when wrapping around from the end of the array to the beginning of the array. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Continuous Array Read is defined by the fCAR3 specification. The Continuous Array Read bypasses both data buffers and leaves the contents of the buffers unchanged. 5.6 Main Memory Page Read A Main Memory Page Read allows the reading of data directly from a single page in the main memory, bypassing both of the data buffers and leaving the contents of the buffers unchanged. To start a page read using the standard DataFlash page size (528 bytes), an opcode of D2h must be clocked into the device followed by three address bytes (which comprise the 22-bit page and byte address sequence) and four dummy bytes. The first 12 bits (PA11 - PA0) of the 22-bit address sequence specify the page in main memory to be read and the last 10 bits (BA9 - BA0) of the 22-bit address sequence specify the starting byte address within that page. To start a page read using the binary page size (512 bytes), the opcode D2h must be clocked into the device followed by three address bytes and four dummy bytes. The first 12 bits (A20 - A9) of the 21-bit address sequence specify which page of the main memory array to read, and the last nine bits (A8 - A0) of the 21-bit address sequence specify the starting byte address within that page. The dummy bytes that follow the address bytes are sent to initialize the read operation. Following the dummy bytes, the additional pulses on SCK result in data being output on the SO (serial output) pin. AT45DB161E 8782H–DFLASH–7/2015 8 The CS pin must remain low during the loading of the opcode, the address bytes, the dummy bytes, and the reading of data. Unlike the Continuous Array Read command, when the end of a page in main memory is reached, the device will continue reading back at the beginning of the same page rather than the beginning of the next page. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). The maximum SCK frequency allowable for the Main Memory Page Read is defined by the fSCK specification. The Main Memory Page Read bypasses both data buffers and leaves the contents of the buffers unchanged. 5.7 Buffer Read The SRAM data buffers can be accessed independently from the main memory array, and utilizing the Buffer Read command allows data to be sequentially read directly from either one of the buffers. Four opcodes, D4h or D1h for Buffer 1 and D6h or D3h for Buffer 2, can be used for the Buffer Read command. The use of each opcode depends on the maximum SCK frequency that will be used to read data from the buffers. The D4h and D6h opcode can be used at any SCK frequency up to the maximum specified by fCAR1 while the D1h and D3h opcode can be used for lower frequency read operations up to the maximum specified by fCAR2. To perform a Buffer Read using the standard DataFlash buffer size (528 bytes), the opcode must be clocked into the device followed by three address bytes comprised of 14 dummy bits and 10 buffer address bits (BFA9 - BFA0). To perform a Buffer Read using the binary buffer size (512 bytes), the opcode must be clocked into the device followed by three address bytes comprised of 15 dummy bits and nine buffer address bits (BFA8 - BFA0). Following the address bytes, one dummy byte must be clocked into the device to initialize the read operation if using opcodes D4h or D6h. The CS pin must remain low during the loading of the opcode, the address bytes, the dummy byte (if using opcodes D4h or D6h), and the reading of data. When the end of a buffer is reached, the device will continue reading back at the beginning of the buffer. A low-to-high transition on the CS pin will terminate the read operation and tri-state the output pin (SO). 6. Program and Erase Commands 6.1 Buffer Write Utilizing the Buffer Write command allows data clocked in from the SI pin to be written directly into either one of the SRAM data buffers. To load data into a buffer using the standard DataFlash buffer size (528 bytes), an opcode of 84h for Buffer 1 or 87h for Buffer 2 must be clocked into the device followed by three address bytes comprised of 14 dummy bits and 10 buffer address bits (BFA9 - BFA0). The 10 buffer address bits specify the first byte in the buffer to be written. To load data into a buffer using the binary buffer size (512 bytes), an opcode of 84h for Buffer 1 or 87h for Buffer 2, must be clocked into the device followed by 15 dummy bits and nine buffer address bits (BFA8 - BFA0). The nine buffer address bits specify the first byte in the buffer to be written. After the last address byte has been clocked into the device, data can then be clocked in on subsequent clock cycles. If the end of the data buffer is reached, the device will wrap around back to the beginning of the buffer. Data will continue to be loaded into the buffer until a low-to-high transition is detected on the CS pin. 6.2 Buffer to Main Memory Page Program with Built-In Erase The Buffer to Main Memory Page Program with Built-In Erase command allows data that is stored in one of the SRAM buffers to be written into an erased or programmed page in the main memory array. It is not necessary to pre-erase the page in main memory to be written because this command will automatically erase the selected page prior to the program cycle. To perform a Buffer to Main Memory Page Program with Built-In Erase using the standard DataFlash page size (528 bytes), an opcode of 83h for Buffer 1 or 86h for Buffer 2 must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be written, and 10 dummy bits. AT45DB161E 8782H–DFLASH–7/2015 9 To perform a Buffer to Main Memory Page Program with Built-In Erase using the binary page size (512 bytes), an opcode of 83h for Buffer 1 or 86h for Buffer 2 must be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory to be written, and nine dummy bits. When a low-to-high transition occurs on the CS pin, the device will first erase the selected page in main memory (the erased state is a Logic 1) and then program the data stored in the appropriate buffer into that same page in main memory. Both the erasing and the programming of the page are internally self-timed and should take place in a maximum time of tEP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent erase and program algorithm that can detect when a byte location fails to erase or program properly. If an erase or programming error arises, it will be indicated by the EPE bit in the Status Register. 6.3 Buffer to Main Memory Page Program without Built-In Erase The Buffer to Main Memory Page Program without Built-In Erase command allows data that is stored in one of the SRAM buffers to be written into a pre-erased page in the main memory array. It is necessary that the page in main memory to be written be previously erased in order to avoid programming errors. To perform a Buffer to Main Memory Page Program without Built-In Erase using the standard DataFlash page size (528 bytes), an opcode of 88h for Buffer 1 or 89h for Buffer 2 must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be written, and 10 dummy bits. To perform a Buffer to Main Memory Page Program using the binary page size (512 bytes), an opcode of 88h for Buffer 1 or 89h for Buffer 2 must be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory to be written, and nine dummy bits. When a low-to-high transition occurs on the CS pin, the device will program the data stored in the appropriate buffer into the specified page in the main memory. The page in main memory that is being programmed must have been previously erased using one of the erase commands (Page Erase, Block Erase, Sector Erase, or Chip Erase). The programming of the page is internally self-timed and should take place in a maximum time of tP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent programming algorithm that can detect when a byte location fails to program properly. If a programming error arises, it will be indicated by the EPE bit in the Status Register. 6.4 Main Memory Page Program through Buffer with Built-In Erase The Main Memory Page Program through Buffer with Built-In Erase command combines the Buffer Write and Buffer to Main Memory Page Program with Built-In Erase operations into a single operation to help simplify application firmware development. With the Main Memory Page Program through Buffer with Built-In Erase command, data is first clocked into either Buffer 1 or Buffer 2, the addressed page in memory is then automatically erased, and then the contents of the appropriate buffer are programmed into the just-erased main memory page. To perform a Main Memory Page Program through Buffer using the standard DataFlash page size (528 bytes), an opcode of 82h for Buffer 1 or 85h for Buffer 2 must first be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be written, and 10 buffer address bits (BFA9 - BFA0) that select the first byte in the buffer to be written. To perform a Main Memory Page Program through Buffer using the binary page size (512 bytes), an opcode of 82h for Buffer 1 or 85h for Buffer 2 must first be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory to be written, and nine buffer address bits (BFA8 - BFA0) that select the first byte in the buffer to be written. After all address bytes have been clocked in, the device will take data from the input pin (SI) and store it in the specified data buffer. If the end of the buffer is reached, the device will wrap around back to the beginning of the buffer. When there is a low-to-high transition on the CS pin, the device will first erase the selected page in main memory (the erased state is a Logic 1) and then program the data stored in the buffer into that main memory page. Both the erasing and the AT45DB161E 8782H–DFLASH–7/2015 10 programming of the page are internally self-timed and should take place in a maximum time of tEP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent erase and programming algorithm that can detect when a byte location fails to erase or program properly. If an erase or program error arises, it will be indicated by the EPE bit in the Status Register. 6.5 Main Memory Byte/Page Program through Buffer 1 without Built-In Erase The Main Memory Byte/Page Program through Buffer 1 without Built-In Erase command combines both the Buffer Write and Buffer to Main Memory Program without Built-In Erase operations to allow any number of bytes (1 to 512/528 bytes) to be programmed directly into previously erased locations in the main memory array. With the Main Memory Byte/Page Program through Buffer 1 without Built-In Erase command, data is first clocked into Buffer 1, and then only the bytes clocked into the buffer are programmed into the pre-erased byte locations in main memory. Multiple bytes up to the page size can be entered with one command sequence. To perform a Main Memory Byte/Page Program through Buffer 1 using the standard DataFlash page size (528 bytes), an opcode of 02h must first be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be written, and 10 buffer address bits (BFA9 - BFA0) that select the first byte in the buffer to be written. After all address bytes are clocked in, the device will take data from the input pin (SI) and store it in Buffer 1. Any number of bytes (1 to 528) can be entered. If the end of the buffer is reached, then the device will wrap around back to the beginning of the buffer. To perform a Main Memory Byte/Page Program through Buffer 1 using the binary page size (512 bytes), an opcode of 02h for Buffer 1 using must first be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory to be written, and nine buffer address bits (BFA8 - BFA0) that selects the first byte in the buffer to be written. After all address bytes are clocked in, the device will take data from the input pin (SI) and store it in Buffer 1. Any number of bytes (1 to 512) can be entered. If the end of the buffer is reached, then the device will wrap around back to the beginning of the buffer. When using the binary page size, the page and buffer address bits correspond to a 21-bit logical address (A20-A0) in the main memory. After all data bytes have been clocked into the device, a low-to-high transition on the CS pin will start the program operation in which the device will program the data stored in Buffer 1 into the main memory array. Only the data bytes that were clocked into the device will be programmed into the main memory. Example: If only two data bytes were clocked into the device, then only two bytes will be programmed into main memory and the remaining bytes in the memory page will remain in their previous state. The CS pin must be deasserted on a byte boundary (multiples of eight bits); otherwise, the operation will be aborted and no data will be programmed. The programming of the data bytes is internally self-timed and should take place in a maximum time of tP (the program time will be a multiple of the tBP time depending on the number of bytes being programmed). During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent programming algorithm that can detect when a byte location fails to program properly. If a programming error arises, it will be indicated by the EPE bit in the Status Register. 6.6 Read-Modify-Write A completely self-contained read-modify-write operation can be performed to reprogram any number of sequential bytes in a page in the main memory array without affecting the rest of the bytes in the same page. This command allows the device to easily emulate an EEPROM by providing a method to modify a single byte or more in the main memory in a single operation, without the need for pre-erasing the memory or the need for any external RAM buffers. The Read-Modify-Write command is essentially a combination of the Main Memory Page to Buffer Transfer, Buffer Write, and Buffer to Main Memory Page Program with Built-in Erase commands. To perform a Read-Modify-Write using the standard DataFlash page size (528 bytes), an opcode of 58h for Buffer 1 or 59h for Buffer 2 must be clocked into the device followed by three address bytes comprised of 2 dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be written, and 10 byte address bits (BA9 - BA0) that designate the starting byte address within the page to reprogram. To perform a Read-Modify-Write using the binary page size (512 bytes), an opcode of 58h for Buffer 1 or 59h for Buffer 2 AT45DB161E 8782H–DFLASH–7/2015 11 must be clocked into the device followed by three address bytes comprised of 3 dummy bits, 12 page address bits (A20 A9) that specify the page in the main memory to be written, and 9 byte address bits (A8 - A0) designate the starting byte address within the page to reprogram. After the address bytes have been clocked in, any number of sequential data bytes from one to 512/528 bytes can be clocked into the device. If the end of the buffer is reached when clocking in the data, then the device will wrap around back to the beginning of the buffer. After all data bytes have been clocked into the device, a low-to-high transition on the CS pin will start the self-contained, internal read-modify-write operation. Only the data bytes that were clocked into the device will be reprogrammed in the main memory. Example: If only one data byte was clocked into the device, then only one byte in main memory will be reprogrammed and the remaining bytes in the main memory page will remain in their previous state. The CS pin must be deasserted on a byte boundary (multiples of 8 bits); otherwise, the operation will be aborted and no data will be programmed. The reprogramming of the data bytes is internally self-timed and should take place in a maximum time of tP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent erase and programming algorithm that can detect when a byte location fails to erase or program properly. If an erase or program error arises, it will be indicated by the EPE bit in the Status Register. The Read-Modify-Write command uses the same opcodes as the Auto Page Rewrite command. If no data bytes are clocked into the device, then the device will perform an Auto Page Rewrite operation. See the Auto Page Rewrite command description on page 26 for more details. 6.7 Page Erase The Page Erase command can be used to individually erase any page in the main memory array allowing the Buffer to Main Memory Page Program without Built-In Erase command or the Main Memory Byte/Page Program through Buffer 1 command to be utilized at a later time. To perform a Page Erase with the standard DataFlash page size (528 bytes), an opcode of 81h must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) that specify the page in the main memory to be erased, and 10 dummy bits. To perform a Page Erase with the binary page size (512 bytes), an opcode of 81h must be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory to be erased, and nine dummy bits. When a low-to-high transition occurs on the CS pin, the device will erase the selected page (the erased state is a Logic 1). The erase operation is internally self-timed and should take place in a maximum time of tPE. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent erase algorithm that can detect when a byte location fails to erase properly. If an erase error arises, it will be indicated by the EPE bit in the Status Register. 6.8 Block Erase The Block Erase command can be used to erase a block of eight pages at one time. This command is useful when needing to pre-erase larger amounts of memory and is more efficient than issuing eight separate Page Erase commands. To perform a Block Erase with the standard DataFlash page size (528 bytes), an opcode of 50h must be clocked into the device followed by three address bytes comprised of two dummy bits, nine page address bits (PA11 - PA3), and 13 dummy bits. The nine page address bits are used to specify which block of eight pages is to be erased. To perform a Block Erase with the binary page size (512 bytes), an opcode of 50h must be clocked into the device followed by three address bytes comprised of three dummy bits, nine page address bits (A20 - A12), and 12 dummy bits. The nine page address bits are used to specify which block of eight pages is to be erased. AT45DB161E 8782H–DFLASH–7/2015 12 When a low-to-high transition occurs on the CS pin, the device will erase the selected block of eight pages. The erase operation is internally self-timed and should take place in a maximum time of tBE. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent erase algorithm that can detect when a byte location fails to erase properly. If an erase error arises, it will be indicated by the EPE bit in the Status Register. Table 6-1. 6.9 Block Erase Addressing PA11/ A20 PA10/ A19 PA9/ A18 PA8/ A17 PA7/ A16 PA6/ A15 PA5/ A14 PA4/ A13 PA3/ A12 PA2/ A11 PA1/ A10 PA0/ A9 Block 0 0 0 0 0 0 0 0 0 X X X 0 0 0 0 0 0 0 0 0 1 X X X 1 0 0 0 0 0 0 0 1 0 X X X 2 0 0 0 0 0 0 0 1 1 X X X 3 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 1 1 1 1 1 1 1 0 0 X X X 508 1 1 1 1 1 1 1 0 1 X X X 509 1 1 1 1 1 1 1 1 0 X X X 510 1 1 1 1 1 1 1 1 1 X X X 511 Sector Erase The Sector Erase command can be used to individually erase any sector in the main memory. The main memory array is comprised of 17 sectors, and only one sector can be erased at a time. To perform an erase of Sector 0a or Sector 0b with the standard DataFlash page size (528 bytes), an opcode of 7Ch must be clocked into the device followed by three address bytes comprised of two dummy bits, nine page address bits (PA11 - PA3), and 13 dummy bits. To perform a Sector 1-15 erase, an opcode of 7Ch must be clocked into the device followed by three address bytes comprised of two dummy bits, four page address bits (PA11 - PA8), and 18 dummy bits. To perform a Sector 0a or Sector 0b erase with the binary page size (512 bytes), an opcode of 7Ch must be clocked into the device followed by three address bytes comprised of three dummy bits, nine page address bits (A20 - A12), and 12 dummy bits. To perform a Sector 1-15 erase, an opcode of 7Ch must be clocked into the device followed by three dummy bits, four page address bits (A20 - A17), and 17 dummy bits. The page address bits are used to specify any valid address location within the sector to be erased. When a low-to high transition occurs on the CS pin, the device will erase the selected sector. The erase operation is internally self-timed and should take place in a maximum time of tSE. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device also incorporates an intelligent algorithm that can detect when a byte location fails to erase properly. If an erase error arises, it will be indicated by the EPE bit in the Status Register. AT45DB161E 8782H–DFLASH–7/2015 13 Table 6-2. 6.10 Sector Erase Addressing PA11/ A20 PA10/ A19 PA9/ A18 PA8/ A17 PA7/ A16 PA6/ A15 PA5/ A14 PA4/ A13 PA3/ A12 PA2/ A11 PA1/ A10 PA0/ A9 Sector 0 0 0 0 0 0 0 0 0 X X X 0a 0 0 0 0 0 0 0 0 1 X X X 0b 0 0 0 1 X X X X X X X X 1 0 0 1 0 X X X X X X X X 2 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 1 1 0 0 X X X X X X X X 12 1 1 0 1 X X X X X X X X 13 1 1 1 0 X X X X X X X X 14 1 1 1 1 X X X X X X X X 15 Chip Erase The Chip Erase command allows the entire main memory array to be erased can be erased at one time. To execute the Chip Erase command, a 4-byte command sequence of C7h, 94h, 80h, and 9Ah must be clocked into the device. Since the entire memory array is to be erased, no address bytes need to be clocked into the device, and any data clocked in after the opcode will be ignored. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to start the erase process. The erase operation is internally self-timed and should take place in a time of tCE. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. The Chip Erase command will not affect sectors that are protected or locked down; the contents of those sectors will remain unchanged. Only those sectors that are not protected or locked down will be erased. The WP pin can be asserted while the device is erasing, but protection will not be activated until the internal erase cycle completes. The device also incorporates an intelligent algorithm that can detect when a byte location fails to erase properly. If an erase error arises, it will be indicated by the EPE bit in the Status Register. Table 6-3. Chip Erase Command Command Byte 1 Byte 2 Byte 3 Byte 4 Chip Erase C7h 94h 80h 9Ah Figure 6-1. Chip Erase CS C7h 94h 80h 9Ah Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 14 6.11 Program/Erase Suspend In some code and data storage applications, it may not be possible for the system to wait the milliseconds required for the Flash memory to complete a program or erase cycle. The Program/Erase Suspend command allows a program or erase operation in progress to a particular 128KB sector of the main memory array to be suspended so that other device operations can be performed. Example: By suspending an erase operation to a particular sector, the system can perform functions such as a program or read operation within a different 128KB sector. Other device operations, such as Read Status Register, can also be performed while a program or erase operation is suspended. To perform a Program/Erase Suspend, an opcode of B0h must be clocked into the device. No address bytes need to be clocked into the device, and any data clocked in after the opcode will be ignored. When the CS pin is deasserted, the program or erase operation currently in progress will be suspended within a time of tSUSP. One of the Program Suspend bits (PS1 or PS2) or the Erase Suspend bit (ES) in the Status Register will then be set to the Logic 1 state. In addition, the RDY/BUSY bit in the Status Register will indicate that the device is ready for another operation. Read operations are not allowed to a 128KB sector that has had its program or erase operation suspended. If a read is attempted to a suspended sector, then the device will output undefined data. Therefore, when performing a Continuous Array Read operation and the device's internal address counter increments and crosses the sector boundary to a suspended sector, the device will then start outputting undefined data continuously until the address counter increments and crosses a sector boundary to an unsuspended sector. A program operation is not allowed to a sector that has been erase suspended. If a program operation is attempted to an erase suspended sector, then the program operation will abort. During an Erase Suspend, a program operation to a different 128KB sector can be started and subsequently suspended. This results in a simultaneous Erase Suspend/Program Suspend condition and will be indicated by the states of both the ES and PS1 or PS2 bits in the Status Register being set to a Logic 1. If a Reset command is performed, or if the RESET pin is asserted while a sector is erase suspended, then the suspend operation will be aborted and the contents of the sector will be left in an undefined state. However, if a reset is performed while a page is program or erase suspended, the suspend operation will abort but only the contents of the page that was being programmed or erased will be undefined; the remaining pages in the 128KB sector will retain their previous contents. AT45DB161E 8782H–DFLASH–7/2015 15 Table 6-4. Operations Allowed and Not Allowed During Suspend Operation During Program Suspend in Buffer 1 (PS1) Operation During Program Suspend in Buffer 2 (PS2) Operation During Erase Suspend (ES) Read Array (All Opcodes) Allowed Allowed Allowed Read Buffer 1 (All Opcodes) Allowed Allowed Allowed Read Buffer 2 (All Opcodes) Allowed Allowed Allowed Buffer 1 Write Not Allowed Allowed Allowed Buffer 2 Write Allowed Not Allowed Allowed Buffer 1 to Memory Program w/ Erase Not Allowed Not Allowed Not Allowed Buffer 2 to Memory Program w/ Erase Not Allowed Not Allowed Not Allowed Buffer 1 to Memory Program w/o Erase Not Allowed Not Allowed Allowed Buffer 2 to Memory Program w/o Erase Not Allowed Not Allowed Allowed Memory Program through Buffer 1 w/ Erase Not Allowed Not Allowed Not Allowed Memory Program through Buffer 2 w/ Erase Not Allowed Not Allowed Not Allowed Memory Program through Buffer 1 w/o Erase Not Allowed Not Allowed Allowed Auto Page Rewrite Not Allowed Not Allowed Not Allowed Page Erase Not Allowed Not Allowed Not Allowed Block Erase Not Allowed Not Allowed Not Allowed Sector Erase Not Allowed Not Allowed Not Allowed Chip Erase Not Allowed Not Allowed Not Allowed Enable Sector Protection Not Allowed Not Allowed Not Allowed Disable Sector Protection Not Allowed Not Allowed Not Allowed Erase Sector Protection Register Not Allowed Not Allowed Not Allowed Program Sector Protection Register Not Allowed Not Allowed Not Allowed Command Read Commands Program and Erase Commands Protection and Security Commands Read Sector Protection Register Allowed Allowed Allowed Not Allowed Not Allowed Not Allowed Allowed Allowed Allowed Freeze Sector Lockdown State Not Allowed Not Allowed Not Allowed Program Security Register Not Allowed Not Allowed Not Allowed Allowed Allowed Allowed Not Allowed Allowed Allowed Main Memory to Buffer 2 Transfer Allowed Not Allowed Allowed Main Memory to Buffer 1 Compare Not Allowed Allowed Allowed Sector Lockdown Read Sector Lockdown Read Security Register Additional Commands Main Memory to Buffer 1 Transfer Main Memory to Buffer 2 Compare Allowed Not Allowed Allowed Enter Deep Power-Down Not Allowed Not Allowed Not Allowed Resume from Deep Power-Down Not Allowed Not Allowed Not Allowed Enter Ultra-Deep Power-Down mode Not Allowed Not Allowed Not Allowed Read Configuration Register Allowed Allowed Allowed Read Status Register Allowed Allowed Allowed Read Manufacturer and Device ID Allowed Allowed Allowed Reset (via Hardware or Software) Allowed Allowed Allowed AT45DB161E 8782H–DFLASH–7/2015 16 6.12 Program/Erase Resume The Program/Erase Resume command allows a suspended program or erase operation to be resumed and continue where it left off. To perform a Program/Erase Resume, an opcode of D0h must be clocked into the device. No address bytes need to be clocked into the device, and any data clocked in after the opcode will be ignored. When the CS pin is deasserted, the program or erase operation currently suspended will be resumed within a time of tRES. The PS1 bit, PS2 bit, or ES bit in the Status Register will then be reset back to a Logic 0 state to indicate that the program or erase operation is no longer suspended. In addition, the RDY/BUSY bit in the Status Register will indicate that the device is busy performing a program or erase operation. During a simultaneous Erase Suspend/Program Suspend condition, issuing the Program/Erase Resume command will result in the program operation resuming first. After the program operation has been completed, the Program/Erase Resume command must be issued again in order for the erase operation to be resumed. While the device is busy resuming a program or erase operation, any attempts at issuing the Program/Erase Suspend command will be ignored. Therefore, if a resumed program or erase operation needs to be subsequently suspended again, the system must either wait the entire tRES time before issuing the Program/Erase Suspend command, or it must check the status of the RDY/BUSY bit or the appropriate PS1, PS2, or ES bit in the Status Register to determine if the previously suspended program or erase operation has resumed. 7. Sector Protection Two protection methods, hardware and software controlled, are provided for protection against inadvertent or erroneous program and erase cycles. The software controlled method relies on the use of software commands to enable and disable sector protection while the hardware controlled method employs the use of the Write Protect (WP) pin. The selection of which sectors that are to be protected or unprotected against program and erase operations is specified in the Nonvolatile Sector Protection Register. The status of whether or not sector protection has been enabled or disabled by either the software or the hardware controlled methods can be determined by checking the Status Register. 7.1 Software Sector Protection Software controlled protection is useful in applications in which the WP pin is not or cannot be controlled by a host processor. In such instances, the WP pin may be left floating (the WP pin is internally pulled high) and sector protection can be controlled using the Enable Sector Protection and Disable Sector Protection commands. If the device is power cycled, then the software controlled protection will be disabled. Once the device is powered up, the Enable Sector Protection command should be reissued if sector protection is desired and if the WP pin is not used. 7.1.1 Enable Sector Protection Sectors specified for protection in the Sector Protection Register can be protected from program and erase operations by issuing the Enable Sector Protection command. To enable the sector protection, a 4-byte command sequence of 3Dh, 2Ah, 7Fh, and A9h must be clocked into the device. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to enable the Sector Protection. Table 7-1. Enable Sector Protection Command Command Enable Sector Protection Byte 1 Byte 2 Byte 3 Byte 4 3Dh 2Ah 7Fh A9h AT45DB161E 8782H–DFLASH–7/2015 17 Figure 7-1. Enable Sector Protection CS SI 3Dh 2Ah 7Fh A9h Each transition represents eight bits 7.1.2 Disable Sector Protection To disable the sector protection, a 4-byte command sequence of 3Dh, 2Ah, 7Fh, and 9Ah must be clocked into the device. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to disable the sector protection. Table 7-2. Disable Sector Protection Command Command Disable Sector Protection Byte 1 Byte 2 Byte 3 Byte 4 3Dh 2Ah 7Fh 9Ah Figure 7-2. Disable Sector Protection CS SI 3Dh 2Ah 7Fh A9h Each transition represents eight bits 7.2 Hardware Controlled Protection Sectors specified for protection in the Sector Protection Register and the Sector Protection Register itself can be protected from program and erase operations by asserting the WP pin and keeping the pin in its asserted state. The Sector Protection Register and any sector specified for protection cannot be erased or programmed as long as the WP pin is asserted. In order to modify the Sector Protection Register, the WP pin must be deasserted. If the WP pin is permanently connected to GND, then the contents of the Sector Protection Register cannot be changed. If the WP pin is deasserted or permanently connected to VCC, then the contents of the Sector Protection Register can be modified. The WP pin will override the software controlled protection method but only for protecting the sectors. Example: If the sectors were not previously protected by the Enable Sector Protection command, then simply asserting the WP pin would enable the sector protection within the maximum specified tWPE time. When the WP pin is deasserted, however, the sector protection would no longer be enabled (after the maximum specified tWPD time) as long as the Enable Sector Protection command was not issued while the WP pin was asserted. If the Enable Sector Protection command was issued before or while the WP pin was asserted, then simply deasserting the WP pin would not disable the sector protection. In this case, the Disable Sector Protection command would need to be issued while the WP pin is deasserted to disable the sector protection. The Disable Sector Protection command is also ignored whenever the WP pin is asserted. A noise filter is incorporated to help protect against spurious noise that may inadvertently assert or deassert the WP pin. Figures 7-3 and Table 7-3 detail the sector protection status for various scenarios of the WP pin, the Enable Sector Protection command, and the Disable Sector Protection command. AT45DB161E 8782H–DFLASH–7/2015 18 Figure 7-3. WP Pin and Protection Status 1 3 2 WP Table 7-3. Time Period WP Pin and Protection Status WP Pin 1 Sector Protection Status Sector Protection Register Command Not Issued Previously X Disabled Read/Write — Issue Command Disabled Read/Write Issue Command — Enabled Read/Write X X Enabled Read Command Issued During Period 1 or 2 Not Issued Yet Enabled Read/Write — Issue Command Disabled Read/Write Issue Command — Enabled Read/Write High 2 Low 3 7.3 Enable Sector Protection Command Disable Sector Protection Command High Sector Protection Register The nonvolatile Sector Protection Register specifies which sectors are to be protected or unprotected with either the software or hardware controlled protection methods. The Sector Protection Register contains 16 bytes of data, of which byte locations 0 through 15 contain values that specify whether Sectors 0 through 15 will be protected or unprotected. The Sector Protection Register is user modifiable and must be erased before it can be reprogrammed. Table 7-4 illustrates the format of the Sector Protection Register. Table 7-4. Sector Protection Register Sector Number 0 (0a, 0b) 1 to 15 Protected FFh See Table 7-5 Unprotected Note: 1. Table 7-5. 00h The default values for bytes 0 through 15 are 00h when shipped from Adesto. Sector 0 (0a, 0b) Sector Protection Register Byte Value Bit 7:6 Bit 5:4 Bit 3:2 Bit 1:0 Sector 0a (Page 0-7) Sector 0b (Page 8-255) N/A N/A Data Value Sectors 0a and 0b Unprotected 00 00 XX XX 0xh Protect Sector 0a 11 00 XX XX Cxh Protect Sector 0b 00 11 XX XX 3xh Protect Sectors 0a and 0b 11 11 XX XX Fxh Note: 1. x = Don’t care AT45DB161E 8782H–DFLASH–7/2015 19 7.3.1 Erase Sector Protection Register In order to modify and change the values of the Sector Protection Register, it must first be erased using the Erase Sector Protection Register command. To erase the Sector Protection Register, a 4-byte command sequence of 3Dh, 2Ah, 7Fh, and CFh must be clocked into the device. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to initiate the internally self-timed erase cycle. The erasing of the Sector Protection Register should take place in a maximum time of tPE. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. If the device is powered-down before the completion of the erase cycle, then the contents of the Sector Protection Register cannot be guaranteed. The Sector Protection Register can be erased with sector protection enabled or disabled. Since the erased state (FFh) of each byte in the Sector Protection Register is used to indicate that a sector is specified for protection, leaving the sector protection enabled during the erasing of the register allows the protection scheme to be more effective in the prevention of accidental programming or erasing of the device. If for some reason an erroneous program or erase command is sent to the device immediately after erasing the Sector Protection Register and before the register can be reprogrammed, then the erroneous program or erase command will not be processed because all sectors would be protected. Table 7-6. Erase Sector Protection Register Command Command Erase Sector Protection Register Byte 1 Byte 2 Byte 3 Byte 4 3Dh 2Ah 7Fh CFh Figure 7-4. Erase Sector Protection Register CS SI 3Dh 2Ah 7Fh CFh Each transition represents eight bits 7.3.2 Program Sector Protection Register Once the Sector Protection Register has been erased, it can be reprogrammed using the Program Sector Protection Register command. To program the Sector Protection Register, a 4-byte command sequence of 3Dh, 2Ah, 7Fh, and FCh must be clocked into the device followed by 16 bytes of data corresponding to Sectors 0 through 15. After the last bit of the opcode sequence and data have been clocked in, the CS pin must be deasserted to initiate the internally self-timed program cycle. The programming of the Sector Protection Register should take place in a maximum time of tP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. If the device is powered-down before the completion of the erase cycle, then the contents of the Sector Protection Register cannot be guaranteed. If the proper number of data bytes is not clocked in before the CS pin is deasserted, then the protection status of the sectors corresponding to the bytes not clocked in cannot be guaranteed. Example: If only the first two bytes are clocked in instead of the complete 16 bytes, then the protection status of the last 14 sectors cannot be guaranteed. Furthermore, if more than 16 bytes of data is clocked into the device, then the data will wrap back around to the beginning of the register. For instance, if 17 bytes of data are clocked in, then the 17th byte will be stored at byte location 0 of the Sector Protection Register. The data bytes clocked into the Sector Protection Register need to be valid values (0xh, 3xh, Cxh, and Fxh for Sector 0a or Sector 0b, and 00h or FFh for other sectors) in order for the protection to function correctly. If a non-valid value is AT45DB161E 8782H–DFLASH–7/2015 20 clocked into a byte location of the Sector Protection Register, then the protection status of the sector corresponding to that byte location cannot be guaranteed. Example: If a value of 17h is clocked into byte location 2 of the Sector Protection Register, then the protection status of Sector 2 cannot be guaranteed. The Sector Protection Register can be reprogrammed while the sector protection is enabled or disabled. Being able to reprogram the Sector Protection Register with the sector protection enabled allows the user to temporarily disable the sector protection to an individual sector rather than disabling sector protection completely. The Program Sector Protection Register command utilizes Buffer 1 for processing. Therefore, the contents of Buffer 1 will be altered from its previous state when this command is issued. Table 7-7. Program Sector Protection Register Command Command Program Sector Protection Register Byte 1 Byte 2 Byte 3 Byte 4 3Dh 2Ah 7Fh FCh Figure 7-5. Program Sector Protection Register CS SI 3Dh 2Ah 7Fh FCh Data Byte n Data Byte n+1 Data Byte n + 15 Each transition represents eight bits 7.3.3 Read Sector Protection Register To read the Sector Protection Register, an opcode of 32h and three dummy bytes must be clocked into the device. After the last bit of the opcode and dummy bytes have been clocked in, any additional clock pulses on the SCK pin will result in the Sector Protection Register contents being output on the SO pin. The first byte (byte location 0) corresponds to Sector 0 (0a and 0b), the second byte corresponds to Sector 1, and the last byte (byte location 15) corresponds to Sector 15. Once the last byte of the Sector Protection Register has been clocked out, any additional clock pulses will result in undefined data being output on the SO pin. The CS pin must be deasserted to terminate the Read Sector Protection Register operation and put the output into a high-impedance state. Table 7-8. Read Sector Protection Register Command Command Read Sector Protection Register Note: 1. Byte 1 Byte 2 Byte 3 Byte 4 32h XXh XXh XXh XX = Dummy byte Figure 7-6. Read Sector Protection Register CS SI 32h XX XX XX Data n SO Data n+1 Data n + 15 Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 21 7.3.4 About the Sector Protection Register The Sector Protection Register is subject to a limit of 10,000 erase/program cycles. Users are encouraged to carefully evaluate the number of times the Sector Protection Register will be modified during the course of the application’s life cycle. If the application requires that the Security Protection Register be modified more than the specified limit of 10,000 cycles because the application needs to temporarily unprotect individual sectors (sector protection remains enabled while the Sector Protection Register is reprogrammed), then the application will need to limit this practice. Instead, a combination of temporarily unprotecting individual sectors along with disabling sector protection completely will need to be implemented by the application to ensure that the limit of 10,000 cycles is not exceeded. 8. Security Features 8.1 Sector Lockdown The device incorporates a sector lockdown mechanism that allows each individual sector to be permanently locked so that it becomes read-only (ROM). This is useful for applications that require the ability to permanently protect a number of sectors against malicious attempts at altering program code or security information. Warning: Once a sector is locked down, it can never be erased or programmed, and it can never be unlocked. To issue the sector lockdown command, a 4-byte command sequence of 3Dh, 2Ah, 7Fh, and 30h must be clocked into the device followed by three address bytes specifying any address within the sector to be locked down. After the last address bit has been clocked in, the CS pin must be deasserted to initiate the internally self-timed lockdown sequence. The lockdown sequence should take place in a maximum time of tP. During this time, the RDY/BUSY bit in the Status Register will indicate that the device is busy. If the device is powered-down before the completion of the lockdown sequence, then the lockdown status of the sector cannot be guaranteed. In this case, it is recommended that the user read the Sector Lockdown Register to determine the status of the appropriate sector lockdown bits or bytes and re-issue the Sector Lockdown command if necessary. Table 8-1. Sector Lockdown Command Command Sector Lockdown Byte 1 Byte 2 Byte 3 Byte 4 3Dh 2Ah 7Fh 30h Figure 8-1. Sector Lockdown CS SI 3Dh 2Ah 7Fh 30h Address byte Address byte Address byte Each transition represents eight bits 8.1.1 Read Sector Lockdown Register The nonvolatile Sector Lockdown Register specifies which sectors in the main memory are currently unlocked or have been permanently locked down. The Sector Lockdown Register is a read-only register and contains 16 bytes of data which correspond to Sectors 0 through 15. To read the Sector Lockdown Register, an opcode of 35h must be clocked into the device followed by three dummy bytes. After the last bit of the opcode and dummy bytes have been clocked in, the data for the contents of the Sector Lockdown Register will be clocked out on the SO pin. The first byte (byte location 0) corresponds to Sector 0 (0a and 0b), the second byte corresponds to Sector 1, and the last byte (byte location AT45DB161E 8782H–DFLASH–7/2015 22 15) corresponds to Sector 15. After the last byte of the Sector Lockdown Register has been read, additional pulses on the SCK pin will result in undefined data being output on the SO pin. Deasserting the CS pin will terminate the Read Sector Lockdown Register operation and put the SO pin into a high-impedance state. Table 8-2 details the format the Sector Lockdown Register. Table 8-2. Sector Lockdown Register Sector Number 0 (0a, 0b) 1 to 15 Locked FFh See Table 8-3 Unlocked Table 8-3. 00h Sector 0 (0a and 0b) Sector Lockdown Register Byte Value Bit 7:6 Bit 5:4 Bit 3:2 Bit 1:0 Sector 0a (Page 0-7) Sector 0b (Page 8-255) N/A N/A Data Value Sectors 0a and 0b Unlocked 00 00 00 00 00h Sector 0a Locked 11 00 00 00 C0h Sector 0b Locked 00 11 00 00 30h Sectors 0a and 0b Locked 11 11 00 00 F0h Table 8-4. Read Sector Lockdown Register Command Command Read Sector Lockdown Register Byte 1 Byte 2 Byte 3 Byte 4 35h XXh XXh XXh Figure 8-2. Read Sector Lockdown Register CS SI 32h XX XX XX Data n SO Data n+1 Data n + 15 Each transition represents eight bits 8.1.2 Freeze Sector Lockdown The Sector Lockdown command can be permanently disabled, and the current sector lockdown state can be permanently frozen so that no additional sectors can be locked down aside from those already locked down. Any attempts to issue the Sector Lockdown command after the Sector Lockdown State has been frozen will be ignored. To issue the Freeze Sector Lockdown command, the CS pin must be asserted and the opcode sequence of 34h, 55h, AAh, and 40h must be clocked into the device. Any additional data clocked into the device will be ignored. When the CS pin is deasserted, the current sector lockdown state will be permanently frozen within a time of tLOCK. In addition, the SLE bit in the Status Register will be permanently reset to a Logic 0 to indicate that the Sector Lockdown command is permanently disabled. AT45DB161E 8782H–DFLASH–7/2015 23 Table 8-5. Freeze Sector Lockdown Command Freeze Sector Lockdown Byte 1 Byte 2 Byte 3 Byte 4 34h 55h AAh 40h Figure 8-3. Freeze Sector Lockdown CS SI 34h 55h AAh 40h Each transition represents eight bits 8.2 Security Register The device contains a specialized Security Register that can be used for purposes such as unique device serialization or locked key storage. The register is comprised of a total of 128 bytes that is divided into two portions. The first 64 bytes (byte locations 0 through 63) of the Security Register are allocated as a One-Time Programmable space. Once these 64 bytes have been programmed, they cannot be erased or reprogrammed. The remaining 64 bytes of the register (byte locations 64 through 127) are factory programmed by Adesto and will contain a unique value for each device. The factory programmed data is fixed and cannot be changed. Table 8-6. Security Register Security Register Byte Number 0 Data Type 8.2.1 1 ··· One-Time User Programmable 63 64 65 ··· 127 Factory Programmed by Adesto Programming the Security Register The user programmable portion of the Security Register does not need to be erased before it is programmed. To program the Security Register, a 4-byte opcode sequence of 9Bh, 00h, 00h, and 00h must be clocked into the device. After the last bit of the opcode sequence has been clocked into the device, the data for the contents of the 64-byte user programmable portion of the Security Register must be clocked in. After the last data byte has been clocked in, the CS pin must be deasserted to initiate the internally self-timed program cycle. The programming of the Security Register should take place in a time of tP, during which time the RDY/BUSY bit in the Status Register will indicate that the device is busy. If the device is powered-down during the program cycle, then the contents of the 64-byte user programmable portion of the Security Register cannot be guaranteed. If the full 64 bytes of data are not clocked in before the CS pin is deasserted, then the values of the byte locations not clocked in cannot be guaranteed. Example: If only the first two bytes are clocked in instead of the complete 64 bytes, then the remaining 62 bytes of the user programmable portion of the Security Register cannot be guaranteed. Furthermore, if more than 64 bytes of data is clocked into the device, then the data will wrap back around to the beginning of the register. For example, if 65 bytes of data are clocked in, then the 65th byte will be stored at byte location 0 of the Security Register. AT45DB161E 8782H–DFLASH–7/2015 24 Warning: The user programmable portion of the Security Register can only be programmed one time. Therefore, it is not possible, for example, to only program the first two bytes of the register and then program the remaining 62 bytes at a later time. The Program Security Register command utilizes Buffer 1 for processing. Therefore, the contents of Buffer 1 will be altered from its previous state when this command is issued. Figure 8-4. Program Security Register CS SI 9Bh 00h 00h 00h Data n Data n+1 Data n+x Each transition represents eight bits 8.2.2 Reading the Security Register To read the Security Register, an opcode of 77h and three dummy bytes must be clocked into the device. After the last dummy bit has been clocked in, the contents of the Security Register can be clocked out on the SO pin. After the last byte of the Security Register has been read, additional pulses on the SCK pin will result in undefined data being output on the SO pin. Deasserting the CS pin will terminate the Read Security Register operation and put the SO pin into a high-impedance state. Figure 8-5. Read Security Register CS SI 77h XX XX XX Data n SO Data n+1 Data n+x Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 25 9. Additional Commands 9.1 Main Memory Page to Buffer Transfer A page of data can be transferred from the main memory to either Buffer 1 or Buffer 2. To transfer a page of data using the standard DataFlash page size (528 bytes), an opcode of 53h for Buffer 1 or 55h for Buffer 2 must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) which specify the page in main memory to be transferred, and 10 dummy bits. To transfer a page of data using the binary page size (512 bytes), an opcode of 53h for Buffer 1 and 55h for Buffer 2 must be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) which specify the page in the main memory to be transferred, and nine dummy bits. The CS pin must be low while toggling the SCK pin to load the opcode and the three address bytes from the input pin (SI). The transfer of the page of data from the main memory to the buffer will begin when the CS pin transitions from a low to a high state. During the page transfer time (tXFR), the RDY/BUSY bit in the Status Register can be read to determine whether or not the transfer has been completed. 9.2 Main Memory Page to Buffer Compare A page of data in main memory can be compared to the data in Buffer 1 or Buffer 2 as a method to ensure that data was successfully programmed after a Buffer to Main Memory Page Program command. To compare a page of data with the standard DataFlash page size (528 bytes), an opcode of 60h for Buffer 1 or 61h for Buffer 2 must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11 - PA0) which specify the page in the main memory to be compared to the buffer, and 10 dummy bits. To compare a page of data with the binary page size (512 bytes), an opcode of 60h for Buffer 1 or 61h for Buffer 2 must be clocked into the device followed by three address bytes comprised of three dummy bits, 12 page address bits (A20 - A9) which specify the page in the main memory to be compared to the buffer, and nine dummy bits. The CS pin must be low while toggling the SCK pin to load the opcode and the address bytes from the input pin (SI). On the low-to-high transition of the CS pin, the data bytes in the selected Main Memory Page will be compared with the data bytes in Buffer 1 or Buffer 2. During the compare time (tCOMP), the RDY/BUSY bit in the Status Register will indicate that the part is busy. On completion of the compare operation, bit 6 of the Status Register will be updated with the result of the compare. 9.3 Auto Page Rewrite This command only needs to be used if the possibility exists that static (non-changing) data may be stored in a page or pages of a sector and the other pages of the same sector are erased and programmed a large number of times. Applications that modify data in a random fashion within a sector may fall into this category. To preserve data integrity of a sector, each page within a sector must be updated/rewritten at least once within every 50,000 cumulative page erase/program operations within that sector. The Auto Page Rewrite command provides a simple and efficient method to “refresh” a page in the main memory array in a single operation. The Auto Page Rewrite command is a combination of the Main Memory Page to Buffer Transfer and Buffer to Main Memory Page Program with Built-In Erase commands. With the Auto Page Rewrite command, a page of data is first transferred from the main memory to Buffer 1 or Buffer 2 and then the same data (from Buffer 1 or Buffer 2) is programmed back into the same page of main memory, essentially “refreshing” the contents of that page. To start the Auto Page Rewrite operation with the standard DataFlash page size (528 bytes), a 1-byte opcode, 58H for Buffer 1 or 59H for Buffer 2, must be clocked into the device followed by three address bytes comprised of two dummy bits, 12 page address bits (PA11-PA0) that specify the page in main memory to be rewritten, and 10 dummy bits. To initiate an Auto Page Rewrite with the a binary page size (512 bytes), the opcode 58H for Buffer 1 or 59H for Buffer 2, must be clocked into the device followed by three address bytes consisting of three dummy bits, 12 page address bits (A20 - A9) that specify the page in the main memory that is to be rewritten, and nine dummy bits. When a low-to-high transition occurs on the CS pin, the part will first transfer data from the page in main memory to a buffer and then AT45DB161E 8782H–DFLASH–7/2015 26 program the data from the buffer back into same page of main memory. The operation is internally self-timed and should take place in a maximum time of tEP. During this time, the RDY/BUSY Status Register will indicate that the part is busy. If a sector is programmed or reprogrammed sequentially page by page and the possibility does not exist that there will be a page or pages of static data, then the programming algorithm shown in Figure 26-1 on page 61 is recommended. Otherwise, if there is a chance that there may be a page or pages of a sector that will contain static data, then the programming algorithm shown in Figure 26-2 on page 62 is recommended. Please contact Adesto for availability of devices that are specified to exceed the 50,000 cycle cumulative limit. 9.4 Status Register Read The 2-byte Status Register can be used to determine the device's ready/busy status, page size, a Main Memory Page to Buffer Compare operation result, the sector protection status, Freeze Sector Lockdown status, erase/program error status, Program/Erase Suspend status, and the device density. The Status Register can be read at any time, including during an internally self-timed program or erase operation. To read the Status Register, the CS pin must first be asserted and then the opcode D7h must be clocked into the device. After the opcode has been clocked in, the device will begin outputting Status Register data on the SO pin during every subsequent clock cycle. After the second byte of the Status Register has been clocked out, the sequence will repeat itself, starting again with the first byte of the Status Register, as long as the CS pin remains asserted and the clock pin is being pulsed. The data in the Status Register is constantly being updated, so each repeating sequence may output new data. The RDY/BUSY status is available for both bytes of the Status Register and is updated for each byte. Deasserting the CS pin will terminate the Status Register Read operation and put the SO pin into a high-impedance state. The CS pin can be deasserted at any time and does not require that a full byte of data be read. Table 9-1. Status Register Format – Byte 1 Type( Bit 7 6 Name RDY/BUS Y COMP Ready/Busy Status Compare Result 1) Density Code R 1 PROTECT Sector Protection Status R Note: Page Size Configuration Device is busy with an internal operation. 1 Device is ready. 0 Main memory page data matches buffer data. 1 Main memory page data does not match buffer data. R DENSITY PAGE SIZE 0 R 5:2 0 Description 101 1 16-Mbit 0 Sector protection is disabled. 1 Sector protection is enabled. 0 Device is configured for standard DataFlash page size (528 bytes). 1 Device is configured for “power of 2” binary page size (512 bytes). R 1. R = Readable only AT45DB161E 8782H–DFLASH–7/2015 27 Table 9-2. Status Register Format – Byte 2 Type( Bit 7 Name RDY/BUS Y Ready/Busy Status 1) RES Reserved for Future Use R 5 EPE Erase/Program Error R 4 RES Reserved for Future Use R 3 SLE Sector Lockdown Enabled R 1 0 PS2 PS1 ES Program Suspend Status (Buffer 2) R Program Suspend Status (Buffer 1) R Erase Suspend R Note: 1. R = Readable only 9.4.1 RDY/BUSY Bit 0 Device is busy with an internal operation. 1 Device is ready. 0 Reserved for future use. 0 Erase or program operation was successful. 1 Erase or program error detected. 0 Reserved for future use. 0 Sector Lockdown command is disabled. 1 Sector Lockdown command is enabled. 0 No program operation has been suspended while using Buffer 2. 1 A sector is program suspended while using Buffer 2. 0 No program operation has been suspended while using Buffer 1. 1 A sector is program suspended while using Buffer 1. 0 No sectors are erase suspended. 1 A sector is erase suspended. R 6 2 Description The RDY/BUSY bit is used to determine whether or not an internal operation, such as a program or erase, is in progress. To poll the RDY/BUSY bit to detect the completion of an internally timed operation, new Status Register data must be continually clocked out of the device until the state of the RDY/BUSY bit changes from a Logic 0 to a Logic 1. 9.4.2 COMP Bit The result of the most recent Main Memory Page to Buffer Compare operation is indicated using the COMP bit. If the COMP bit is a Logic 1, then at least one bit of the data in the Main Memory Page does not match the data in the buffer. 9.4.3 DENSITY Bits The device density is indicated using the DENSITY bits. For the AT45DB161E, the four bit binary value is 1011. The decimal value of these four binary bits does not actually equate to the device density; the four bits represent a combinational code relating to differing densities of DataFlash devices. The DENSITY bits are not the same as the density code indicated in the JEDEC Device ID information. The DENSITY bits are provided only for backward compatibility to older generation DataFlash devices. 9.4.4 PROTECT Bit The PROTECT bit provides information to the user on whether or not the sector protection has been enabled or disabled, either by the software-controlled method or the hardware-controlled method. AT45DB161E 8782H–DFLASH–7/2015 28 9.4.5 PAGE SIZE Bit The PAGE SIZE bit indicates whether the buffer size and the page size of the main memory array is configured for the “power of 2” binary page size (512 bytes) or the standard DataFlash page size (528 bytes). 9.4.6 EPE Bit The EPE bit indicates whether the last erase or program operation completed successfully or not. If at least one byte during the erase or program operation did not erase or program properly, then the EPE bit will be set to the Logic 1 state. The EPE bit will not be set if an erase or program operation aborts for any reason, such as an attempt to erase or program a protected region or a locked down sector or an attempt to erase or program a suspended sector. The EPE bit is updated after every erase and program operation. 9.4.7 SLE Bit The SLE bit indicates whether or not the Sector Lockdown command is enabled or disabled. If the SLE bit is a Logic 1, then the Sector Lockdown command is still enabled and sectors can be locked down. If the SLE bit is a Logic 0, then the Sector Lockdown command has been disabled and no further sectors can be locked down. 9.4.8 PS2 Bit The PS2 bit indicates if a program operation has been suspended while using Buffer 2. If the PS2 bit is a Logic 1, then a program operation has been suspended while Buffer 2 was being used, and any command attempts that would modify the contents of Buffer 2 will be ignored. 9.4.9 PS1 Bit The PS1 bit indicates if a program operation has been suspended while using Buffer 1. If the PS1 bit is a Logic 1, then a program operation has been suspended while Buffer 1 was being used, and any command attempts that would modify the contents of Buffer 1 will be ignored. 9.4.10 The ES bit The ES bit indicates whether or not an erase has been suspended. If the ES bit is a Logic 1, then an erase operation (page, block, sector, or chip) has been suspended. AT45DB161E 8782H–DFLASH–7/2015 29 10. Deep Power-Down During normal operation, the device will be placed in the standby mode to consume less power as long as the CS pin remains deasserted and no internal operation is in progress. The Deep Power-Down command offers the ability to place the device into an even lower power consumption state called the Deep Power-Down mode. When the device is in the Deep Power-Down mode, all commands including the Status Register Read command will be ignored with the exception of the Resume from Deep Power-Down command. Since all commands will be ignored, the mode can be used as an extra protection mechanism against program and erase operations. Entering the Deep Power-Down mode is accomplished by simply asserting the CS pin, clocking in the opcode B9h, and then deasserting the CS pin. Any additional data clocked into the device after the opcode will be ignored. When the CS pin is deasserted, the device will enter the Deep Power-Down mode within the maximum time of tEDPD. The complete opcode must be clocked in before the CS pin is deasserted, and the CS pin must be deasserted on an even byte boundary (multiples of eight bits); otherwise, the device will abort the operation and return to the standby mode once the CS pin is deasserted. In addition, the device will default to the standby mode after a power cycle. The Deep Power-Down command will be ignored if an internally self-timed operation such as a program or erase cycle is in progress. The Deep Power-Down command must be reissued after the internally self-timed operation has been completed in order for the device to enter the Deep Power-Down mode. Figure 10-1. Deep Power-Down CS tEDPD 0 1 2 3 4 5 6 7 SCK Opcode SI 1 0 1 1 1 0 0 1 MSB SO High-impedance Active Current ICC Standby Mode Current Deep Power-Down Mode Current AT45DB161E 8782H–DFLASH–7/2015 30 10.1 Resume from Deep Power-Down In order to exit the Deep Power-Down mode and resume normal device operation, the Resume from Deep Power-Down command must be issued. The Resume from Deep Power-Down command is the only command that the device will recognize while in the Deep Power-Down mode. To resume from the Deep Power-Down mode, the CS pin must first be asserted and then the opcode ABh must be clocked into the device. Any additional data clocked into the device after the opcode will be ignored. When the CS pin is deasserted, the device will exit the Deep Power-Down mode and return to the standby mode within the maximum time of tRDPD. After the device has returned to the standby mode, normal command operations such as Continuous Array Read can be resumed. If the complete opcode is not clocked in before the CS pin is deasserted, or if the CS pin is not deasserted on an even byte boundary (multiples of eight bits), then the device will abort the operation and return to the Deep Power-Down mode. Figure 10-2. Resume from Deep Power-Down CS tRDPD 0 1 2 3 4 5 6 7 SCK Opcode SI 1 0 1 0 1 0 1 1 MSB SO High-impedance Active Current ICC Deep Power-Down Mode Current Standby Mode Current AT45DB161E 8782H–DFLASH–7/2015 31 10.2 Ultra-Deep Power-Down The Ultra-Deep Power-Down mode allows the device to consume far less power compared to the standby and Deep Power-Down modes by shutting down additional internal circuitry. Since almost all active circuitry is shutdown in this mode to conserve power, the contents of the SRAM buffers cannot be maintained. Therefore, any data stored in the SRAM buffers will be lost once the device enters the Ultra-Deep Power-Down mode. When the device is in the Ultra-Deep Power-Down mode, all commands including the Status Register Read and Resume from Deep Power-Down commands will be ignored. Since all commands will be ignored, the mode can be used as an extra protection mechanism against program and erase operations. Entering the Ultra-Deep Power-Down mode is accomplished by simply asserting the CS pin, clocking in the opcode 79h, and then deasserting the CS pin. Any additional data clocked into the device after the opcode will be ignored. When the CS pin is deasserted, the device will enter the Ultra-Deep Power-Down mode within the maximum time of tEUDPD. The complete opcode must be clocked in before the CS pin is deasserted, and the CS pin must be deasserted on an even byte boundary (multiples of eight bits); otherwise, the device will abort the operation and return to the standby mode once the CS pin is deasserted. In addition, the device will default to the standby mode after a power cycle. The Ultra-Deep Power-Down command will be ignored if an internally self-timed operation such as a program or erase cycle is in progress. The Ultra-Deep Power-Down command must be reissued after the internally self-timed operation has been completed in order for the device to enter the Ultra-Deep Power-Down mode. Figure 10-3. Ultra-Deep Power-Down CS tEUDPD 0 1 2 3 4 5 6 7 SCK Opcode SI 0 1 1 1 1 0 0 1 MSB SO High-impedance Active Current ICC Standby Mode Current Ultra-Deep Power-Down Mode Current AT45DB161E 8782H–DFLASH–7/2015 32 10.2.1 Exit Ultra-Deep Power-Down To exit from the Ultra-Deep Power-Down mode, the CS pin must simply be pulsed by asserting the CS pin, waiting the minimum necessary tCSLU time, and then deasserting the CS pin again. To facilitate simple software development, a dummy byte opcode can also be entered while the CS pin is being pulsed just as in a normal operation like the Program Suspend operation; the dummy byte opcode is simply ignored by the device in this case. After the CS pin has been deasserted, the device will exit from the Ultra-Deep Power-Down mode and return to the standby mode within a maximum time of tXUDPD. If the CS pin is reasserted before the tXUDPD time has elapsed in an attempt to start a new operation, then that operation will be ignored and nothing will be performed. The system must wait for the device to return to the standby mode before normal command operations such as Continuous Array Read can be resumed. Since the contents of the SRAM buffers cannot be maintained while in the Ultra-Deep Power-Down mode, the SRAM buffers will contain undefined data when the device returns to the standby mode. Figure 10-4. Exit Ultra-Deep Power-Down CS tCSLU tXUDPD SO High-impedance Active Current ICC Standby Mode Current Ultra-Deep Power-Down Mode Current AT45DB161E 8782H–DFLASH–7/2015 33 11. Buffer and Page Size Configuration The memory array of DataFlash devices is actually larger than other Serial Flash devices in that extra user-accessible bytes are provided in each page of the memory array. For the AT45DB161E, there are an extra 16 bytes of memory in each page for a total of an extra 64KB (512-Kbits) of user-accessible memory. Therefore, the device density is actually 16.5-Mbits instead of 16-Mbits. Some applications, however, may not want to take advantage of this extra memory and instead architect their software to operate on a “power of 2” binary, logical addressing scheme. To allow this, the DataFlash can be configured so that the buffer and page sizes are 512 bytes instead of the standard 528 bytes. In addition, the configuration of the buffer and page sizes is reversible and can be changed from 528 bytes to 512 bytes or from 512 bytes to 528 bytes. The configured setting is stored in an internal nonvolatile register so that the buffer and page size configuration is not affected by power cycles. The nonvolatile register has a limit of 10,000 erase/program cycles; therefore, care should be taken to not switch between the size options more than 10,000 times. Devices are initially shipped from Adesto with the buffer and page sizes set to 528 bytes. Devices can be ordered from Adesto pre-configured for the “power of 2” binary size of 512 bytes. For details, see Section 27., Ordering Information on page 63. To configure the device for “power of 2” binary page size (512 bytes), a 4-byte opcode sequence of 3Dh, 2Ah, 80h, and A6h must be clocked into the device. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to initiate the internally self-timed configuration process and nonvolatile register program cycle. The programming of the nonvolatile register should take place in a time of tEP, during which time the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device does not need to be power cycled after the completion of the configuration process and register program cycle in order for the buffer and page size to be configured to 512 bytes. To configure the device for standard DataFlash page size (528 bytes), a 4-byte opcode sequence of 3Dh, 2Ah, 80h, and A7h must be clocked into the device. After the last bit of the opcode sequence has been clocked in, the CS pin must be deasserted to initial the internally self-timed configuration process and nonvolatile register program cycle. The programming of the nonvolatile register should take place in a time of tEP, during which time the RDY/BUSY bit in the Status Register will indicate that the device is busy. The device does not need to be power cycled after the completion of the configuration process and register program cycle in order for the buffer and page size to be configured to 528 bytes. Table 11-1. Buffer and Page Size Configuration Commands Command Byte 1 Byte 2 Byte 3 Byte 4 “Power of 2” binary page size (512 bytes) 3Dh 2Ah 80h A6h DataFlash page size (528 bytes) 3Dh 2Ah 80h A7h Figure 11-1. Buffer and Page Size Configuration CS SI 3Dh 2Ah 80h Opcode Byte 4 Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 34 12. Manufacturer and Device ID Read Identification information can be read from the device to enable systems to electronically query and identify the device while it is in the system. The identification method and the command opcode comply with the JEDEC Standard for “Manufacturer and Device ID Read Methodology for SPI Compatible Serial Interface Memory Devices”. The type of information that can be read from the device includes the JEDEC-defined Manufacturer ID, the vendor-specific Device ID, and the vendor-specific Extended Device Information. The Read Manufacturer and Device ID command is limited to a maximum clock frequency of fCLK. Since not all Flash devices are capable of operating at very high clock frequencies, applications should be designed to read the identification information from the devices at a reasonably low clock frequency to ensure that all devices to be used in the application can be identified properly. Once the identification process is complete, the application can then increase the clock frequency to accommodate specific Flash devices that are capable of operating at the higher clock frequencies. To read the identification information, the CS pin must first be asserted and then the opcode 9Fh must be clocked into the device. After the opcode has been clocked in, the device will begin outputting the identification data on the SO pin during the subsequent clock cycles. The first byte to be output will be the Manufacturer ID, followed by two bytes of the Device ID information. The fourth byte output will be the Extended Device Information (EDI) String Length, which will be 01h indicating that one byte of EDI data follows. After the one byte of EDI data is output, the SO pin will go into a high-impedance state; therefore, additional clock cycles will have no affect on the SO pin and no data will be output. As indicated in the JEDEC Standard, reading the EDI String Length and any subsequent data is optional. Deasserting the CS pin will terminate the Manufacturer and Device ID Read operation and put the SO pin into a high-impedance state. The CS pin can be deasserted at any time and does not require that a full byte of data be read. Table 12-1. Manufacturer and Device ID Information Byte No. Data Type Value 1 Manufacturer ID 1Fh 2 Device ID (Byte 1) 26h 3 Device ID (Byte 2) 00h 4 Extended Device Information (EDI) String Length 01h 5 [Optional to Read] Extended Device Information Byte 1 00h Table 12-2. Manufacturer and Device ID Details Data Type Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 1 1 1 0 Hex Value Details JEDEC Assigned Code Manufacturer ID 0 Device ID (Byte 1) Device ID (Byte 2) 0 0 1 1 Family Code 0 0 0 1Fh JEDEC code: 0001 1111 (1Fh for Adesto) 26h Family code: 001 (AT45Dxxx Family) Density code: 00110 (16-Mbit) 00h Sub code: 000 (Standard Series) Product variant:00000 Density Code 1 0 Sub Code 0 1 0 1 Product Variant 0 0 0 0 0 0 AT45DB161E 8782H–DFLASH–7/2015 35 Table 12-3. EDI Data Byte Number Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 RFU Bit 2 Bit 1 Bit 0 Hex Valu e Device Revision 1 00h 0 0 0 0 0 0 0 0 Details RFU: Reserved for Future Use Device revision:00000 (Initial Version) Figure 12-1. Read Manufacturer and Device ID CS 0 6 7 8 14 15 16 22 23 24 30 31 32 38 39 40 46 SCK Opcode SI SO 9Fh High-impedance Note: Each transition 1Fh 26h 00h 01h 00h Manufacturer ID Device ID Byte 1 Device ID Byte 2 EDI String Length EDI Data Byte 1 shown for SI and SO represents one byte (8 bits) AT45DB161E 8782H–DFLASH–7/2015 36 13. Software Reset In some applications, it may be necessary to prematurely terminate a program or erase cycle early rather than wait the hundreds of microseconds or milliseconds necessary for the program or erase operation to complete normally. The Software Reset command allows a program or erase operation in progress to be ended abruptly and returns the device to an idle state. To perform a Software Reset, the CS pin must be asserted and a 4-byte command sequence of F0h, 00h, 00h, and 00h must be clocked into the device. Any additional data clocked into the device after the last byte will be ignored. When the CS pin is deasserted, the program or erase operation currently in progress will be terminated within a time tSWRST. Since the program or erase operation may not complete before the device is reset, the contents of the page being programmed or erased cannot be guaranteed to be valid. The Software Reset command has no effect on the states of the Sector Protection Register, the Sector Lockdown Register, or the buffer and page size configuration. The PS2, PS1, and ES bits of the Status Register, however, will be reset back to their default states. If a Software Reset operation is performed while a sector is erase suspended, the suspend operation will abort and the contents of the page or block being erased in the suspended sector will be left in an undefined state. If a Software Reset is performed while a sector is program suspended, the suspend operation will abort and the contents of the page that was being programmed and subsequently suspended will be undefined. The remaining pages in the sector will retain their previous contents. The complete 4-byte opcode must be clocked into the device before the CS pin is deasserted, and the CS pin must be deasserted on a byte boundary (multiples of eight bits); otherwise, no reset operation will be performed. Table 13-1. Software Reset Command Software Reset Byte 1 Byte 2 Byte 3 Byte 4 F0h 00h 00h 00h Figure 13-1. Software Reset CS SI F0h 00h 00h 00h Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 37 14. Operation Mode Summary The commands described previously can be grouped into four different categories to better describe which commands can be executed at what times. Group A commands consist of: 1. Main Memory Page Read 2. Continuous Array Read (SPI) 3. Read Sector Protection Register 4. Read Sector Lockdown Register 5. Read Security Register 6. Buffer 1 (or 2) Read Group B commands consist of: 1. Page Erase 2. Block Erase 3. Sector Erase 4. Chip Erase 5. Main Memory Page to Buffer 1 (or 2) Transfer 6. Main Memory Page to Buffer 1 (or 2) Compare 7. Buffer 1 (or 2) to Main Memory Page Program with Built-In Erase 8. Buffer 1 (or 2) to Main Memory Page Program without Built-In Erase 9. Main Memory Page Program through Buffer 1 (or 2) with Built-In Erase 10. Main Memory Byte/Page Program through Buffer 1 without Built-In Erase 11. Auto Page Rewrite Group C commands consist of: 1. Buffer 1 (or 2) Write 2. Status Register Read 3. Manufacturer and Device ID Read Group D commands consist of: 1. Erase Sector Protection Register 2. Program Sector Protection Register 3. Sector Lockdown 4. Program Security Register 5. Buffer and Page Size Configuration 6. Freeze Sector Lockdown If a Group A command is in progress (not fully completed), then another command in Group A, B, C, or D should not be started. However, during the internally self-timed portion of Group B commands, any command in Group C can be executed. The Group B commands using Buffer 1 should use Group C commands using Buffer 2 and vice versa. Finally, during the internally self-timed portion of a Group D command, only the Status Register Read command should be executed. Most of the commands in Group B can be suspended and resumed, except the Buffer Transfer, Buffer Compare, and Auto Page Rewrite operations. If a Group B command is suspended, all of the Group A commands can be executed. See Table 6-4 to determine which of the Group B, Group C, and Group D commands are allowed. AT45DB161E 8782H–DFLASH–7/2015 38 15. Command Tables Table 15-1. Read Commands Command Opcode Main Memory Page Read D2h Continuous Array Read (Low Power Mode) 01h Continuous Array Read (Low Frequency) 03h Continuous Array Read (High Frequency) 0Bh Continuous Array Read (High Frequency) 1Bh Continuous Array Read (Legacy Command – Not Recommended for New Designs) E8h Buffer 1 Read (Low Frequency) D1h Buffer 2 Read (Low Frequency) D3h Buffer 1 Read (High Frequency) D4h Buffer 2 Read (High Frequency) D6h Table 15-2. Program and Erase Commands Command Opcode Buffer 1 Write 84h Buffer 2 Write 87h Buffer 1 to Main Memory Page Program with Built-In Erase 83h Buffer 2 to Main Memory Page Program with Built-In Erase 86h Buffer 1 to Main Memory Page Program without Built-In Erase 88h Buffer 2 to Main Memory Page Program without Built-In Erase 89h Main Memory Page Program through Buffer 1 with Built-In Erase 82h Main Memory Page Program through Buffer 2 with Built-In Erase 85h Main Memory Byte/Page Program through Buffer 1 without Built-In Erase 02h Page Erase 81h Block Erase 50h Sector Erase 7Ch Chip Erase C7h + 94h + 80h + 9Ah Program/Erase Suspend B0h Program/Erase Resume D0h Read-Modify-Write through Buffer 1 58h Read-Modify-Write through Buffer 2 59h AT45DB161E 8782H–DFLASH–7/2015 39 Table 15-3. Protection and Security Commands Command Opcode Enable Sector Protection 3Dh + 2Ah + 7Fh + A9h Disable Sector Protection 3Dh + 2Ah + 7Fh + 9Ah Erase Sector Protection Register 3Dh + 2Ah + 7Fh + CFh Program Sector Protection Register 3Dh + 2Ah + 7Fh + FCh Read Sector Protection Register Sector Lockdown Read Sector Lockdown Register 32h 3Dh + 2Ah + 7Fh + 30h 35h Freeze Sector Lockdown 34h + 55h + AAh + 40h Program Security Register 9Bh + 00h + 00h + 00h Read Security Register 77h Table 15-4. Additional Commands Command Opcode Main Memory Page to Buffer 1 Transfer 53h Main Memory Page to Buffer 2 Transfer 55h Main Memory Page to Buffer 1 Compare 60h Main Memory Page to Buffer 2 Compare 61h Auto Page Rewrite through Buffer 1 58h Auto Page Rewrite through Buffer 2 59h Deep Power-Down B9h Resume from Deep Power-Down ABh Ultra-Deep Power-Down 79h Status Register Read D7h Manufacturer and Device ID Read 9Fh Configure “Power of 2” (Binary) Page Size 3Dh + 2Ah + 80h + A6h Configure Standard DataFlash Page Size 3Dh + 2Ah + 80h + A7h Software Reset F0h + 00h + 00h + 00h Table 15-5. Legacy Commands(1) Command Opcode Buffer 1 Read 54H Buffer 2 Read 56H Main Memory Page Read 52H Continuous Array Read 68H Status Register Read 57H Note: 1. Legacy commands are not recommended for new designs. AT45DB161E 8782H–DFLASH–7/2015 40 Table 15-6. Detailed Bit-level Addressing Sequence for Binary Page Size (512 bytes) A20 A19 A18 A17 A16 A15 A14 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 Address Byte Reserved Address Byte Reserved Address Byte Reserved Page Size = 512 bytes Additional Dummy Bytes 01h 0 0 0 0 0 0 0 1 X X X A A A A A A A A A A A A A A A A A A A A A N/A 02h 0 0 0 0 0 0 1 0 X X X A A A A A A A A A A A A A A A A A A A A A N/A 03h 0 0 0 0 0 0 1 1 X X X A A A A A A A A A A A A A A A A A A A A A N/A 0Bh 0 0 0 0 1 0 1 1 X X X A A A A A A A A A A A A A A A A A A A A A 1 1Bh 0 0 0 1 1 0 1 1 X X X A A A A A A A A A A A A A A A A A A A A A 2 32h 0 0 1 1 0 0 1 0 X X X X X X X X X X X X X X X X X X X X X X X X N/A 35h 0 0 1 1 0 1 0 1 X X X X X X X X X X X X X X X X X X X X X X X X N/A 50h 0 1 0 1 0 0 0 0 X X X A A A A A A A A A X X X X X X X X X X X X N/A 53h 0 1 0 1 0 0 1 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 55h Opcode Opcode 0 1 0 1 0 1 0 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 58h (1) 0 1 0 1 1 0 0 0 X X X A A A A A A A A A A A A X X X X X X X X X N/A 58h (2) 0 1 0 1 1 0 0 0 X X X A A A A A A A A A A A A A A A A A A A A A N/A 59h (1) 0 1 0 1 1 0 0 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 59h (2) 0 1 0 1 1 0 0 1 X X X A A A A A A A A A A A A A A A A A A A A A N/A 60h 0 1 1 0 0 0 0 0 X X X A A A A A A A A A A A A X X X X X X X X X N/A 61h 0 1 1 0 0 0 0 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 77h 0 1 1 1 0 1 1 1 X X X X X X X X X X X X X X X X X X X X X X X X N/A 79h 0 1 1 1 1 0 0 1 7Ch 0 1 1 1 1 1 0 0 X X X A A A A X X X X X X X X X X X X X X X X X N/A 81h 1 0 0 0 0 0 0 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 82h 1 0 0 0 0 0 1 0 X X X A A A A A A A A A A A A A A A A A A A A A N/A 83h 1 0 0 0 0 0 1 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 84h 1 0 0 0 0 1 0 0 X X X X X X X X X X X X X X X A A A A A A A A A N/A 85h 1 0 0 0 0 1 0 1 X X X A A A A A A A A A A A A A A A A A A A A A N/A 86h 1 0 0 0 0 1 1 0 X X X A A A A A A A A A A A A X X X X X X X X X N/A 87h 1 0 0 0 0 1 1 1 X X X X X X X X X X X X X X X A A A A A A A A A N/A 88h 1 0 0 0 1 0 0 0 X X X A A A A A A A A A A A A X X X X X X X X X N/A 89h 1 0 0 0 1 0 0 1 X X X A A A A A A A A A A A A X X X X X X X X X N/A 9Fh 1 0 0 1 1 1 1 1 N/A N/A N/A N/A B9h 1 0 1 1 1 0 0 1 N/A N/A N/A N/A ABh 1 0 1 0 1 0 1 1 N/A N/A N/A N/A B0h 1 0 1 1 0 0 0 0 N/A N/A N/A N/A D0h 1 1 0 1 0 0 0 0 N/A N/A N/A N/A D1h 1 1 0 1 0 0 0 1 X X X X X X X X X X X X X X X A A A A A A A A A N/A D2h 1 1 0 1 0 0 1 0 X X X A A A A A A A A A A A A A A A A A A A A A 4 D3h 1 1 0 1 0 0 1 1 X X X X X X X X X X X X X X X A A A A A A A A A N/A D4h 1 1 0 1 0 1 0 0 X X X X X X X X X X X X X X X A A A A A A A A A 1 D6h 1 1 0 1 0 1 1 0 X X X X X X X X X X X X X X X A A A A A A A A A 1 D7h 1 1 0 1 0 1 1 1 N/A N/A N/A N/A N/A N/A N/A N/A AT45DB161E 8782H–DFLASH–7/2015 41 1. Shown to indicate when Auto Page Rewrite Operation is executed. 2. Shown to indicate when Read Modify Write Operation is executed. Note: X = Dummy Bit Table 15-7. Detailed Bit-level Addressing Sequence for Standard DataFlash Page Size (528 bytes) PA10 PA9 PA8 PA7 PA6 PA5 PA4 PA3 PA2 PA1 PA0 BA9 BA8 BA7 BA6 BA5 BA4 BA3 BA2 BA1 BA0 Address Byte PA11 Address Byte Reserved Address Byte Reserved Page Size = 528-bytes Additional Dummy Bytes 01h 0 0 0 0 0 0 0 1 X X P P P P P P P P P P P P B B B B B B B B B B N/A 02h 0 0 0 0 0 0 1 0 X X P P P P P P P P P P P P B B B B B B B B B B N/A 03h 0 0 0 0 0 0 1 1 X X P P P P P P P P P P P P B B B B B B B B B B N/A 0Bh 0 0 0 0 1 0 1 1 X X P P P P P P P P P P P P B B B B B B B B B B 1 1Bh 0 0 0 1 1 0 1 1 X X P P P P P P P P P P P P B B B B B B B B B B 2 32h 0 0 1 1 0 0 1 0 X X X X X X X X X X X X X X X X X X X X X X X X N/A 35h 0 0 1 1 0 1 0 1 X X X X X X X X X X X X X X X X X X X X X X X X N/A 50h 0 1 0 1 0 0 0 0 X X P P P P P P P P P X X X X X X X X X X X X X N/A 53h 0 1 0 1 0 0 1 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A Opcode Opcode 55h 0 1 0 1 0 1 0 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A 58h (1) 0 1 0 1 1 0 0 0 X X P P P P P P P P P P P P X X X X X X X X X X N/A 58h (2) 0 1 0 1 1 0 0 0 X X P P P P P P P P P P P P B B B B B B B B B B N/A 59h (1) 0 1 0 1 1 0 0 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A (2) 59h 0 1 0 1 1 0 0 1 X X P P P P P P P P P P P P B B B B B B B B B B N/A 60h 0 1 1 0 0 0 0 0 X X P P P P P P P P P P P P X X X X X X X X X X N/A 61h 0 1 1 0 0 0 0 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A 77h 0 1 1 1 0 1 1 1 X X X X X X X X X X X X X X X X X X X X X X X X N/A 79h 0 1 1 1 1 0 0 1 7Ch 0 1 1 1 1 1 0 0 X X P P N/A P P X X X X X X N/A X X X X X X X X N/A X X X X N/A N/A 81h 1 0 0 0 0 0 0 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A 82h 1 0 0 0 0 0 1 0 X X P P P P P P P P P P P P B B B B B B B B B B N/A 83h 1 0 0 0 0 0 1 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A 84h 1 0 0 0 0 1 0 0 X X X X X X X X X X X X X X B B B B B B B B B B N/A 85h 1 0 0 0 0 1 0 1 X X P P P P P P P P P P P P B B B B B B B B B B N/A 86h 1 0 0 0 0 1 1 0 X X P P P P P P P P P P P P X X X X X X X X X X N/A 87h 1 0 0 0 0 1 1 1 X X X X X X X X X X X X X X B B B B B B B B B B N/A 88h 1 0 0 0 1 0 0 0 X X P P P P P P P P P P P P X X X X X X X X X X N/A 89h 1 0 0 0 1 0 0 1 X X P P P P P P P P P P P P X X X X X X X X X X N/A 9Fh 1 0 0 1 1 1 1 1 N/A N/A N/A N/A B9h 1 0 1 1 1 0 0 1 N/A N/A N/A N/A ABh 1 0 1 0 1 0 1 1 N/A N/A N/A N/A B0h 1 0 1 1 0 0 0 0 N/A N/A N/A N/A D0h 1 1 0 1 0 0 0 0 N/A N/A N/A N/A AT45DB161E 8782H–DFLASH–7/2015 42 PA10 PA9 PA8 PA7 PA6 PA5 PA4 PA3 PA2 PA1 PA0 BA9 BA8 BA7 BA6 BA5 BA4 BA3 BA2 BA1 BA0 Address Byte PA11 Address Byte Reserved Address Byte Reserved Page Size = 528-bytes Additional Dummy Bytes D1h 1 1 0 1 0 0 0 1 X X X X X X X X X X X X X X B B B B B B B B B B N/A D2h 1 1 0 1 0 0 1 0 X X P P P P P P P P P P P P B B B B B B B B B B 4 D3h 1 1 0 1 0 0 0 1 X X X X X X X X X X X X X X B B B B B B B B B B N/A D4h 1 1 0 1 0 1 0 0 X X X X X X X X X X X X X X B B B B B B B B B B 1 D6h 1 1 0 1 0 1 1 0 X X X X X X X X X X X X X X B B B B B B B B B B 1 D7h 1 1 0 1 0 1 1 1 Opcode Opcode N/A 1. Shown to indicate when Auto Page Rewrite Operation is executed. 2. Shown to indicate when Read Modify Write Operation is executed. Note: 16. N/A N/A N/A P = Page Address Bit B = Byte/Buffer Address Bit X = Dummy Bit Power-On/Reset State When power is first applied to the device, or when recovering from a reset condition, the device will default to SPI Mode 3. In addition, the output pin (SO) will be in a high impedance state, and a high-to-low transition on the CS pin will be required to start a valid instruction. The SPI mode (Mode 3 or Mode 0) will be automatically selected on every falling edge of CS by sampling the inactive clock state. 16.1 Initial Power-Up Timing Restrictions As the device initializes, there will be a transient current demand. The system needs to be capable of providing this current to ensure correct initialization. During power-up, the device must not be accessed for at least the minimum tVCSL time after the supply voltage reaches the minimum VCC level. While the device is being powered-up, the internal PowerOn Reset (POR) circuitry keeps the device in a reset mode until the supply voltage rises above the maximum POR threshold value (VPOR). During this time, all operations are disabled and the device will not respond to any commands. After power-up, the device will be in the standby mode. If the first operation to the device after power-up will be a program or erase operation, then the operation cannot be started until the supply voltage reaches the minimum VCC level and an internal device delay has elapsed. This delay will be a maximum time of tPUW. Table 16-1. Power-Up Timing Symbol Parameter tVCSL Minimum VCC to Chip Select Low Time tPUW Power-Up Device Delay Before Program or Erase Allowed VPOR Power-On Reset (POR) Voltage Min Max 70 1.5 Units µs 3 ms 2.2 V AT45DB161E 8782H–DFLASH–7/2015 43 Figure 16-1. Power-Up Timing VCC Read Operation Permitted VCC (min) tVCSL VPOR (max) VPOR (min) Do Not Attempt Device Access During this Time tPUW Program/Erase Operations Permitted Time AT45DB161E 8782H–DFLASH–7/2015 44 17. System Considerations The serial interface is controlled by the Serial Clock (SCK), Serial Input (SI), and Chip Select (CS) pins. These signals must rise and fall monotonically and be free from noise. Excessive noise or ringing on these pins can be misinterpreted as multiple edges and cause improper operation of the device. PCB traces must be kept to a minimum distance or appropriately terminated to ensure proper operation. If necessary, decoupling capacitors can be added on these pins to provide filtering against noise glitches. As system complexity continues to increase, voltage regulation is becoming more important. A key element of any voltage regulation scheme is its current sourcing capability. Like all Flash memories, the peak current for DataFlash devices occurs during the programming and erasing operations. The supply voltage regulator needs to be able to supply this peak current requirement. An under specified regulator can cause current starvation. Besides increasing system noise, current starvation during programming or erasing can lead to improper operation and possible data corruption. AT45DB161E 8782H–DFLASH–7/2015 45 18. Electrical Specifications 18.1 Absolute Maximum Ratings* Temperature under Bias . . . . . . . -55°C to +125°C Storage Temperature. . . . . . . . . . -65°C to +150°C All Input Voltages (except VCC but including NC pins) with Respect to Ground . . . . . . -0.6V to VCC + 0.6V All Output Voltages with Respect to Ground . . . . . . -0.6V to VCC + 0.6V 18.2 *Notice: Stresses beyond those listed under “Absolute Maximum Ratings” may cause permanent damage to the device. The “Absolute Maximum Ratings” are stress ratings only and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of this specification is not implied. Exposure to absolute maximum rating conditions for extended periods may affect device reliability. Voltage extremes referenced in the “Absolute Maximum Ratings” are intended to accommodate short duration undershoot/overshoot conditions and does not imply or guarantee functional device operation at these levels for any extended period of time. DC and AC Operating Range Operating Temperature (Case) VCC Power Supply Industrial AT45DB161E 2.3V Version AT45DB161E 2.5V Version -40C to 85C -40C to 85C 2.3V to 3.6V 2.5V to 3.6V AT45DB161E 8782H–DFLASH–7/2015 46 18.3 DC Characteristics Symbol Parameter Condition IUDPD Ultra-Deep Power-Down Current CS= VCC. All other inputs at 0V or VCC IDPD Deep Power-Down Current ISB Typ Max Units 0.4 1 µA CS= VCC. All other inputs = VIH or VIL 5 12 µA Standby Current CS= VCC. All other inputs = VIH or VIL 25 50 µA Active Current, Low Power Read (01h) Operation f = 1MHz; IOUT = 0mA; VCC = 3.6V 6 9 mA ICC1 f = 15MHz; IOUT = 0mA; VCC = 3.6V 7 11 mA ICC2(1)(2) Active Current, Read Operation f = 50MHz; IOUT = 0mA; VCC = 3.6V 12 17 mA f = 85MHz; IOUT = 0mA; VCC = 3.6V 16 22 mA ICC3 Active Current, Program Operation CS=VCC 12 18 mA ICC4 Active Current, Erase Operation CS=VCC 12 18 mA ILI Input Load Current All inputs at CMOS levels 1 µA ILO Output Leakage Current All inputs at CMOS levels 1 µA VIL Input Low Voltage VCC x 0.3 V VIH Input High Voltage VCC + 0.6 V VOL Output Low Voltage IOL = 100µA 0.4 V VOH Output High Voltage IOH = -100µA Notes: 1. 2. Min VCC x 0.7 VCC 0.2V V Typical values measured at 3.0V at 25C. ICC2 during a Buffer Read is 20mA maximum @ 20MHz. AT45DB161E 8782H–DFLASH–7/2015 47 18.4 AC Characteristics Symbol Parameter fSCK SCK Frequency fCAR1 AT45DB161E 2.3V Version AT45DB161E 2.5V Version Min Min Max Max Units 70 70 MHz SCK Frequency for Continuous Read (0x0B) 85 85 MHz fCAR2 SCK Frequency for Continuous Read (0x03) (Low Frequency) 50 50 MHz fCAR3 SCK Frequency for Continuous Read (Low Power Mode – 01h Opcode) 15 15 MHz fCAR4 SCK Frequency for Continuous Read (0x1B) 104 104 MHz tWH SCK High Time 4 4 ns tWL SCK Low Time 4 4 ns tSCKR(1) SCK Rise Time, Peak-to-peak 0.1 0.1 V/ns tSCKF(1) SCK Fall Time, Peak-to-peak 0.1 0.1 V/ns tCS Minimum CS High Time 20 20 ns tCSS CS Setup Time 5 5 ns tCSH CS Hold Time 5 5 ns tSU Data In Setup Time 2 2 ns tH Data In Hold Time 1 1 ns tHO Output Hold Time 0 0 ns tDIS Output Disable Time 6 6 ns tV Output Valid 7 7 ns tWPE WP Low to Protection Enabled 1 1 µs tWPD WP High to Protection Disabled 1 1 µs tLOCK Freeze Sector Lockdown Time (from CS High) 100 100 µs tEUDPD CS High to Ultra-Deep Power-Down 4 4 µs tCSLU Minimum CS Low Time to Exit Ultra-Deep Power-Down tXUDPD Exit Ultra-Deep Power-Down Time tEDPD 20 20 ns 180 180 µs CS High to Deep Power-Down 2 2 µs tRDPD Resume from Deep Power-Down Time 35 35 µs tXFR Page to Buffer Transfer Time 200 200 µs tCOMP Page to Buffer Compare Time 200 200 µs tRST RESET Pulse Width tREC RESET Recovery Time 1 1 µs tSWRST Software Reset Time 35 35 µs 10 10 µs AT45DB161E 8782H–DFLASH–7/2015 48 Note: 18.5 1. Program and Erase Characteristics Symbol Parameter Typ Max Units tEP Page Erase and Programming Time (512/528 bytes) 17 25* ms tP Page Programming Time 3 4 ms tBP Byte Programming Time 8 tPE Page Erase Time 12 35 ms tBE Block Erase Time 45 100 ms tSE Sector Erase Time 1.4 2* s tCE Chip Erase Time 22 40 s Program 10 15 tSUSP Suspend Time Erase 20 30 Program 10 15 tRES Resume Time Erase 20 30 tOTPP OTP Security Register Program Time 200 500 Notes: 1. 19. Values are based on device characterization, not 100% tested in production. Min µs µs µs µs Values are based on device characterization, not 100% tested in production. 2. Not 100% tested (value guaranteed by design and characterization). 3. *Specification waiver for legacy inventory may apply. Input Test Waveforms and Measurement Levels AC Driving Levels 0.9VCC VCC/2 0.1VCC AC Measurement Level tR, tF < 2ns (10% to 90%) 20. Output Test Load Device Under Test 30pF AT45DB161E 8782H–DFLASH–7/2015 49 21. Utilizing the RapidS Function To take advantage of the RapidS function's ability to operate at higher clock frequencies, a full clock cycle must be used to transmit data back and forth across the serial bus. The DataFlash is designed to always clock its data out on the falling edge of the SCK signal and clock data in on the rising edge of SCK. For full clock cycle operation to be achieved, when the DataFlash is clocking data out on the falling edge of SCK, the host controller should wait until the next falling edge of SCK to latch the data in. Similarly, the host controller should clock its data out on the rising edge of SCK in order to give the DataFlash a full clock cycle to latch the incoming data in on the next rising edge of SCK. Figure 21-1. RapidS Mode Slave CS 1 8 2 3 4 5 6 1 8 7 2 3 4 5 6 1 7 SCK B A MOSI E C D MSB LSB BYTE-MOSI H G I F MISO MSB LSB BYTE-SO MOSI = Master Out, Slave In MISO = Master In, Slave Out The Master is the host controller and the Slave is the DataFlash. The Master always clocks data out on the rising edge of SCK and always clocks data in on the falling edge of SCK. The Slave always clocks data out on the falling edge of SCK and always clocks data in on the rising edge of SCK. A. B. C. D. E. F. G. H. I. Master clocks out first bit of BYTE-MOSI on the rising edge of SCK Slave clocks in first bit of BYTE-MOSI on the next rising edge of SCK Master clocks out second bit of BYTE-MOSI on the same rising edge of SCK Last bit of BYTE-MOSI is clocked out from the Master Last bit of BYTE-MOSI is clocked into the slave Slave clocks out first bit of BYTE-SO Master clocks in first bit of BYTE-SO Slave clocks out second bit of BYTE-SO Master clocks in last bit of BYTE-SO AT45DB161E 8782H–DFLASH–7/2015 50 Figure 21-2. Command Sequence for Read/Write Operations for Page Size 512 bytes (Except Status Register Read, Manufacturer and Device ID Read) SI (INPUT) MSB CMD XXX 8-bits XXXX 3 Dummy Bits 8-bits 8-bits XXXXXXXXX Page Address (A20 - A9) XXXX XXXX LSB Byte/Buffer Address (A8 - A0/BFA8 - BFA0) Figure 21-3. Command Sequence for Read/Write Operations for Page Size 528 bytes (Except Status Register Read, Manufacturer and Device ID Read) SI (INPUT) MSB CMD 8-bits 8-bits 8-bits XX XX XXXX XXXX XXXX 2 Page Address Dummy Bits (PA11 - PA0) XXXX XXXX LSB Byte/Buffer Address (BA9 - BA0/BFA9 - BFA0) AT45DB161E 8782H–DFLASH–7/2015 51 22. AC Waveforms Four different timing waveforms are shown in Figure 22-1 through Figure 22-4. Waveform 1 shows the SCK signal being low when CS makes a high-to-low transition and Waveform 2 shows the SCK signal being high when CS makes a high-to-low transition. In both cases, output SO becomes valid while the SCK signal is still low (SCK low time is specified as tWL). Timing Waveforms 1 and 2 conform to RapidS serial interface but for frequencies up to 85MHz. Waveforms 1 and 2 are compatible with SPI Mode 0 and SPI Mode 3, respectively. Waveform 3 and 4 illustrate general timing diagram for RapidS serial interface. These are similar to Waveform 1 and 2, except that output SO is not restricted to become valid during the tWL period. These timing waveforms are valid over the full frequency range (maximum frequency = 85MHz) of the RapidS serial case. Figure 22-1. Waveform 1 = SPI Mode 0 Compatible tCS CS tWH tCSS tWL tCSH SCK tHO tV SO High-impedance Valid Out tSU SI tDIS High-impedance tH Valid In Figure 22-2. Waveform 2 = SPI Mode 3 Compatible tCS CS tCSS tWL tWH tCSH SCK tV SO High Z tHO Valid Out tSU SI tDIS High-impedance tH Valid In AT45DB161E 8782H–DFLASH–7/2015 52 Figure 22-3. Waveform 3 = RapidS Mode 0 tCS CS tWH tCSS tWL tCSH SCK tHO tV SO High-impedance Valid Out tSU SI tDIS High-impedance tH Valid In Figure 22-4. Waveform 4 = RapidS Mode 3 tCS CS tCSS tWL tWH tCSH SCK tV SO tHO High Z Valid Out tSU SI tDIS High-impedance tH Valid In AT45DB161E 8782H–DFLASH–7/2015 53 23. Write Operations The following block diagram and waveforms illustrate the various write sequences available. Figure 23-1. Block Diagram Flash Memory Array Page (512/528 bytes) Buffer 1 To Main Memory Page Program Buffer 2 To Main Memory Page Program Buffer 1 (512/528 bytes) Buffer 2 (512/528 bytes) Buffer 2 Write Buffer 1 Write I/O Interface SI Figure 23-2. Buffer Write Completes Writing into Selected Buffer CS Binary Page Size 15 Dummy Bits + BFA8-BFA0 SI (Input) CMD X X···X, BFA9-8 BFA7-0 n n+1 Last Byte Figure 23-3. Buffer to Main Memory Page Program Starts Self-timed Erase/Program Operation CS Binary Page Size A20-A9 + 9 Dummy Bits SI (Input) CMD PA11-6 Each transition represents eight bits PA5-0, XX XXXX XX n = 1st byte read n+1 = 2nd byte read AT45DB161E 8782H–DFLASH–7/2015 54 24. Read Operations The following block diagram and waveforms illustrate the various read sequences available. Figure 24-1. Block Diagram Flash Memory Array Page (512/528 bytes) Main Memory Page To Buffer 2 Main Memory Page To Buffer 1 Buffer 1 (512/528 bytes) Buffer 2 (512/528 bytes) Buffer 1 Read Main Memory Page Read Buffer 2 Read I/O Interface SO Figure 24-2. Main Memory Page Read CS Address for Binary Page Size SI (Input) CMD A20-A16 A15-A8 A7-A0 PA11-6 PA5-0, BA9-8 BA7-0 X X 4 Dummy Bytes SO (Output) n n+1 AT45DB161E 8782H–DFLASH–7/2015 55 Figure 24-3. Main Memory Page to Buffer Transfer Data From the selected Flash Page is read into either SRAM Buffer Starts Reading Page Data into Buffer CS Binary Page Size A20-A9 + 9 Dummy Bits SI (Input) CMD PA11-6 PA5-0, XX XXXX XX SO (Output) Figure 24-4. Buffer Read CS Address for Binary Page Size SI (Input) CMD A20-A16 A15-A8 A7-A0 X X... X, BFA9-8 BFA7-0 X No Dummy Byte (opcodes D1H and D3H) 1 Dummy Byte (opcodes D4H and D6H) SO (Output) n n+1 Each transition represents eight bits AT45DB161E 8782H–DFLASH–7/2015 56 25. Detailed Bit-level Read Waveforms: RapidS Mode 0/Mode 3 Figure 25-1. Continuous Array Read (Legacy Opcode E8h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 62 63 64 65 66 67 68 69 70 71 72 SCK Opcode SI 1 1 1 0 Address Bits 1 0 0 A 0 MSB A A A A A 32 Dummy Bits A A A X MSB X X X X X MSB Data Byte 1 SO High-impedance D D D D D D D D MSB D D MSB Bit 0 of Page n+1 Bit 4095/4223 of Page n Figure 25-2. Continuous Array Read (Opcode 0Bh) CS 0 1 2 3 4 5 6 7 8 9 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 10 11 12 SCK Opcode SI 0 0 0 0 1 Address Bits A20 - A0 0 1 A 1 MSB A A A A A Dummy Bits A A A MSB X X X X X X X X MSB Data Byte 1 SO High-impedance D D D MSB D D D D D D D MSB Figure 25-3. Continuous Array Read (Opcode 01h or 03h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 SCK Opcode SI 0 0 0 0 0 MSB Address Bits A20-A0 0 1 1 A A A A A A A A A MSB Data Byte 1 SO High-impedance D MSB D D D D D D D D D MSB AT45DB161E 8782H–DFLASH–7/2015 57 Figure 25-4. Main Memory Page Read (Opcode D2h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 62 63 64 65 66 67 68 69 70 71 72 SCK Opcode SI 1 1 0 1 0 Address Bits 0 1 A 0 MSB A A A A A 32 Dummy Bits A A A MSB X X X X X X MSB Data Byte 1 SO High-impedance D D D D D D D D MSB D D MSB Figure 25-5. Buffer Read (Opcode D4h or D6h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 SCK Address Bits Binary Page Size = 15 Dummy Bits + BFA8-BFA0 Standard DataFlash Page Size = 14 Dummy Bits + BFA9-BFA0 Opcode SI 1 1 0 1 0 1 0 0 X MSB X X X X X A A A MSB Dummy Bits X X X X X X X X MSB Data Byte 1 SO High-impedance D D MSB D D D D D D D D MSB Figure 25-6. Buffer Read – Low Frequency (Opcode D1h or D3h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 SCK Address Bits Binary Page Size = 15 Dummy Bits + BFA8-BFA0 Standard DataFlash Page Size = 14 Dummy Bits + BA9-BFA0 Opcode SI 1 1 0 1 0 MSB 0 0 1 X X X X X X A A A MSB Data Byte 1 SO High-impedance D MSB D D D D D D D D D MSB AT45DB161E 8782H–DFLASH–7/2015 58 Figure 25-7. Read Sector Protection Register (Opcode 32h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 SCK Opcode SI 0 0 1 1 0 Dummy Bits 0 1 X 0 MSB X X X X X X X X MSB Data Byte 1 SO High-impedance D D D D D D D D MSB D MSB Figure 25-8. Read Sector Lockdown Register (Opcode 35h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 SCK Opcode SI 0 0 1 1 0 Dummy Bits 1 0 X 1 MSB X X X X X X X X MSB Data Byte 1 SO High-impedance D D D D D D D D MSB D MSB Figure 25-9. Read Security Register (Opcode 77h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 29 30 31 32 33 34 35 36 37 38 39 40 SCK Opcode SI 0 1 1 1 0 MSB Dummy Bits 1 1 1 X X X X X X X X X MSB Data Byte 1 SO High-impedance D MSB D D D D D D D D MSB AT45DB161E 8782H–DFLASH–7/2015 59 Figure 25-10. Status Register Read (Opcode D7h) CS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 SCK Opcode SI 1 1 0 1 0 1 1 1 MSB Status Register Data High-impedance SO D D D D D D D Status Register Data D MSB D D D D D D D D MSB D D MSB Figure 25-11. Manufacturer and Device Read (Opcode 9Fh) CS 0 6 7 8 14 15 16 22 23 24 30 31 32 38 39 40 46 SCK Opcode SI 9Fh High-impedance SO Note: Each transition 1Fh 26h 00h 01h 00h Manufacturer ID Device ID Byte 1 Device ID Byte 2 EDI String Length EDI Data Byte 1 shown for SI and SO represents one byte (8 bits) Figure 25-12.Reset Timing CS tREC tCSS SCK tRST RESET SO (Output) High Impedance High Impedance SI (Input) Note: 1. The CS signal should be in the high state before the RESET signal is deasserted. AT45DB161E 8782H–DFLASH–7/2015 60 26. Auto Page Rewrite Flowchart Figure 26-1. Algorithm for Programming or Re-programming of the Entire Array Sequentially START Provide Address and Data Buffer Write (84h, 87h) Main Memory Page Program through Buffer (82h, 85h) Buffer To Main Memory Page Program (83h, 86h) END Notes: 1. This type of algorithm is used for applications in which the entire array is programmed sequentially, filling the array page-by-page 2. A page can be written using either a Main Memory Page Program operation or a buffer write operation followed by a buffer to Main Memory Page Program operation 3. The algorithm above shows the programming of a single page. The algorithm will be repeated sequentially for each page within the entire array AT45DB161E 8782H–DFLASH–7/2015 61 Figure 26-2. Algorithm for Programming or Re-programming of the Entire Array Randomly START Provide Address of Page to Modify Main Memory Page to Buffer Transfer (53h, 55h) If planning to modify multiple bytes currently stored within a page of the Flash array Buffer Write (84h, 87h) Main Memory Page Program through Buffer (82h, 85h) Buffer to Main Memory Page Program (83h, 86h) Auto Page Rewrite (58h, 59h) (2) Increment Page (2) Address Pointer END Notes: 1. To preserve data integrity, each page of an DataFlash sector must be updated/rewritten at least once within every 50,000 cumulative page erase and program operations 2. A page address pointer must be maintained to indicate which page is to be rewritten. The auto page rewrite command must use the address specified by the page address pointer 3. Other algorithms can be used to rewrite portions of the Flash array. Low-power applications may choose to wait until 50,000 cumulative page erase and program operations have accumulated before rewriting all pages of the sector. AT45DB161E 8782H–DFLASH–7/2015 62 27. Ordering Information 27.1 Ordering Detail AT 4 5 D B 1 6 1 E - S S H D 2 B - B Designator Product Family Shipping Carrier Option B = Bulk (tubes) T = Tape and reel Y = Trays 45DB = DataFlash Page Size Option Device Density “ ” = Standard (528 bytes/page) 2B = Binary (512 bytes/page) 16 = 16-Mbit Interface 1 = Serial Device Revision Operating Voltage D = 2.5V minimum (2.5V to 3.6V) F = 2.3V minimum (2.3V to 3.6V) Device Grade H = Green, NiPdAu lead finish, Industrial temperature range (–40°C to +85°C) U = Green, Matte Sn or Sn alloy, Industrial temperature range (–40°C to +85°C) Package Option SS = 8-lead, 0.150” wide SOIC S = 8-lead, 0.208” wide SOIC M = 8-pad, 5 x 6 x 0.6mm UDFN CC = 9-ball, 3 x 3 (1mm pitch) UBGA DWF = Die in Wafer Form AT45DB161E 8782H–DFLASH–7/2015 63 27.2 Ordering Codes (Standard Page Size) Ordering Code Package Lead Finish Operating Voltage fSCK 2.5V to 3.6V 85MHz Device Grade AT45DB161E-SSHD-B (1)(3) AT45DB161E-SSHD-T(1)(3) 8S1 AT45DB161E-SHD-B(1)(2)(3) AT45DB161E-SHD-T(1)(2)(3) 8S2 NiPdAu Industrial (-40C to 85C) AT45DB161E-MHD-Y(1)(3) AT45DB161E-MHD-T(1)(3) AT45DB161E-CCUD-T(1)(3) 8MA1 9CC1 SnAgCu AT45DB161E-SSHF-B(1) AT45DB161E-SSHF-T(1) 8S1 AT45DB161E-SHF-B(1)(2) AT45DB161E-SHF-T(1)(2) 8S2 NiPdAu 2.3V to 3.6V AT45DB161E-MHF-Y(1) AT45DB161E-MHF-T(1) AT45DB161E-CCUF-T(1) AT45DB161E-DWF Notes: 1. (4) Industrial 85MHz (-40C to 85C) 8MA1 9CC1 SnAgCu DWF The shipping carrier suffix is not marked on the device. 2. Not recommended for new design. Use the 8S1 package option. 3. Not recommended for new design. Use the F (2.3V to 3.6V) voltage option. 4. Contact Adesto for mechanical drawing or Die Sales information. Package Type 8S1 8-lead 0.150" wide, Plastic Gull Wing Small Outline (JEDEC SOIC) 8S2 8-lead 0.208" wide, Plastic Gull Wing Small Outline (EIAJ SOIC) 8MA1 8-pad (5 x 6 x 0.6mm body), Thermally Enhanced Plastic Ultra Thin Dual Flat No-lead (UDFN) 9CC1 9-ball (6 x 6 x 0.6mm body) 3 x 3 array x 1mm pitch, Ultra-thin Ball Grid Array (UBGA) DWF Die in Wafer Form AT45DB161E 8782H–DFLASH–7/2015 64 27.3 Ordering Codes (Binary Page Size) Ordering Code Package AT45DB161E-SSHD2B-T(1)(3)(4) 8S1 AT45DB161E-SHD2B-T(1)(2)(3)(4) 8S2 AT45DB161E-MHD2B-T (1)(3)(4) 8MA1 AT45DB161E-SSHF2B-T(1)(3) 8S1 AT45DB161E-SHF2B-T(1)(2)(3) 8S2 AT45DB161E-MHF2B-T(1)(3) Notes: 1. Lead Finish Operating Voltage fSCK Device Grade NiPdAu 2.5V to 3.6V 85MHz NiPdAu 2.3V to 3.6V 85MHz Industrial (-40C to 85C) Industrial (-40C to 85C) 8MA1 The shipping carrier suffix is not marked on the device. 2. Not recommended for new design. Use the 8S1 package option. 3. Parts ordered with suffix code ‘2B’ are shipped in tape and reel (T&R) with the page size set to 512 bytes. This option is only available for shipping in T&R (-T). 4. Not recommended for new design. Use the F (2.3V-3.6V) voltage option. Package Type 8S1 8-lead 0.150" wide, Plastic Gull Wing Small Outline (JEDEC SOIC) 8S2 8-lead 0.208" wide, Plastic Gull Wing Small Outline (EIAJ SOIC) 8MA1 8-pad (5 x 6 x 0.6mm body), Thermally Enhanced Plastic Ultra Thin Dual Flat No-lead (UDFN) AT45DB161E 8782H–DFLASH–7/2015 65 27.4 Ordering Codes (Reserved) Ordering Code Package AT45DB161E-SSHFHA-T(1)(2) 8S1 AT45DB161E-SHFHA-T(1)(2) 8S2 AT45DB161E-SSHFHC-T (1)(3) AT45DB161E-SHFHC-T(1)(3) Notes: 1. Lead Finish Operating Voltage fSCK NiPdAu 2.3V to 3.6V 85MHz 8S1 Device Grade Industrial (-40C to 85C) 8S2 The shipping carrier suffix is not marked on the device. 2. Parts ordered with suffix code ‘HA’ are shipped in tape and reel (T&R) only with the page size set to 528 bytes. 3. Parts ordered with suffix code ‘HC’ are shipped in tape and reel (T&R) only with the page size set to 512 bytes. 4. Please contact Adesto for a description of these ‘Reserved’ codes. Package Type 8S1 8-lead 0.150" wide, Plastic Gull Wing Small Outline (JEDEC SOIC) 8S2 8-lead 0.208" wide, Plastic Gull Wing Small Outline (EIAJ SOIC) AT45DB161E 8782H–DFLASH–7/2015 66 28. Packaging Information 28.1 8S1 – 8-lead JEDEC SOIC C 1 E E1 L N Ø TOP VIEW END VIEW e b COMMON DIMENSIONS (Unit of Measure = mm) A A1 D SIDE VIEW Notes: This drawing is for general information only. Refer to JEDEC Drawing MS-012, Variation AA for proper dimensions, tolerances, datums, etc. SYMBOL MIN A 1.35 NOM MAX – 1.75 A1 0.10 – 0.25 b 0.31 – 0.51 C 0.17 – 0.25 D 4.80 – 5.05 E1 3.81 – 3.99 E 5.79 – 6.20 e NOTE 1.27 BSC L 0.40 – 1.27 Ø 0° – 8° 6/22/11 Package Drawing Contact: contact@adestotech.com TITLE 8S1, 8-lead (0.150” Wide Body), Plastic Gull Wing Small Outline (JEDEC SOIC) GPC SWB DRAWING NO. REV. 8S1 G AT45DB161E 8782H–DFLASH–7/2015 67 28.2 8S2 – 8-lead EIAJ SOIC C 1 E E1 L N q TOP VIEW END VIEW e b COMMON DIMENSIONS (Unit of Measure = mm) A SYMBOL A1 D SIDE VIEW MAX NOM NOTE 1.70 2.16 A1 0.05 0.25 b 0.35 0.48 4 C 0.15 0.35 4 D 5.13 5.35 E1 5.18 5.40 E 7.70 8.26 L 0.51 0.85 q 0° 8° e Notes: 1. 2. 3. 4. MIN A 1.27 BSC 2 3 This drawing is for general information only; refer to EIAJ Drawing EDR-7320 for additional information. Mismatch of the upper and lower dies and resin burrs aren't included. Determines the true geometric position. Values b,C apply to plated terminal. The standard thickness of the plating layer shall measure between 0.007 to .021 mm. Package Drawing Contact: contact@adestotech.com TITLE 8S2, 8-lead, 0.208” Body, Plastic Small Outline Package (EIAJ) GPC STN 4/15/08 DRAWING NO. REV. 8S2 AT45DB161E 8782H–DFLASH–7/2015 F 68 28.3 8MA1 – 8-pad UDFN E C Pin 1 ID SIDE VIEW D y TOP VIEW A1 A K E2 0.45 8 Option A Pin #1 Chamfer (C 0.35) 1 Pin #1 Notch (0.20 R) (Option B) 7 2 e D2 6 3 COMMON DIMENSIONS (Unit of Measure = mm) SYMBOL MIN NOM MAX A 0.45 0.55 0.60 A1 0.00 0.02 0.05 b 0.35 0.40 0.48 C 5 4 b L BOTTOM VIEW NOTE 0.152 REF D 4.90 5.00 D2 3.80 4.00 4.20 E 5.90 6.00 6.10 E2 3.20 3.40 3.60 e 5.10 1.27 L 0.50 0.60 0.75 y 0.00 – 0.08 K 0.20 – – 4/15/08 TITLE Package Drawing Contact: contact@adestotech.com 8MA1, 8-pad (5 x 6 x 0.6 mm Body), Thermally Enhanced Plastic Ultra Thin Dual Flat No Lead Package (UDFN) GPC YFG DRAWING NO. 8MA1 AT45DB161E 8782H–DFLASH–7/2015 REV. D 69 28.4 9CC1 – 9-ball UBGA Top view d 0.10 (4X) Side View view "A" (rotated 90°CW) E A f 0.10 C d 0.10 C seating plane C Pin#1 ID A A A1 A section A-A See view "A" D B C 1 2 3 B E1 b A1 A A2 Ø0.40±0.05 Ø0.30 ORIGINAL/RAW BALL 9-Øb j n 0.15 m C A B j n 0.05 m C C COMMON DIMENSIONS (Unit of Measure = mm) D1 B SYMBOL MIN NOM MAX A – 0.53 0.60 A1 0.12 – - A e A2 A1 ball corner 1 2 3 D e Bottom View 0.38 REF 5.90 D1 E e 6.00 6.10 2.00 BSC 5.90 E1 b NOTE 6.00 6.10 2.00 BSC 0.35 0.40 0.45 Note 1 1.00 BSC Notes: 1. Dimension “b” is measured at the maximum ball diameter, in a plane parallel to the seating plane. 6/30/09 Package Drawing Contact: contact@adestotech.com TITLE GPC DRAWING NO. REV. 9CC1, 9-ball, 6 x 6 x 0.6mm Body, 1.0mm ball pitch (3x3 Array), Ultra-thin Ball Grid Array Package(UBGA) CAA 9CC1 A AT45DB161E 8782H–DFLASH–7/2015 70 29. Revision History Doc. Rev. Date Comments 8782H 7/2015 Added Die in Wafer Form package option. Added explanation of Read-Modify-Write command (Section 6.6). Updated Table 6-4 (Main Memory to Buffer Compare). Added information on Power Up (Section 16.1). Added footnotes to Tables 15-6 and 15-7. Updated Tables 12-1 and 12-3. Updated condition description for IUDPD, IDPD, and ISB. 8782G 10/2013 Updated spec in Continuous Array Read (1Bh Opcode) to fCAR4. Corrected Low Power Read Option (up to 15MHz). Corrected Ultra-Deep Power-Down current (400nA typical). Updated spec for Input High Voltage (Max) to VCC + 0.6V. 8782F 7/2013 Updated Auto Page Rewrite cycle to 50,000 cumulative page erase/program operations. Added reserved part order codes.Updated DC conditions for VOL, ICC3 and ICC4. F voltage option (2.3V - 3.6V) recommended for new designs. 8782E 6/2013 8782D 11/2012 Updated electrical and power specifications. Additional 2.3V package options. “Buffer 1 (or 2) Read” moved from Group C to Group A in Operation Mode Summary. Added Legacy Commands table. Updated to Adesto logos. Updated preliminary to complete datasheet status. 8782C 07/2012 Corrected pinout drawings to state top view. Increased tXUDPD maximum from 70µs to 120µs. Updated ordering detail to add 2B equals factory set 512 byte binary page size option. AT45DB161E 8782H–DFLASH–7/2015 71 Doc. Rev. Date Comments Update “Enable Sector Protection”, “Disable Sector Protection”, “Erase Sector Protection Register”, “Program Sector Protection Register”, and “Read Sector Lockdown Register” figures. Correct descriptions for PAGE SIZE, bit 0 in “Status Register Format – Byte 1” table. Insert 1Bh opcode in “Detailed Bit-level Addressing Sequence for Binary Page Size (512 bytes)” and “Detailed Bit-level Addressing Sequence for Standard DataFlash Page Size (528 bytes)” tables. DC Characterisitcs:  Add ICC1 condition of f = 20MHz; IOUT = 0mA; VCC = 3.6V with typical 7.5mA and maximum 10mA.  Add ICC4 – Active Current, Erase Operation, VCC = 3.6V, typical 14mA and maximum 20mA.  Update IZP to IUDPD – decrease typical from 0.5µA to 0.4µA and maximum from 2µA to 1µA.  Update IDP to IDPD and ISP to ISB.  Update ICC0 to ICC1 – decrease typical 7mA to 6.5mA.  Update ICC1 to ICC2 – 33MHZ, increase maximum from 17mA to 19mA; 50MHz, decrease maximum from 20mA to 19mA; and at 85MHz, increase typical 14mA to 16mA and maximum 23mA to 26mA.  Update ICC2 to ICC3 – remove erase operation, decrease typical from 15mA to 12mA and maximum from 20mA to 18mA. AC Characterisitics: 8782B 06/2012  Remove typical columns, tSECP, and tSECUP.  fCAR3 – increase 2.3V/2.5V maximum 10MHz to 20MHz.  tWH – decrease 2.3V minimum from 6.8ns to 6.4ns and 2.5V minimum from 6.8ns to 5.2ns.  tWL – decrease 2.3V minimum from 6.8ns to 6.4ns and 2.5V minimum from 6.8ns to 5.2ns.  tCS – decrease 2.3V/2.5V minimum from 50ns to 30ns.  tH – decrease 2.3V/2.5V minimum from 3ns to 1ns.  tDIS – decrease 2.3V maximum from 35ns to 7ns and 2.5V from 35ns to 6ns.  tV – decrease 2.3V maximum from 8ns to 7ns.  tCOMP – decrease 2.3V/2.5V maximum from 250µs to 220µs. Program and Erase Characteristics:  Remove 2.3V minimum, typical, and maximum columns.  tEP – decrease typical from 17ms to 15ms and maximum from 50ms to 40ms.  tPE – decrease typical from 15ms to 12ms and maximum from 50ms to 35ms.  tSE – decrease typical from 1.6s to 1.4s and maximum from 5s to 3.5s.  tCE – decrease typical from 25s to 22s and maximum from 60s to 40s. Update ordering code detail. Replace package option from 9C1-CBGA to 9CC1-UBGA. Various topographical edits throughout document. Update template. 8782A 03/2012 Initial document release. AT45DB161E 8782H–DFLASH–7/2015 72 Corporate Office California | USA Adesto Headquarters 1250 Borregas Avenue Sunnyvale, CA 94089 Phone: (+1) 408.400.0578 Email: contact@adestotech.com © 2015 Adesto Technologies. All rights reserved. / Rev.: 8782H–DFLASH–7/2015 Adesto®, the Adesto logo, CBRAM®, and DataFlash® are registered trademarks or trademarks of Adesto Technologies. All other marks are the property of their respective owners. Disclaimer: Adesto Technologies Corporation makes no warranty for the use of its products, other than those expressly contained in the Company's standard warranty which is detailed in Adesto's Terms and Conditions located on the Company's web site. The Company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and does not make any commitment to update the information contained herein. No licenses to patents or other intellectual property of Adesto are granted by the Company in connection with the sale of Adesto products, expressly or by implication. Adesto's products are not authorized for use as critical components in life support devices or systems.