{
  "slug": "nand-target",
  "term": "NAND target",
  "aliases": [
    "ONFI target"
  ],
  "definition": "An ONFI NAND target groups one or more logical units that share a chip-enable signal within a NAND package.",
  "note": "A target is an interface-selection boundary, not a synonym for a host-visible filesystem volume, block-device volume or SSD. Its logical units can contain multiple planes, each grouping erase blocks. [onfi4]\n\nSoftware keeps these levels separate: Linux records target count, LUNs per target and planes per LUN as distinct geometry fields. Read the part's organization and driver conventions before translating a package or die count into a target count. [linux612]\n\nCE_n pin reduction changes the host-side count. ONFI 4.0 permits several NAND targets to share one host chip-enable signal, with Volume Select choosing the initialized target address. This protocol Volume is not a host filesystem volume; a host CE_n count alone need not equal the NAND target count. [onfi4]",
  "related": [
    "nand-logical-unit",
    "nand-plane",
    "nand-flash",
    "channel-nand",
    "die-stacking"
  ],
  "citations": [
    {
      "id": "onfi4",
      "title": "ONFI 4.0, sections 1.4.1, 2.20 and 3: NAND hierarchy and CE_n pin reduction",
      "url": "https://onfi.org/files/onfi_4_0-gold.pdf",
      "accessed": "2026-10-23"
    },
    {
      "id": "linux612",
      "title": "Linux v6.12, include/linux/mtd/nand.h: nand_memory_organization, nand_pos and nanddev_target_size",
      "url": "https://raw.githubusercontent.com/torvalds/linux/v6.12/include/linux/mtd/nand.h",
      "accessed": "2026-10-20"
    }
  ],
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "provenance": [
    "ONFI terminology is scoped to the cited editions; component geometry and supported command sequences must be checked for the selected device."
  ],
  "updated": "2026-10-23"
}