Electronic Components Datasheet Search
  English  ▼

Delete All
ON OFF
ALLDATASHEET.COM

X  

Preview PDF Download HTML

ADP1046AW Datasheet(PDF) 39 Page - Analog Devices

Part No. ADP1046AW
Description  Digital Controller for Isolated
Download  88 Pages
Scroll/Zoom Zoom In 100% Zoom Out
Maker  AD [Analog Devices]
Homepage  http://www.analog.com
Logo 

ADP1046AW Datasheet(HTML) 39 Page - Analog Devices

Zoom Inzoom in Zoom Outzoom out
 39 / 88 page
background image
Data Sheet
ADP1046AW
Rev. 0 | Page 39 of 88
GENERAL CALL SUPPORT
The ADP1046AW is capable of decoding and acknowledging a
general call address. The general call address is supported for
send, write, and read commands that use Address 0x00 as the
slave address. The I2C slave responds to both its own address
and to the general call address (0x00).
Note that all commands start with a slave address with the R/W
bit cleared (set to 0), followed by the command code. This is also
true when using the general call address to communicate with
the I2C slave device.
10-BIT ADDRESSING
The ADP1046AW does not support 10-bit addressing as defined
in the I2C specification.
FAST MODE
Fast mode (400 kB/sec) uses essentially the same mechanics
as the standard mode of operation; the electrical specifications
and timing are most affected. The I2C slave is capable of commu-
nicating with a master device operating in standard mode
(100 kB/sec) or fast mode.
REPEATED START CONDITION
In general, a repeated start condition is the absence of a stop
condition between two transfers. The two transfers can be of
any direction type, for example, a transmit followed by a receive
or a receive followed by a transmit. However, the ADP1046AW
I2C communication protocol uses the repeated start condition
only when performing a read access (read byte, read word, and
block read). Other uses of the repeated start condition are not
allowed.
ELECTRICAL SPECIFICATIONS
All logic complies with the electrical specifications outlined in the
Philips I2
C Bus Specification, Version 2.1, dated January 2000.
FAULT CONDITIONS
The I2C protocol provides a very comprehensive set of fault
conditions that are monitored during communication. These
communication faults are error conditions associated with the
data transfer mechanism of the I2C protocol and are explained
in the following sections.
TIMEOUT CONDITION
A timeout condition occurs if any single SCL clock pulse is held
low for longer than the tTIMEOUT, MIN of 25 ms. Upon detecting the
timeout condition, the I2C slave device has 10 ms to abort the
transfer, release the bus lines, and be ready to accept a new start
condition. The device initiating the timeout is required to hold
the SCL clock line low for a minimum of tTIMEOUT,MAX = 35 ms,
guaranteeing that the slave device is given enough time to reset
its communication protocol.
DATA TRANSMISSION FAULTS
Data transmission faults occur when two communicating
devices violate the I2C communication protocol.
Sending Too Few Bits
Transmission is interrupted by a start or stop condition before
a complete byte (eight bits) has been sent. Not supported; any
transmitted data is ignored.
Reading Too Few Bits
Transmission is interrupted by a start or stop condition before
a complete byte (eight bits) has been read. Not supported; any
received data is ignored.
Host Sends or Reads Too Few Bytes
If a host ends a packet with a stop condition before the required
bytes are sent/received, it is assumed that the host intended to
stop the transfer. Therefore, the I2C slave does not consider this
to be an error and takes no action, except to flush any remain-
ing bytes in the transmit FIFO.
Host Sends Too Many Bytes
If a host sends more bytes than are expected for the corre-
sponding command, the I2C slave considers this a data
transmission fault and responds as follows:
Issues a no acknowledge for all unexpected bytes as they
are received
Flushes and ignores the received command and data
Host Reads Too Many Bytes
If a host reads more bytes than are expected for the corre-
sponding command, the I2C slave considers this a data
transmission fault and sends all 1s (0xFF) as long as the host
continues to request data.
Device Busy
The I2C slave device is too busy to respond to a request from the
master device. Typically SCL clock stretching is involved until
the device is free to communicate.
DATA CONTENT FAULTS
Data content faults occur when data transmission is successful,
but the I2C slave device cannot process the data that is received
from the master device.
Improperly Set Read Bit in the Address Byte
All I2C commands start with a slave address with the R/W bit
cleared (set to 0), followed by the command code. If a host
starts an I2C transaction with R/W set in the address phase
(equivalent to an I2C read), the I2C slave considers this a data
content fault and responds as follows:
Acknowledges the address byte
Issues a no acknowledge for the command and data bytes
Sends all 1s (0xFF) as long as the host continues to
request data


Html Pages

1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53  54  55  56  57  58  59  60  61  62  63  64  65  66  67  68  69  70  71  72  73  74  75  76  77  78  79  80  81  82  83  84  85  86  87  88 


Datasheet Download




Link URL




Privacy Policy
ALLDATASHEET.COM
Does ALLDATASHEET help your business so far?  [ DONATE ]  

About Alldatasheet   |   Advertisement   |   Datasheet Upload   |   Contact us   |   Privacy Policy   |   Alldatasheet API   |   Link Exchange   |   Manufacturer List
All Rights Reserved© Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn