Method and apparatus for connecting manufacturing test interface to a global serial bus including an I2 c bus

[0002] The present invention relates generally to the data processing field, and more particularly, relates to methods and apparatus for connecting a manufacturing test interface to a global serial bus, such as, an inter integrated circuit (I²C) bus.

[0003] The I²C bus is an industry standard serial bidirectional 2-wire bus typically used to interconnect multiple integrated circuits by one or more masters and slaves. The I²C bus includes two bus lines, a serial data line (SDA) and a serial clock line (SCA). The I²C bus supports any integrated circuit (IC) fabrication process, such as negative-channel metal oxide semiconductor (NMOS), complementary metal oxide semiconductor (CMOS), and bipolar. Serial data (SDA) and serial clock (SLC) information are carried by two wires between multiple devices connected to the 1²C bus.

[0004] A need exists for methods and an effective mechanism to connect a manufacturing test interface, such as a Joint Test Action Group (JTAG) interface IEEE 1149.1 specification, to a global serial bus including an inter integrated circuit (I²C) bus. It is desirable to use the global serial bus, such as the I²C bus, to query VPD information, provide register access, and perform testing in multiple devices attached to the serial bus including memory and IO subsystems.

[0005] A principal object of the present invention is to provide methods and apparatus for connecting a manufacturing test interface to a global serial bus, including an inter integrated circuit (I²C) bus. Other objects are to provide such methods and apparatus substantially without negative effects and that overcome many of the disadvantages of prior art arrangements.

[0006] In brief, methods and apparatus are provided for connecting a manufacturing test interface to a global serial bus, such as an inter integrated circuit (I²C) bus. Input/output buffer logic buffers data to be transferred to and from the global serial bus. A slave interface logic connected to the input/output buffer logic receives and sends data to the input/output buffer logic. A slave controller coupled to the input/output buffer logic and to the slave interface logic paces data exchange to the input/output buffer logic.

[0007] In accordance with a feature of the invention, error detection logic is coupled between the input/output buffer and the global serial bus for detecting an error.

[0008] The present invention together with the above and other objects and advantages may best be understood from the following detailed description of the preferred embodiments of the invention illustrated in the drawings, wherein:

[0009] FIG. 1 is a block diagram representation of manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus in accordance with the preferred embodiment;

[0010] FIG. 2 is a block diagram representation illustrating slave data and control registers of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (1²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0011] FIG. 3 is a block diagram representation illustrating a slave IO buffer logic of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0012] FIG. 4 is a block diagram representation illustrating a slave test access port (TAP) interface of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0013] FIG. 5 is a block diagram representation illustrating a slave controller of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0014] FIG. 6 is a block diagram representation illustrating data pacing between IO buffer logic of the I²C slave state machine and a physical interface of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0015] FIG. 7 is a block diagram representation illustrating data pacing between IO buffer logic of the I²C slave state machine and a slave test access port (TAP) interface of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0016] FIG. 8 is a block diagram representation illustrating a slave error handling logic of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0017] FIG. 9 is a block diagram representation illustrating multiple states of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0018] FIGS. 10A and 10B respectively illustrate primitive write control flow and primitive read control flow of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0019] FIGS. 10C and 10D respectively illustrate register write control flow and register read control flow of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment;

[0020] FIGS. 10E and 10F respectively illustrate control write control flow and control read control flow of the I²C slave state machine of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment; and

[0021] FIG. 11 is a block diagram representation illustrating a test access port (TAP) and boundary-scan architecture, Access of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus of FIG. 1 in accordance with the preferred embodiment.

[0022] Having reference now to the drawing, FIG. 1 illustrates a manufacturing test interface and global inter integrated circuit (I2C) bus interconnection apparatus generally designated by the reference character 100 in accordance with the present invention. Manufacturing test interface and I²C bus interconnection apparatus 100 includes a slave I²C state machine and translator 102 connected via an I²C physical interface 104 to an I²C bus 106. Manufacturing test interface and I²C bus interconnection apparatus 100 can be defined by a single integrated circuit chip. I²C state machine and translator 102 is connected with a multiplexer (MUX) 108 via an internal JTAG bus 110. MUX 108 is connected to an external JTAG bus 112. A control input 113 is applied to the MUX 108 to select between the internal JTAG bus 110 and the external JTAG bus 112. A test access port and boundary-scan architecture, Access 114 or other JTAG implementation is connected between MUX 108 and clock control, built in self test (BIST) and other functions 118, up to 2²³architected registers 120, and JTAG scannable registers or test data registers (TDRs) 122.

[0023] In accordance with features of the preferred embodiment, manufacturing test interface and I²C bus interconnection apparatus 100 bridges the gap between the I²C bus 106 and JTAG test access port (TAP) Access 114 in a unique manner, allowing the interconnection apparatus to support both native I²C register transfer protocol and full JTAG functionality. Manufacturing test interface and I²C bus interconnection apparatus 100 adheres to industry standard I²C bus protocol, while not limiting JTAG functionality. Manufacturing test interface and I²C bus interconnection apparatus 100 minimizes interconnect wiring, introduces chip-level addressability, and defines direct memory mapped input/output (MMIO) read and write register addressability.

[0024] In accordance with features of the preferred embodiment, manufacturing test interface and I²C bus interconnection apparatus 100 enables the use of manufacturing test hardware for in-circuit datapath, test, and lab/field debug functions. Manufacturing test interface and I²C bus interconnection apparatus 100 introduces a new scan controller instruction, Scan Communications Read-Immediate, reducing register read response latency on I²C bus 106. Manufacturing test interface and I²C bus interconnection apparatus 100 simplifies and reduces connections for system-level manufacturing testing. System level manufacturing tests may use a single I²C connection 106 for test interface, simplifying the test hook-up procedure and software required to perform integration and burn-in tests.

[0025] I²C state machine and translator 102 converts data sent across the I²C bus 106 into native JTAG commands. I²C state machine and translator 102 can be used as a TAP controller that interfaces with Access 114 in order to perform reading, writing and scanning registers within a chip attached to I²C bus 106. I²C state machine and translator 102 can initiate Logic Built In Self Test (LBIST) or Array Built In Self Test (ABIST), scan JTAG TDRs 122, control chip clocking, as well as any other features that can be initiated via JTAG bus 112 that are implemented by Access 114. Manufacturing test interface and I²C bus interconnection apparatus 100 uses a 7 bit slave addressing mode, allowing 2⁷slaves to be directly addressed. The protocol implies that an addressed slave responds to read/write by addressing successive bytes serially, starting in memory where defined by the particular slave. Manufacturing test interface and I²C bus interconnection apparatus 100 extends direct-addressing to 2²³, operating on 8-byte aligned registers. In addition, operations other than register read/write which are supported by Access 114 are available.

[0026] The serial I²C bus 106 consists of two wires for serial data (SDA) and serial clock (SDC) which rest at 1 while the bus is quiescent. Any bus master may initiate a message transfer with a start bit (SDA 1→0 while SCL=‘1’). I²C bus protocol operates on packets, each one byte wide, and each followed by an acknowledge bit (0=good ask). When the message begins, the slave owns driving the SDA during the acknowledge bit timing, the master owns driving SCL and SDA at other times. Master Logic always owns the clock. Slave owns SDA on reads except for the acknowledge bit. Each SDA data/ack bit must remain stable 1 or 0 while SCL clocks (0→1→0); such that SDA is setup prior to SCL rising edge, is held after falling edge, and transitions while SCL is low.

[0027] Packet bits are transmitted most significant bit first (bit1). The start byte bits 1:7 address a particular slave chip. Bit 8 of the start byte is a read/write bit. Writes progress with the master sending bytes and the slave acknowledging. A read begins as the master writes the start byte, but the dataflow reverses after the slave acknowledges the start byte. Now the slave is sending packets and the master is acknowledging. The slave continues to send until the master Ack=1. All transmissions end with a stop bit (SCL=1 while SDA 0→1). The bus is quiescent again following the stop bit.

[0028] IEEE 1149.1 defines a 5-wire interface called test access port for communicating with boundary-scan architecture. Access 114 is a specific implementation of the Joint Test Action Group (JTAG) interface IEEE 1149.1 specification. JTAG test access port (TAP) 5 wires include JTAG test clock input (TCK), JTAG test data input (TDI), JTAG test data output (TDO), JTAG test mode select input (TMS), and JTAG test logic reset input (TRST). The rising edge of test clock input (TCK) causes TMS and TDI to be sampled by Access 114.

[0029] The value of JTAG test mode select input (TMS) during the rising edge of TCK causes a state transition in the TAP controller of Access 114. Test data input (TDI) is serial data input to Access 114. Test data output (TDO) is the serial data output from Access 114. JTAG test logic reset input (TRST) causes an asynchronous reset of the test logic (TAP→TestLogicRst) for recovering Access 114. ShiftIR is the state where an instruction is serially shifted between TDI and TDO inside Access 114. While TMS is held 0, each TCK clock causes another bit to be shifted into the instruction register from TDI and IR Status to be shifted out TDO. The contents of the instruction register determine the specific TDR addressed, or non-register operation to be performed. ShiftDR is the state where one of many data registers (TDRs) is serially connected between TDI and TDO. While TMS is held 0, each TCK clock causes another bit to be shifted into the register from TDI and (old) data to be shifted out TDO.

[0030] FIG. 2 illustrates primary slave data and control registers of the I²C state machine and translator 102 generally designated 200 in accordance with the preferred embodiment. I²C slave logic 200 includes an input/output buffer register (IOBUF) 201 for data, address and register read/write (R/W) buffering and an associated input/output byte count register (IOCNT) 202. I²C slave logic 200 includes an error detect 203 coupled between the physical interface 104 and a slave JTAG interface 204. I²C slave logic 200 includes a slave controller 206 coupled to physical interface 104, input/output byte count register (IOCNT) 202, and slave JTAG interface 204. Slave JTAG interface 204 includes a serial shift register (SSR) 208 and a bit count register (BCR) 210 associated with the serial shift register (SSR) 208. Slave JTAG interface, 204 includes a test mode select (TMS) select register (TSR) 212 and TMS terminal select register (TTSR) 214, a clock generator (CG) 216 providing test clock input (TCK), and a MUX 218 providing JTAG test mode select input (TMS).

[0031] The Physical Interface 104 handles I²C protocol and timing, providing a one byte wide data interface along with associated handshaking signals. SDA refers to the bidirectional Serial Data signal defined by I²C. SCL refers to the Serial Clock signal defined by I²C. Operation of the physical interface 104 is generally in accordance with the conventional implementation of the I²C standard.

[0032] The IO Buffer (IOBUF) 201 buffers successive bytes transferred to and from the chip addressed as the Slave chip by the I²C Start Byte. Data in the IOBUF 201 is transferred in parallel, one byte at a time to and from the physical interface 104. The entire start byte is held in the IOBUF 201, but only the read/write bit is further used by the I²C state machine 102. During write operations, data flow is from I²C bus 106 to TDI or TMS of the internal JTAG bus 110. During read operations the data flow is from TDO of the internal JTAG bus 110 to I²C bus 106. The Serial Shift Register (SSR) 208 can receive or supply up to 8 bytes in parallel from and to the IOBUF 201. This data is then serially shifted to and from internal JTAG bus 110 following IEEE 1149.1 protocol.

[0033] The physical interface 104 monitors the I²C bus 106 and receives incoming/outgoing bytes. If the byte is a start byte, physical interface 104 compares the 7-bit slave address to the chip address. The start byte and remaining message are ignored if the address does not match. Physical interface 104 asserts a signal to the slave controller 206 indicating a byte has been received.

[0034] The slave controller 206 paces data exchange to and from IOBUF 201 decrementing the IO count (IOCNT) 202 to keep the data aligned properly in the IOBUF 201. When the end of the message is received or sent, or when the IOBUF overflows or underflows, the slave controller 206 transfers data between the SSR 208 and IOBUF 201 and triggers slave JTAG interface 204 to perform one or more JTAG primitive operations. As used in this specification and claims, a primitive operation is defined to mean a sequence of one or more test clock input (TCK) pulses to drive either test mode select (TMS), control, or TDI/TDO, instruction or data/status, to and from the internal slave JTAG interface 204.

[0035] FIG. 3 illustrates the slave IO buffer logic implementing the IOBUF 201 and IOCNT 202. Slave IO buffer logic 201 and IOCNT 202 includes an IO count register (IOCNTL2) 302, an up/down counter 304, a compare (>“1011”) 306, an AND gate 307, an IO buffer (IOBUFL2) 308, and a pair of multiplexers (MUX IOA, MUX IOB), 310, 312. IOCNT 202 is equivalent to IO count register (IOCNTL2) 302, and up/down counter 304.

[0036] When quiescent, the IO Count Register (IOCNTL2) 302 is parallel-loaded with Count Data (CNTDATA) of b‘1011’, pointing to the least-significant byte of the IO Buffer 201. The I²C state machine 102 indicates CNTDATA is valid by asserting LOADCNT, applied to IOCNTL2302. As bytes are transferred over I²C Bus 106 the count is decremented, successively pointing at the next-most-significant byte. The I²C physical interface 104 handles transferring bits (most significant bit first), the IOBUF 201 presents and accepts bytes to and from the I²C physical interface 104 (least significant byte first).

[0037] If the start byte indicates a read operation on I²C bus 106, the I²C state machine 102 jumps IOCNT ahead to the data portion of the IO Buffer 201 by asserting LOADCNT active and CNTDATA=b‘0111’ in preparation of returning data to I²C bus 106.

[0038] The IOCNT register IOCNTL2302 is reused during register read/write operations as a primitive operation step counter 304. In this mode, CountUp, applied to step counter 304, is activated by the I²C state machine 102 each time the next primitive command step in the register read/write sequence is executed. Only the IOCNTL2 and data portion of IOBUF 201 are changed, the IOBUF address and start bytes retain their values.

[0039] The 12-byte IO Buffer Register (IOBUFL2) 308 is loaded, one byte at a time, from right to left beginning with the start byte. The data from the I²C Physical Interface 104 arrives on signal IS_BYTE_O, and is indicated valid by signal COUNTBYTE from the I²C state machine 102. MUX IOA 310 feeds back IOBUF data to all bytes except the byte pointed to by IOCNT, which is replaced with the data on IS_BYTE_O.

[0040] Read information is presented to the Physical Interface 104 on signal IS_BYTE_I. MUX IOB 312 selects the IOCNT'th byte to be driven on IS_BYTE_I. Data from the SSR 208 is parallel loaded into the data portion of the IOBUF 201 when the BUFLOAD signal is activated by the I²C state machine 102. This occurs at the end of a register read primitive sequence, or after a one-step JTAG primitive command is executed at the request of an I²C command.

[0041] The data, command/address, and r/w bit are presented to the I²C state machine 102 and the SSR 208 over the IOBUFL2 (0:95) signal. The OVERRUN signal generated by AND gate 307 indicates IOBUF full/empty condition.

[0042] TABLE 1 below provides MUX definitions for multiplexers (MUX IOA, MUX 10B), 310, 312, where x indicates don't care.

[0043] FIG. 4 illustrates slave Test Access Port (TAP) interface logic implementing JTAG interface 204. Slave TAP interface logic 204 includes a TAP clock state machine (TAPCMSL2) 402, a plurality of multiplexers (MUX A, MUX B, MUX C, MUX D, MUX E), 404, 406, 408, 410, and 412, a plurality of registers (SSRL2(0:63), TTSRL2, TSRL2, BCRL2(0:5), 414, 416, 418, and 420, a down counter 421, a compare (=“111111”) 422, a plurality of latches 413, 424 and 426, and a pair of AND gates 428 and 430.

[0044] When the Load Command (LOADCMD) signal is activated, the Test Access Port Command (TAPCMD) is considered valid to initiate activity on the internal JTAG bus 110. The information on the TAPCMD signal is loaded into the command registers as described below, and the one clock (ONECLK2) latch 426 is set to 1 to release at one or mote TCK pulses. See definitions for TAP Clock State Machine (TAPCSM) 402, TAP Primitive Command Interface, and MUX D 410 in the following TABLES 2, 3 and 4. MUX B 406 provides feedback, holding the command registers present value while LOADCMD is not active. MUX A 404 likewise holds the SSR (data) value.

[0045] The TAP Clock State Machine (TAPCMSL2) 402 remains in idle until activated by ONECLKL2. The state machine 402 proceeds sequentially through states TCKF1, TCKR0, TCKR1 before returning to IDLE. The machine 402 continues to loop through these states as long as ONECLKL2=1. TCK is driven to 1 in the TCK Rise (TCKR0, TCKR1) states, effectively dividing the base slave clock frequency by a factor of four and providing roughly 50% duty cycle. The BCR is decremented and the SSR data is shifted one bit right in the TCKR1 state. The JTAG requirement that TDO be sampled on the rising edge of TCK is achieved by loading the TDOL2 latch 413 from TDO in the TCKR0 state. See MUX E 412 definition in TABLE 4 below.

[0046] The state of the state machine 402 is greycoded to prevent glitches on TCK during state transitions. Outputs are 0 unless specified otherwise in state table.

[0047] The tap command (TAPCMD) signal applied to MUX A 404, MUX B 406, and BCRL2420 is 9 bytes wide. The first byte is a primitive command to be performed by the JTAG Scan Logic 204. TMS Select Register (TSRL2:TAPCMD bit 0) 418 determines whether MUX C 408 will select SSR data from SSRL2 (0:63) 414 to be shifted out to TMS, or a constant value. A zero 0 indicates that the data in SSRL2414 is a stream of TMS control information. A 1 directs MUX C to select a static 0 value driven on TMS of the first N−1 TCK clock pulses; the TTSRL2416 value is then driven on TMS during the Nth (terminal) TCK pulse.

[0048] Terminal TMS Select Register (TTSRL2:TAPCMD bit 1) 416 provides a value on TMS during the Nth (terminal) TCK pulse. TTSRL2416 is intended for long scanning operations when the 64-bit width of the SSR is insufficient to complete the scan. TTSRL2=0 will bridge primitive operations, allowing the scan to continue with another primitive command. TTSRL2=1 terminates the operation by moving the JTAG TAP state inside Access 114 out of the shift-DR or shift-IR state. Test Logic Reset (TRST) is formed by gating TAPCMD bits 0:1 in a combination not otherwise used for primitive commands. This output of AND gate 428 is latched by latch 424 to de-glitch the Test Logic Reset TRST signal. Bit Count Register 420 (BCRL2:TAPCMD bit 2:7) defines the number of TCK pulses to send, along with a sequence of information on TMS or TDI. A BCR value of b‘111110’ indicates that 64 TCK pulses are to be sent (the entire SSR register 414 will be right-shifted out of TDI or TMS, shifting TDO back into the SSR on the left. BCR=b‘111111’ is the terminal count, indicating that one TCK pulse is to be released.

[0049] The definition of the first byte of the TAPCMD is summarized in the following TABLE 3.

[0050] The remaining bits of the TAPCMD signal represent data to be loaded into the SSR 208 in preparation of shifting out TDI or TMS.

[0051] When the BCR reaches b‘111111’ the command is done. The ONECLKL2 latch 426 returns to 0 and the TAPCMD state machine 402 rests in idle. The internal JTAG bus 110 is inactive. The CMDDONE signal output of AND gate 430 is fed back to the I²C Slave State Machine 102 as an indicator that a new primitive command may be initiated.

[0052] In the following TABLE 4 of MUX definitions for multiplexers (MUX A, MUX B, MUX C, MUX D, MUX E), 404, 406, 408, 410, and 412, x indicates don't care, and /= means is not equal to.

[0053] FIG. 5 illustrates slave controller logic implementing slave controller 206. Slave controller logic 206 includes an I²C Slave State Machine logic (I2CSSML2(0:3) 502, a compare (=) 504, a plurality of multiplexers, MUX SMA 506 for TAP CMD routing, MUX SMB 508 for data routing, MUX SMD 510 for control. Slave controller logic 206 includes a register read/write (REGRW) bus sync logic 512. REGRW bus sync logic 512 includes a pair of AND gates 514, 516, a SC idle latch (SCIDLEL2) 520, a NOT gate 522 and a multiplexer MUX SMB 524. Slave controller logic 206 performs multiple basic functions as follows. I²C Slave State Machine logic (I2CSSML2(0:3) 502 paces data exchange between the physical interface 106 and IO buffer logic 300 and paces data exchange between the IO buffer logic 300 and JTAG scan logic 204. MUX SMA 506 for TAP CMD routing provides an ordered sequence of commands for register read/write operations. REGRW bus sync logic 512 paces data exchange between the JTAG scan logic 204 and Access 114. MUX SMB 508 for data routing minimizes I²C bandwidth requirements for data routing.

[0054] TABLES 5, 6, 7, and 8 respectively provide multiplexer definitions for MUX SMA 506, MUX SMB 524, MUX SMC 508 and MUX SMD 510 of the slave controller 206.

[0055] The IOBUF 201 and SSR 208 data do not always transfer byte for byte. If I²C uses a Primitive Command sequence to address a TDR shorter than, or not an even multiple of the IOBUF/SSR register width then the data from I²C bus 106 is left-aligned in IOBUF 201 so that an overflow can be detected when all the significant data has been received. The IOBUF 201 data is right-aligned when it is loaded into the SSR 208. The data scanned-out of the targeted TDR is left-aligned in the SSR 208 and remains left-aligned when transferred to IOBUF 201 again so that underflow of data returned to I²C can be detected at the proper time.

[0056] REGRW bus sync logic 512 uses the SCidle signal for register read/write bus synchronization. In CHKADR state, SCidleL2 latch 520 is set to 1 (assume SCIDLE signal from Access 114 is active). When a register R/W operation initiates, SCIDLE goes low, resetting ScidleL2520. When the register read operation completes, SCIDLE and not SCidleL2 indicates the register read data is available inside Access 114. The register read sequence in the TABLE is paused after completing the third step to sync with the register read bus using this logic.

[0057] FIG. 6 shows the signals needed to pace data transfer between IOBUF 201 and physical interface 104. The signal definitions may be best understood having reference to the state machine description.

[0058] FIG. 7 illustrates IO Buffer 201 to JTAG Scan Logic 204 data pacing. FIG. 7 shows the signals used to pace data transfer between IOBUF 201 and JTAG Scan Logic 204. The signal definitions may be best understood having reference to the state machine description.

[0059] Referring now to FIG. 8, error handling logic implementing error detect 203 is shown. Error handling logic 203 includes a cyclic redundancy check (CRC) logic 802 for CRC checking transferred data to and from the I²C bus 106. Error handling logic 203 includes an ACK TYPE MUX 804 receiving inputs: CRC_Good, Attention, IOCNTL2, read_or_write, and a primative command from a compare 808.

[0060] The I²C state machine 102 and error handling logic 203 receives the Attention input from the,JTAG TAP Controller Access 114. This Attention input from Access 114 may be activated as a result of a register read/write bus error or from a number of other error scenarios. Read_or_write is an input from I²C state machine buffered from Physical Interface 104. IOBUFL2 is an input to compare 808 from IO buffer Logic 201. TapCmdAdr applied to compare 808 is a constant configurable as internal constant, or via chip IO pins. IOCNTL2 is an input to MUX 804 from IO buffer Logic 201. CRC_Good is a signal from CRC logic 802 indicating the CRC byte was correctly transferred. Is_slave_ack_type is an output from the MUX 804 of the error handling logic 800 to the Physical Interface 104.

[0061] The I²C slave handles errors with an acknowledgment pulse. I²C requires an acknowledgment of every byte of data on the Ack or 9th clock cycle and also on 9th bit of the slave address. When the slave encounters an error, it will no longer acknowledge its address and data when trying to do a read sequence. This way software can determine that there is an error condition and use the I²C bus 106 to determine what caused the error so a recovery can be made from the error condition.

[0062] There are several situations that could cause the slave to not acknowledge on a read or a write sequence. For example, if CRC-Checking has been enabled the slave will not acknowledge the 13th byte in order to prevent software from overwriting the data. These 13 bytes include the slave address, the 3 byte register read address, 8 data bytes and a CRC byte. The write will only occur if the CRC was calculated and transmitted correctly. Without CRC checking, data will be over written if software writes more than 8 bytes of data. When the Attention signal is raised inside Access 114 and the Attention has not been blocked inside the state machine will cause a No-Ack when trying to do a register read direct sequence. If doing a write sequence and the 3-byte address sent was not a primitive address, the slave will not acknowledge the data bytes being sent across the I²C bus 106. Once CRC checking has been enabled and the CRC sent on the I²C bus was not correct, the slave will not acknowledge on the next read attempt.

[0063] Referring now to FIGS. 9, 10A, 10B, 10C, 10D, 10E and 10F, in FIG. 9 sequential states of state machine 102 are shown. FIGS. 10A and 10B respectively illustrate primitive write control flow and primitive read control flow of the I²C slave state machine 102. FIGS. 10C and 10D respectively illustrate register write control flow and register read control flow of the I²C slave state machine 102. FIGS. 10E and 10F respectively illustrate control write control flow and control read control flow of the I²C slave state machine 102.

[0064] At an IDLE State 902 of the I²C slave state machine 102, there is no I²C activity. IOcntL2 is loaded with b‘1011’, pointing at LSByte of IOBUFL2 in preparation of receiving start byte. A plurality of states are I²C Write States including an AMATCH state 904, a WBYTE state 906, a CHKOVRFLW state 908, and a WRTACK state 910. In the Write I²C states, when I²C master is writing bytes to slave, the first byte is always a start byte that addresses the slave. The eighth bit of the start byte is a Read/Write bit. The next three bytes are interpreted as either a register address, Primitive TAP Command, or Slave Control Command. The remaining bytes are data.

[0065] In the AMATCH State 904 (Address Match), the Physical Interface 104 has recognized a start bit and is assembling the (next) byte of a message. AMATCH state 904 returns to IDLE state 902 when a repeated start, or the start byte address mismatches, sending the slave back to IDLE. If the message ends before the first four bytes (start+address bytes) are received, the slave returns to IDLE. If CRC is enabled and a CRC error is detected, AMATCH state 904 returns to IDLE state 902. AMATCH state 904 moves to WBYTE state 906 when 8 or more bits are received by the Physical Interface 104. One specific implementation of the Physical Interface 104 indicates Is8times prior to IsStartDetected during the start byte, requiring Is8times to be latched (Is8timesL2) so that it is not missed. AMATCH state 904 moves to a CHKADR state 912 when a stop bit has been detected by the Physical Interface 104 after one or more bytes of data have been received.

[0066] In the WBYTE state 906 (Write Byte), the Is_Byte_O from the Physical interface is written to the IOBUFL2(IocntL2^thbyte) then IOcntL2 is decremented. WBYTE state 906 moves to CHKOVRFLW state 908 if this is an I²C write operation. The dataflow continues from master/initiator to slave. WBYTE state 906 move to CHKADR state 912 when this is I²C read operation. The dataflow reverses after the start byte. The master will now receive data from the slave.

[0067] In the CHKOVRFLW State 908, (Check for Over(under)flow in IO Buffer), there is no action. CHKOVRFLW State 908 moves to the WRTACK state 910 when this is a write operation and the IOCntL2 has not wrapped from b‘0000’ to b‘1111’, there is space for more bytes in IOBUFL2. CHKOVRFLW state 908 moves to a WAITREAD state 910 in the case when a Register read or Primitive command has already filled IOBUFL2 and the CHKOVRFLW state 908 was entered from an RBYTE state 932 from the I²C read states. One or more bytes have already been read, but IOBUFL2 has not yet underflowed. Move to CHKADR: IOBUFL2 is full/empty, trigger a Register write/read or Primitive operation.

[0068] The WRTACK State 910 (Acknowledge the I²C byte just written to slave), provides a Good Ack action if within the first four bytes of message (start+3 address bytes). WRTACK State 910 provides a fail Ack if Register read address and Attention is active from Access 114. An IsDoRead (IOBUF read the byte written by I²C master) is activated to Physical Interface 104 indicating that a byte is ready for the IOBUF. NeedAckL2 is reset. If this is was the fourth byte (last address byte just written to IOBUF; IOcntL2 now=7) and address indicates a Primitive command, look at ValidBytes, which is decoded from the BCR field of the Primitive to jump IOcntL2 ahead in the data buffer. For example: BCR=b‘000000’, only two bits will be transmitted to Access 114 so only one byte of data is needed. IOcntL2 is advanced to b‘0000’ so that the overflow will occur immediately after the first byte of data. Otherwise I²C would have to waste time transmitting another 7 bytes of data that are insignificant.

[0069] The WRTACK state 910 moves to AMATCH state 904 with NeedAckL2. The Physical Interface 104 activates IsAckSeht for one cycle after the ack is sent/received. NeedAckL2 remembers, in case the slave state machine was waiting until the Ack was sent.

[0070] In the CHKADR state 912 (Check Address), the IOBUFL2 address field is examined to determine if this is a Register read/write, Primitive, or Control command where I²C Slave Command Formats are used. Primitive signal is active for both Primitive and Control operations. SCidleL2 is set in case this is a Register read/write operation. REGRW Bus Sync Logic 512 will monitor the Register read/write (architected register r/w) bus to keep the JTAG command steps from overrunning the Register read/write operation. The IOcntL2 reg is set to b‘0001’ in case this is a Register read/write operation. In this case, IOCNT will step through a defined sequence of Primitive TAP commands in order to accomplish the Register read/write operation.

[0071] CHKADR state 912 moves to IDLE state 902, Register reads will Fail Ack if Attention is active or CRC is enabled and miscompares. CHKADR state 912 moves to one of the register read/write command states, a REGRWGO state 918 when IOBUFL2 address does not match primitive base address. CHKADR state 912 moves to one of the primitive command states, a LDTAPCMD state 914 when IOBUFL2 address matches primitive r/w command address. CHKADR state 912 moves to a CHKSTOP state 924 when IOBUFL2 address matches one of the control command addresses. These commands are accomplished without any JTAG bus activity.

[0072] The Primitive Command States include the LDTAPCMD state 914 and a WAITTAPDONE state 916. The IOBUFL2 address bytes match the address reserved for directly communicating to the on chip JTAG interface. Either TMS or TDI/TDO activity will occur, but not both. Any number of bits, up to the width of the SSRL2 register will be transferred, according to the Primitive TAP Command loaded in IOBUFl2 byte ten.

[0073] In the LDTAPCMD State 914, (Load TAP Command), the TAP Command is loaded from IOBUFL2(byte ten) into the JTAG interface 204. The LoadCmd and ValidBytes signals work together to load significant byte-aligned data into the rightmost bytes of the SSRL2. This implies that the data must be sent by I²C right-aligned within the data field. For example: if BCR-b‘000111’, 9 bits will be transmitted to Access 114, LSByte of data from I²C physical interface 104 must contain 8 significant bits, the next byte from I²C physical interface 104 contains one significant bit, which must be sent as the right-most bit within that byte.

[0074] In the WAITTAPDONE state 916, (Wait for TAP Done), there is no action. The JTAG interface 204 is busy executing a Primitive TAP command. WAITTAPDONE State 916 moves to CHKSTOP state 224 with CmdDone from the JTAG interface 204 signaling when the hardware is finished.

[0075] In the CHKSTOP state 924, (Check for I²C Stop condition), the register read/write operations always transfer 8 bytes but Primitive commands may conclude with only a portion of the data being valid in SSRL2. IOcntL2302 is loaded with ValidBytes which indicates how many left-aligned bytes contain valid data. For example: BCR 210 started with b‘000111’ (9 bit transfer). SSRL2414 initially held right-aligned 9 bits, so only bytes 6, 7 were valid. After the Primitive command completed, TDO data was captured left-aligned in SSRL2414, so only bytes 0, 1 are valid.

[0076] CHKSTOP state 924 moves to the IDLE state 902, when an I²C stop bit has been detected, and no further action is required. This is an unlikely path, unless the register read/write operation is delayed with a long timeout. CHKSTOP state 924 moves to a LOADRESULTS state 926 when there is read data in the SSR 208 that needs to be returned to I²C physical interface 104. CHKSTOP state 924 moves to the WRTACK state 910 when the write requested by I²C physical interface 104 is complete and I²C physical interface 104 will be expecting the slave to acknowledge (ACK) the most recent byte transferred.

[0077] I²C Read states include the LOADRESULTS state 926, a READACK state 928, a WAITREAD state 930, and a RBYTE state 932.

[0078] In the I²C Read states, I²C physical interface 104 is reading bytes from a slave. A register read, Primitive, or Control read followed by the LOADRESULTS and READACK states 926 and 928 are executed each time the IO Buffer 201 runs out of data. The master owns all timing back from the slave. The master may read one or more bytes, terminating the I²C transfer when Ack=1. The loop formed by WAITREAD, RBYTE, and CHKOVRFLW states 930, 932 and 908 is executed once for every byte transferred.

[0079] In the LOADRESULTS State 926 (Load data from SSR to IOBUF), if the JTAG operation just performed was a Primitive, then the data is still in SSRL2414 and must be copied into IOBUFL2308. Otherwise this was already done in step six of a Register read/write operation described below, and the SSR is garbage.

[0080] In the READACK state 928 (Wait for Acknowledge of the I²C byte just read from slave), the Physical Interface 104 takes care of read timing, including waiting for the Ack bit. Referring also to FIG. 6, after Physical Interface 104 receives the Ack, Physical Interface 104 indicates that it needs another byte from IOBUF 201 by activating IAckReady which sets a NeedAckL2 latch. IsWrtReady is activated back to the Physical Interface 104 to indicate that the next byte is ready to be written from IOBUF 201 onto Is_Byte_I. At the same time, NeedAckL2 is reset.

[0081] READACK state 928 moves to the WAITREAD state 930 if the Physical Interface 104 is busy either sending another data byte back to the master, or if. Ack=1, waiting for the stop bit, which is the only possible condition allowed by I²C protocol upon termination of a read.

[0082] In the WAITREAD State 930 (Wait for I²C to read a byte from slave), there is no action. The Physical Interface 104 is busy either sending another data byte back to the master, or if Ack=1, waiting for the stop bit.

[0083] WAITREAD State 930 moves to the IDLE state 902 when the first data byte read by the master was acknowledged with a ‘1’, then exitting to IDLE is provided as soon as the stop bit is detected by the Physical Interface 104. Otherwise, NeedAckL2 indicates when the Physical Interface 104 has completed sending another byte to the master and received Ack=1, upon which exitting to IDLE state 902 is provided. The IDLE state 902 will activate IsWrtReady to allow the Physical Interface 104 to begin looking for the stop bit, reset NeedAckL2, and consume the stop bit. WAITREAD State 930 moves to RBYTE state 932 when the Physical Interface 104 has received Ack=0, indicating another data byte is needed.

[0084] In the RBYTE State 932 (Set up to read another byte of data), the IOcntL2302 is decremented, pointing to the next data byte in IOBUFL2308.

[0085] Register read/write (REGRW) Command States include the REGRWGO state 918, a WAITCMDDONE state 920 and a CMDSTEP state 922. The IOBUFL2 address bytes do not match any address reserved for Primitive or Control commands. The address is interpreted directly as a register read/write address. Both TMS and TDI/TDO activity will occur in a sequence of defined steps in order to accomplish the register read/write operation. Exactly 64 bits, the width of the SSRL2 register 414 will be transferred.

[0086] In the REGRWGO State 918, (Start the (next) step of the Register Command Sequence), the (next) step in the Register sequence is put on the TapCmd bus and LoadCmd activated to start the JTAG interface 204. If IOcntL2=step 6, the data read by register read is in SSRL2414 and needs to be saved to IOBUFL2308 before the cleanup steps that return the Access 114 TAP controller to RunTestIdle, the final command steps would otherwise corrupt the data in the SSR. This is accomplished by activating BufLoad.

[0087] In the WAITCMDDONE State 920, Wait for TAP and/or Register read Done), there is no action. Either the JTAG Scan Logic is busy executing a Primitive TAP command or the Register read operation has been initiated but is not yet complete.

[0088] WAITCMDDONE state 920 moves to CMDSTEP state 922 when the CmdDone signal from JTAG Scan Logic indicates the most recent command step is complete and the RegisterRWdone signal is active after the SCIDLE signal form Access has gone inactive followed by a return to active. The RegisterRWdone signal is only significant during step 3 of a Register read, immediately after which the Register read operation should occur.

[0089] In the CMDSTEP state 922, (Advance to the next command step), IOcntL2 is incremented, IOcntL2 is being used in CmdMuxSel to index through the Register read/write command steps.

[0090] CMDSTEP state 922 moves to SCOMGO: Both Register read and write command sequences are exactly 7 steps long. If step 7 has not yet completed, looping back to initiate the next step is provided. CMDSTEP state 922 moves to the CHKSTOP state 924 when the 7th step has just completed.

[0091] FIG. 11 illustrates primary functions of the test access port (TAP) and boundary-scan architecture, Access 114 of the manufacturing test interface and global inter integrated circuit (I²C) bus interconnection apparatus 100. Access provides a JTAG scan function 1102 and a scan communications function 1104. JTAG scan function 1102 allows the I²C slave state machine 102 to scan chip rings through the test access port (TAP) interface (IEEE 1149.1) indicated at line TAP/SP. The Attention output and a power-on-reset (POR) output are also provided indicated at line TAP/SP. The Attention output is provided to alert the I²C slave state machine 102 to conditions requiring observation or intervention/recovery.

[0092] Scan communications function 1104 provides a parallel data path between the functional logic of a chip and the scan function. Access operations can be performed while the chip clocks are running and the system is operating; the scan communications function 1104 takes advantage of this to allow communication with an operating chip or system.

[0093] A clock tree 1114 receives a TCK SCAN CLOCKS input from Access 114. Clock tree 1114 also outputs chip clocks. A semicustom LBIST/SCAN interface 1116 optionally is used to organize the chip scan rings into functional groups, such as level-sensitive scan design (LSSD) rings, and BIST channels. Interface 1116 is coupled between JTAG scan 1102 of Access 114 and functional chip logic 1118.

[0094] The new instruction of the preferred embodiment, Scan Communications Read-Immediate, added to the design of the Access 114 JTAG scan-cohtroller, facilitates the design of the new I²C-to-JTAG interface function.

[0095] Before design of new instruction, Scan Communications Read-Immediate, reading a chip register required two steps: Step 1: execute Access scan-controller command “Scan Communications Read” (hex code ‘17’) to fetch contents of target chip reg, and load contents into Access Scan Communications Data Reg 1104. Step 2: execute Access scan-controller command “Scan-Out” (hex code ‘12’) to read out contents of Access Scan Communications Data Reg 1104. This two-step process was designed to accommodate existing software and hardware.

[0096] With the new Scan Communications Read-Immediate command, steps 1 and 2 combine into a single step: execute Access scan-controller command “Scan Communications Read-Immediate” (hex code ‘14’) to fetch contents of target chip reg 1120, and load contents into Access Scan Communications Data Register 1104, then immediately read out contents of Access Scan Communications Data Register 1104.

[0097] If the I²C-to-JTAG interface function was forced to use the original two-step process, it would need to attempt to execute the two steps in one clock cycle (one of its own I²C clock cycles). Since the I²C clock cycle can vary with respect to other system clocks, it cannot be guaranteed that both steps would successfully complete. By reducing the process to one step, it can now be guaranteed that the operation will complete in one clock cycle.

[0098] Operation of interconnection apparatus 100 and the I²C state machine 102 may be understood from the following examples.

[0099] A 64-bit register read/write operation begins with the start byte address (I²C slave base addr), optionally followed by up to 3 bytes of register read/write address (LSByte, high-order bit first). One implementation defines register read/write addresses that are eight byte aligned. A write must start with all 3 bytes of the register read/write address; a read may use a previously written address or modify one, two, or all three bytes (unless CRC checking is enabled) of the address before the restart/read byte. I²C slave implements a 24 bit register read/write address (23 down to 0, 0=LSB). Access/JTAG defines the LSB as a parity bit. The remaining 23 bits (23 down to 1) represent a byte-aligned address. The register read/write transfers are always 8-bytes wide, but each chip usually architects registers of varying widths that may not necessarily be aligned on 8-byte boundaries. The specific alignment of data within the I²C register read/write data field is chip implementation dependent. If a stopbit is received at this point only the portion of the address written will be altered, no other activity is initiated.

[0100] For a write operation, data for the write operation follows, starting with the fourth byte (LSByte, high-order bit first). A stop or overflow condition following one or more data bytes kicks off the register read/write operation, the register read/write address is not auto-incremented. An overflow/underflow occurs when more than 8 bytes of data are written/read. As an option to this design, the register read/write address could be auto-incremented to write/read successive register read/write addresses for writes/reads of more than 8-bytes. Writing more than 8 bytes of data will result in the data at the same register read/write address being overwritten. Writing less than 8 bytes of data will result in the register read/write address being written with a full 8 bytes, the most significant bytes of data will be written with whatever was left in the register read/write data IO buffer from the previous operation. With the CRC Checking enabled, the slave will not acknowledge the 9th (CRC) byte during a write to prevent from overwriting a good data transfer.

[0101] For a read operation, a restart (a stop followed by a start) is then issued on the I²C interface with the R/W bit=‘1’. This triggers a register read to be kicked off inside of the I²C hardware. The dataflow then reverses and the slave returns one data byte for each acknowledge (LSByte first). The register read/write address is not auto-incremented. If greater than 8 bytes are read, the data will be repeated starting with LSByte.

[0102] The non-register TAP command format is identified by the reserved register read/write addr (23:12)=x‘524’ (this address is relocatable). There are eight modes of operation, selected by the value of Tap Cmd bits 10:8. Bit 11 is reserved for future use. In the primitive TAP command (TapCmd Addr(11:8)=“0000”) format, the LSByte of the register read/write address is interpreted as a TAP command causing bits to be shifted out to the TAP port on TMS or TDI and capturing TDO. this enables the I²C interface 104 to perform any action supported by the JTAG logic. A stop or overflow condition kicks off the BCR with its current value for a Write operation and an overflow condition. Stop or Start with R/W Address bit set to 1 kicks off the BCR with its current value for a Read operation. Writing or reading more than “BCR_value mod 8” (+1 if remainder is non-zero) bytes of data causes a BCR re-load to continue the data stream (i.e. Write/Read successive bytes in Scan Ring). With CRC checking enabled, all reads/write primitive and register read/write are suppressed unless the CRC byte is correctly transmitted.

[0103] Tap command example: 64 bit+bit ring register

[0104] read/write out: (CRC disabled).

[0105] The following delineates the sequence of I²C Commands needed to perform a Primitive 64-Bit SCAN Out of an Internal Scan Ring followed by 1-bit Scan Out:

[0106] 1. Load Primitive Command: Instruct Slave to Bring Tap State Machine first to Test Logic Reset and then to Shift-IR to scan in an instruction.

[0107] I²C Write Start w/R/W Bit=0, Length=5 Bytes, STOP

[0108] 2. Load Primitive Command and Instruction Data:

[0109] Instruct Slave to Scan the following into the Tap Controller Instruction Register: OF 80 00 41. This is a SCAN Out of the Internal Ring, Then take Tap S/M to Exit1-IR.

[0110] I²C Write Start w/R/W Bit=0), Length=7 Bytes, STOP

[0111] 3. Load Primitive Command: Instruct Slave to Sequence Tap State Machine to Shift-DR (from Exit1-IR).

[0112] I²C Write Start w/R/W Bit=0, Length=4 Bytes, STOP

[0113] 4. Load Primitive Cmd: Instruct Slave to initiate 64 TCK Pulses with TMS=0 for all and to hold Tap S/M in Shift-DR.

[0114] I²C Write Start Cmd: Instruct Slave to initiate 64 TCK Pulses with TMS=0 for all and to hold Tap S/M in Shift-DR

[0115] 5. Get Return Data for Scan Out Command - - - TMS is 0's, Leave Tap S/M in Shift-DR.

[0116] I²C Read Restart w/R/W Bit=1), Length=8 Bytes, STOP

[0117] 6. Load Next Primitive command: Instruct Slave to initiate 1 TCK Pulse with TMS=1 to kick Tap S/M to exit1-DR after 1-bit SCAN

[0118] I²C Write Start w/R/W Bit=0) Length=3 Bytes, STOP

[0119] 7. Get Return Data for Scan Out Command (1 Bit) - - - Kick Tap S/M to Exit1-DR

[0120] I²C Read Restart w/R/W Bit=1), Length=1 Byte, STOP

[0121] 8. Load Next Primitive Command: Instruct Slave to Bring Tap State Machine to Test Logic Reset State

[0122] I²C Write Start w/R/W Bit=0), Length=4 Bytes, STOP

[0123] Tap Command Example: 2.5 Byte Register WRITE:

[0124] The following delineates the sequence of I²C Commands needed to SCAN in 2.5 Bytes (20 Bits) of data into the internal Scan Ring (NOTE: Resulting SCAN in data will be A EF BA hex).

[0125] 1. Load Primitive Command: Instruct Slave to Bring Tap State Machine first to Test Logic Reset and then to Shift-IR to scan in an instruction

[0126] I²C Write Start w/R/W Bit=0, Length=5 Bytes, STOP

[0127] 2. Load Primitive Command and Instruction Data: Instruct Slave to Scan the following into the Tap Controller Instruction Register: OF 80 00 41. This is a SCAN Out of the Internal Ring, Then take Tap S/M to Exit1-IR.

[0128] I²C Write Start w/R/W Bit=0), Length=7 Bytes, STOP

[0129] 3. Load Primitive Command: Instruct Slave to Sequence Tap State Machine to Shift-DR (from Exit1-IR).

[0130] I²C Write Start w/R/W Bit=0, Length=4 Bytes, STOP

[0131] 4. Load Primitive Cmd: Instruct Slave to initiate a 2-Byte SCAN-IN consisting of 2 series of 8 TCK Pulses with TMS=0 for all and to leave S/M in Shift-DR

[0132] I²C Write Start w/R/W Bit=0), Length=5 Bytes, STOP

[0133] 5. Load Primitive Cmd: Finish the 2.5 Byte SCAN-IN by scanning in the last 4 bits. The will be 4 TCK Pulses with TMS=0 for all but last TCK. The last TCK with TMS=1 will kick TAP S/M to Exit1-DR.

[0134] I²C Write Start w/R/W Bit=0), Length=4 Bytes, STOP

[0135] 6. Load Next Primitive Command: Instruct Slave to Bring Tap State Machine to Test Logic Reset State

[0136] I²C Write Start w/R/W Bit=0), Length=4 Bytes, STOP

[0137] Null TAP Command (TapCmd Addr(11:8)=“0001”)

[0138] JTAG activity on TCK/TMS/TDI is suppressed. This mode is intended, for example, to read back IR status information immediately following a Tap Cmd sequence which scans a new command into the IR.

[0139] An I²C write to the SSR Data (IO Buffer) has no effect. An I²C read of the SSR Data will return the most recent JTAG/TDO data scanned out.

[0140] Tap Command Example: Reading IR Status Immediately After Scanning in an Instruction:

[0141] 1. Load Primitive Command: Instruct Slave to Bring Tap State Machine first to Test Logic Reset and then to Shift-IR to scan in an instruction.

[0142] I²C Write Start w/R/W Bit=0, Length=5 Bytes, STOP

[0143] 2. Load Primitive Command and Instruction Data: Instruct Slave to Scan the following into the Tap Controller Instruction Register: OF 80 00 41. This is a SCAN Out of the Internal Ring, Then take Tap S/M to Exit1-IR.

[0144] I²C Write Start w/R/W Bit=0), Length=7 Bytes, STOP

[0145] 3. Load Primitive Command: Instruct Slave to Read what was last SCANNED OUT of Scan Controller (This will be the IR-STATUS since an Instruction Register Scan was the last operation)

[0146] I²C Write Start w/R/W bit=0, Length=3 Bytes, STOP

[0147] 4. Get Return Data for Primitive Read Command - - - Return Data that was Scanned Out (represented by dashes below)

[0148] I²C Read Restart w/R/W Bit=1), Length=4 Bytes, STOP

[0149] 5. Load Next Primitive Command: Instruct Slave to Bring Tap State Machine to Test Logic Reset State

[0150] I²C Write Start w/R/W Bit=0), Length=4 bytes, STOP

[0151] Issue I²C stop sequence

[0152] Enable Attention Command (TapCmd Addr(11:8)=“0010”) I²C method of Enabling attention raised from access.

[0153] An I²C write to the SSR Data (IO Buffer) enables attention checking by I²C slave. JTAG activity is suppressed.

[0154] Note that when this sequence is written, the slave will then acknowledge Register read/write operations only when attention is not active. When Attention is active, only primitive Tap commands will be acknowledged with the standard I²C ack pulse.

[0155] Tap Command Example: Re-Enabling attention checking internally

[0156] 1. I²C Write Start w/R/W Bit=0), Length=4 Bytes, STOP

[0157] 3. Issue I²C Stop sequence

[0158] Disable. Attention Command (TapCmd Addr(11:8)=“0011”). I²C method of disabling attention raised from access.

[0159] An I²C write to the SSR Data (IO Buffer) disables attention checking by I²C slave.

[0160] Note that when this sequence is written the slave will acknowledge primitive commands as well as register read/write sequences even if Attention is active. This method is used for overriding issues such as machine check being active which would in turn cause an attention to be raised. This does not correct an attention being raised from an register read/write error and the data received after an register read/write error should be disregarded. By default attention is masked off.

[0161] Tap Command Example: Masking attention internally

[0162] 1. I²C Write Start w/R/W Bit 0), Length=4 Bytes, STOP

[0163] 3. Issue I²C Stop sequence

[0164] Primitive Command Example: Enabling CRC checking internally. This sequence of bytes turns on CRC Checking.

[0165] 1. I²C Write Start w/R/W Bit=0), Length=3 Bytes, STOP

[0166] 3. Issue I²C Stop sequence

[0167] Note: CRC checking will now be enabled until byte 2:45x and Byte 3:52x are sent to the slave.

[0168] Example: Performing a Register read using CRC

[0169] For this example one implementation of CRC uses: x⁸+x⁴+x³+x²+1 for 8-bit CRC accumulator.

[0170] For this example one implementation of CRC uses: x⁸+x⁴+x³+x²+1 for 8-bit CRC accumulator.

[0171] Write Primitive Decode to turn CRC Checking on

[0172] 1. I²C Write Start w/R/W Bit=0), Length=3 Bytes, STOP

[0173] 3. Issue I²C Stop sequence

[0174] (CRC_CHECKING is now enabled)

[0175] Send in the address to be read and the CRC byte for the slave address and the 3 byte address (59x in this ex.)

[0176] 1. I²C Write Start w/R/W Bit=0), Length=4 Bytes, STOP

[0177] 3. Issue I²C Stop sequence

[0178] (Register read/write address 800003 is stored in the slave)

[0179] Read as many bytes as you want until done, the CRC byte is calculated only on the data that is sent back on the I²C bus.

[0180] 1. I²C Write Start w/R/W Bit=1, Length=8 Bytes, STOP read Bytes 1-8 for this example. (variable length)

[0181] 2. Issue I²C Stop sequence

[0182] To obtain the CRC byte that was calculated on the last read operation, you need to transmit the primitive decode ‘5247’x along with ‘11’x as the CRC byte (if ‘03’x is sent in the don't care part of the command)

[0183] 1. I²C Write Start w/R/W Bit=0, Length=4 Bytes, STOP

[0184] 3. Issue I²C Stop sequence

[0185] (Register read/write address 800003 is stored in the slave)

[0186] After sending down the primitive decode for the CRC read, a read sequence can be performed to obtain the CRC for the Register read that was performed. Only one byte is valid so you should only read one byte or ignore the rest. The Master should no-ack (‘1’b) this byte so it is possible to perform this operation without causing a bus error.

[0187] 1. I²C Write Start w/R/W Bit=1), Length=1 Byte, STOP read Byte #1 for this example (only one byte is valid)

[0188] 2. Issue I²C Stop sequence

[0189] Note that the CRC byte should be sent through the previously calculated byte to zero out the register.

[0190] This sequence of bytes turns off CRC Checking.

[0191] 1. I²C Write Start w/R/W Bit=0. Length=3 Bytes, STOP

[0192] 3. Issue I²C Stop sequence

[0193] CRC Checking is now disabled for the next programmer.

[0194] While the present invention has been described with reference to the details of the embodiments of the invention shown in the drawing, these details are not intended to limit the scope of the invention as claimed in the appended claims.