Check out my first novel, midnight's simulacra!

Winbond

From dankwiki
Revision as of 04:44, 29 March 2019 by Dank (talk | contribs) (→‎Registers)

Winbond of Taiwan manufactures semiconductor devices, including flash storage.

W25N01GVxxIG/IT

A 1Gb (128MB) Quad-SPI SLC NAND chip of 1K 128KB blocks (each made up of 64 ECC-protected 2KB pages), capable of up to 104MHz Quad-SPI. Each page, in addition to the 2048 usable bytes, contains a 64-byte "Spare Area". Writes load 2,112 bytes. When on-device ECC is enabled, the majority of the Spare Area is used for ECC and bad block marking, though 2 unprotected and 4 ECC-protected bits are available to the user in each of 4 16-byte lines. When on-device ECC is disabled, the 64 bytes of the Spare Area are available to the user. The serial NAND employs 32-bit addresses: the four MSB are unused, 10 bits select the block, 6 bits select the page, and the 12 LSB specify the byte.

The xx refers to the package code. The IT part sets the BUF mode selector to 0 on initialization. The IG part sets BUF to 1. Both allow the mode to be configured by writing to the BUF bit of the Configuration Register.

Packages

  • 8-pad WSON 8x6mm (package code ZE)
  • 16-pin SOIC 300-mil (package code SF)
  • 1x4 + 4x5 24-ball 8x6mm TFBGA (package code TB)
  • 4x6 24-ball 8x6mm TFBGA (package code TC)

Lines

  • CLK serial clock input
  • /CS chip select input
    • High deselects the device, putting it into standby mode (reduced power consumption)
    • Transition to low places device into active mode
    • /CS must track VCC during initialization and shutdown
  • DI (IO0) data input / data io0
  • DO (IO1) data output / data io1
  • /WP (IO2) write protect input / data io2
  • /HOLD (IO3) hold input / data io3
  • VCC power (2.7V--3.6V)
  • GND

/WP and /HOLD are only for SPI/Dual-SPI (Quad-SPI uses data io 0--3). Data is always written on the rising edge of CLK, and read on the falling edge. SPI must write through DO and read through DI. Dual- and Quad-SPI treat data io pins as bidirectional.

Registers

Used with the ReadStatusRegister and WriteStatusRegister commands:

  • Protection Register (SR1)
    • MSB: Status register protect 0
    • B6, B5, B4, B3: Block protection bits, all initialized to 1 (unless set via OTP)
    • B2: Type of protection bit. When 1, protection applies to the lower end of the protected blocks; when 0, the upper end
    • B1: Write protection mode. Defaults to 0 (Software protection, Quad-SPI)
      • Hardware write protection (/WP, /HOLD) cannot be used with Quad-SPI
    • LSB: Status register protect 1
  • Configuration Register (SR2)
    • MSB: OTP lock. Once set to 1, the OTP area (10 2KB pages) cannot be reprogrammed.
    • B6: OTP access enable. Must be set to 1 to access OTP area.
    • B5: SR1 lock. Once set to 1, selected SR1 values are OTP-locked.
    • B4: ECC enable. Defaults to 1. Controls on-device bidirectional ECC.
    • B3: BUF mode select. Default depends on part number (IG defaults to 1). 1 is buffer read mode, 0 is continuous.
      • Buffer mode: provided a starting byte and a page, returns the page starting at that byte, plus the Spare Area
      • Continuous mode: provided a page, returns (multiple pages of) memory starting at the first byte of that page
      • Only buffer mode allows the Spare Area to be read
    • B2, B1, LSB: reserved
  • Status Register (SR3)
    • MSB: reserved
    • B6: LUT full, set to 1 when all 20 entries of the LUT are used
    • B5: ECC-1 (ECC status), set to 0 on successful read (even with corrections), 1 on uncorrected error
    • B4: ECC-0 (ECC details)
      • If ECC-1 is 0, 0 indicates no corrections, 1 indicates corrections.
      • If ECC-1 is 1, 0 indicates unusable page, 1 indicates multiple unusable pages (during continuous read)
      • Both ECC bits are reset to 0 only on initialization and following RESET
    • B3: PFAIL (Program failure), set to 1 when a ProgramExecute command fails
    • B2: EFAIL (Erase failure), set to 1 when a BlockErase command fails
      • Both PFAIL and EFAIL are reset at the beginning of each ProgramExecute or BlockErase
    • B1: Write-enabled latch, set to 1 following WriteEnable instruction, set to 0 following many instructions
    • B0: Busy, set to 1 while instructions are not being accepted following many instructions