PI6C110E
Clock Solution for 133 MHz
Celeron/Pentium II/III Processors
Consider the command code and the byte count bytes required as the first two bytes of any transfer. The command code is software
programmable via the controller, but will be specified as 0000 0000 in the clock specification. The byte count byte is the number of
additional bytes required for the transfer, not counting the command code and byte count bytes. Additionally, the byte count byte is
required to be a minimum of 1 byte and a maximum of 32 bytes to satisfy the above requirement. For example:
7. Clock Stretching: The clock device must not hold/stretch the SCLK or SDATA lines low for more than 10 mS. Clock stretching is
discouraged and should only be used as a last resort. Stretching the clock/data lines for longer than this time puts the device in an error/
time-out mode and may not be supported in all platforms. It is assumed that all data transfers can be completed as specified without
the use of clock/data stretching.
8. General Call: It is assumed that the clock driver will not have to respond to the general call.
9. Electrical Characteristics: All electrical characteristics must meet the standard mode specifications found in section 15
of the I2C specification.
A) Pull-Up Resistors: There is a 100k internal resistor pull-ups on the SDATA and SCLK inputs. Assume that the board designer
will use a single external pull-up resistor for each line and that these values are in the 5-6K Ohm range. Assume one I2C device
per DIMM (serial presence detect), one I2C controller, one clock driver plus one/two more I2C devices on the platform for capacitive
loading purposes.
B) Input Glitch Filters: Only fast mode I2C devices require input glitch filters to suppress bus noise. The clock driver is specified
as a standard mode device and is not required to support this feature.
10. PWRDWN#: If a clock driver is placed in Power down mode, the SDATA and SCLK inputs are Tri-Stated and the device must retain
all programming information.
For specific I2C information consult the Philips I2C Peripherals Data Handbook ICI2 (1996)
A transfer is considered valid after the acknowledge bit corresponding to the byte count is read by the controller. The serial controller
interface can be simplified by discarding the information in both the command code and the byte count bytes and simply reading all the
bytes that are sent to the clock driver after being addressed by the controller. It is expected that the controller will not provide more bytes
than the clock driver can handle.
etybtnuocetyBsetoN
BSMBSL
00000000.etybenotsaeltaevahtsuM.dewollatoN
00001000)cepsni0etybyltnerruc(retsigertcelesycneuqerfdnalanoitcnufrofataD
00000100)1etybneht,0etyb(atadfosetybowttsrifsdaeR
00001100)redroni2,1,0etyb(atadfosetybeerhttsrifsdaeR
00000010)redroni3,2,1,0etyb(atadfosetybruoftsrifsdaeR
00001010)redroni4,3,2,1,0etyb(atadfosetybeviftsrifsdaeR
00000110)redroni5,4,3,2,1,0etyb(atadfosetybxistsrifsdaeR
00001110)redroni6,5,4,3,2,1,0etyb(atadfosetybnevestsrifsdaeR
0100000023=detroppustnuocetyb.xaM