{
  "id": "enwiki-001370518635",
  "slug": "jtag",
  "title": "JTAG",
  "qid": "",
  "lead": "JTAG (named after the Joint Test Action Group which codified it) is an industry standard for verifying designs of and testing printed circuit boards after manufacture. JTAG implements standards for on-chip instrumentation in electronic design automation (EDA) as a complementary tool to digital simulation. It specifies the use of a dedicated debug port implementing a serial communications interface for low-overhead access without requiring direct external access to the system address and data buses. The interface connects to an on-chip Test Access Port (TAP) that implements a stateful protocol to access a set of test registers that present chip logic levels and device capabilities of various parts. The Joint Test Action Group formed in 1985 to develop a method of verifying designs and testing printed circuit boards after manufacture. In 1990, the Institute of Electrical and Electronics Engineers codified the results of the effort in IEEE Standard 1149.1-1990, entitled Standard Test Access Port and Boundary-Scan Architecture. The JTAG standards have been extended by multiple semiconductor chip manufacturers with specialized variants to provide vendor-specific features.",
  "body": "JTAG (named after the Joint Test Action Group which codified it) is an industry standard for verifying designs of and testing printed circuit boards after manufacture. JTAG implements standards for on-chip instrumentation in electronic design automation (EDA) as a complementary tool to digital simulation. It specifies the use of a dedicated debug port implementing a serial communications interface for low-overhead access without requiring direct external access to the system address and data buses. The interface connects to an on-chip Test Access Port (TAP) that implements a stateful protocol to access a set of test registers that present chip logic levels and device capabilities of various parts. The Joint Test Action Group formed in 1985 to develop a method of verifying designs and testing printed circuit boards after manufacture. In 1990, the Institute of Electrical and Electronics Engineers codified the results of the effort in IEEE Standard 1149.1-1990, entitled Standard Test Access Port and Boundary-Scan Architecture. The JTAG standards have been extended by multiple semiconductor chip manufacturers with specialized variants to provide vendor-specific features. Shifting that value bit-by-bit, in either the Shift_IR or Shift_DR stable state; TCK transitions shift the shift register one bit, from TDI towards TDO, exactly like a SPI mode 1 data transfer through a daisy chain of devices (with TMS=0 acting like the chip select signal, TDI as MOSI, etc.). Updating IR or DR from the temporary value shifted in, on transition through the Update_IR or Update_DR state. Note that it is not possible to read (capture) a register without writing (updating) it, and vice versa. A common idiom adds flag bits to say whether the update should have side effects, or whether the hardware is ready to execute such side effects. Running ... One stable state is called Run_Test/Idle. The distinction is TAP-specific. Clocking TCK in the Idle state has no particular side effects, but clocking it in the Run_Test state may change system state. For example, some ARM9 cores support a debugging mode where TCK cycles in the Run_Test state drive the instruction pipeline. At a basic level, using JTAG involves reading and writing instructions and their associated data registers, and sometimes involves running a number of test cycles. Behind those registers is hardware that is not specified by JTAG, and which has its own states that are affected by JTAG activities. Most JTAG hosts use the shortest path between two states, perhaps constrained by quirks of the adapter. (For example, one adapter only handles paths whose lengths are multiples of seven bits.) Some layers built on top of JTAG monitor the state transitions and use uncommon paths to trigger higher-level operations. Some ARM cores use such sequences to enter and exit a two-wire (non-JTAG) SWD mode. A Zero Bit Scan (ZBS) sequence is used in IEEE 1149.7 to access advanced functionality such as switching TAPs into and out of scan chains, power management, and a different two-wire mode. == Similar interface standards == Serial Wire Debug (SWD) is an alternative 2-pin electrical interface that uses the same protocol. It uses the existing GND connection. SWD uses an ARM CPU standard bi-directional wire protocol, defined in the ARM Debug Interface v6. This enables the debugger to become another AMBA bus master for access to system memory and peripheral or debug registers. Data rate is up to . SWD also has built-in error detection. On JTAG devices with SWD capability, the TMS and TCK are used as SWDIO and SWCLK signals, providing for dual-mode programmers. IEEE Standard for Reduced-Pin and Enhanced-Functionality Test Access Port and Boundary-Scan Architecture The official IEEE 1149.7 Standard. , Intel whitepaper on JTAG usage in system software debug across a wide range of architectures. IEEE Std 1149.1 (JTAG) Testability Primer Includes a strong technical presentation about JTAG, with design-for-test chapters. Boundary Scan / IEEE 1149 tutorial including details of variants of the IEEE standard, BSDL, DFT, and other topics JTAG Tutorial Useful tutorials and information on JTAG technology. What is JTAG? Useful information on JTAG, timeline, architecture and more. JTAG Applications JTAG for product development, life cycle, testing, tools needed, and other topics.",
  "categories": [
    "125876068",
    "129826521",
    "22897364",
    "22914102",
    "22915359",
    "22920469",
    "22978714",
    "22985424",
    "22992747",
    "23045568",
    "23118434",
    "23556908",
    "23603337",
    "24623845",
    "24745122",
    "26460396",
    "27179390",
    "27179417",
    "44035751",
    "85550926"
  ],
  "license": "CC BY-SA 4.0",
  "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1370518635",
  "content_hash": "",
  "created_at": null,
  "updated_at": 1787321147.0,
  "claims": [
    {
      "id": 29657243,
      "subject_qid": "",
      "subject_slug": "jtag",
      "predicate": "date of formation",
      "object_text": "1985",
      "object_num": 19850000.0,
      "object_unit": null,
      "polarity": 1,
      "qualifier": "",
      "source_uri": "https://en.wikipedia.org/w/index.php?oldid=1370518635",
      "source_name": "Wikipedia",
      "source_tier": 3,
      "retrieved_at": 1792484590.6499975,
      "confidence": 0.95,
      "article_slug": "jtag",
      "span_start": 28,
      "span_end": 74
    }
  ],
  "contradictions": [],
  "confidence": 0.95,
  "csl": {
    "id": "enwiki-001370518635",
    "type": "webpage",
    "title": "JTAG",
    "author": [
      {
        "family": "Anticloud FZ LLE",
        "literal": "Anticloud FZ LLE"
      }
    ],
    "container-title": "encyclopegia.org",
    "publisher": "Anticloud FZ LLE",
    "publisher-place": "Dubai, United Arab Emirates",
    "URL": "https://encyclopegia.org/a/jtag",
    "issued": {
      "date-parts": [
        [
          2026,
          11,
          17
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          11,
          17
        ]
      ]
    },
    "license": "CC BY-SA 4.0",
    "DOI": "eo1:enwiki-001370518635",
    "isBasedOn": "https://en.wikipedia.org/w/index.php?oldid=1370518635",
    "note": "Immutable snapshot enwiki-001370518635"
  }
}