| Electronic Components Datasheet Search |
|
AD9542 Datasheet(PDF) 53 Page - Analog Devices |
|
|
|||||||||||||||||||||||||||||
AD9542 Datasheet(HTML) 53 Page - Analog Devices |
|
53 / 61 page ![]() Data Sheet AD9542 Rev. 0 | Page 53 of 61 Table 32. Example Conditional Processing Sequence Instruction Operation 0x00 to 0x7F A sequence of register transfer instructions that execute unconditionally 0xB1 Apply Condition 1 0x00 to 0x7F A sequence of register transfer instructions that execute only if the condition ID is 1 0xB2 Apply Condition 2 0xB3 Apply Condition 3 0x00 to 0x7F A sequence of register transfer instructions that execute only if the condition ID is 1, 2, or 3 0x91 Calibrate the system clock PLL 0xB0 Clear condition map 0x80 Input/output update 0xFF Terminate sequence Pause Instruction (0xFE) The EEPROM controller only recognizes the pause instruction during an upload sequence. Upon encountering a pause instruction, the EEPROM controller enters an idle state, but preserves the current value of the EEPROM address pointer. One use of the pause instruction is for saving multiple, yet distinct, values of the same AD9542 register, which is useful for sequencing power-up conditions. The pause instruction is also useful for executing an upload sequence requiring more space than is available in the EEPROM sequence registers in the EEPROM section of the register map (see the EEPROM Upload section). End of Data Instruction (0xFF) When the EEPROM controller encounters an end of data instruction during an upload sequence, it stores the instruction in EEPROM along with the computed checksum, clears the EEPROM address pointer, and then enters an idle state. When encountered during a download sequence, however, the EEPROM controller clears the EEPROM address pointer, verifies the checksum, and then enters an idle state. Note that during EEPROM downloads, condition instructions always execute unconditionally. MULTIDEVICE SUPPORT Multidevice support enables multiple AD9542 devices to share the contents of a single EEPROM. There are two levels of multidevice support. Level 1 supports a configuration where multiple AD9542 devices share a single EEPROM through a dedicated I 2C bus. Level 2 supports a configuration where multiple AD9542 devices share a single EEPROM connected to a common I 2C bus that includes other I2C master devices. Figure 51 and Figure 52 show the Level 1 and Level 2 configurations, respectively. SDA SCL CPU EEPROM SCL SDA SCL SDA SCL SDA AD9542 DEVICE 1 M1 M2 SCL SDA AD9542 DEVICE 2 M1 M2 SCL SDA 2 4 33 35 2 4 33 35 Figure 51. Level 1 Multidevice Configuration AD9542 DEVICE 1 M1 M2 SCL SDA AD9542 DEVICE 2 M1 M2 SCL SDA SDA SCL CPU SDA SCL EEPROM SCL SDA 2 4 33 35 2 4 33 35 Figure 52. Level 2 Multidevice Configuration Multidevice Bus Arbitration The EEPROM controller implements bus arbitration by continuously monitoring the SDA and SCL bus signals for start and stop conditions. The controller can determine whether the bus is idle or busy. If the bus is busy, the EEPROM controller delays its pending I 2C transfer until a stop condition indicates that the bus is available. Bus arbitration is essential in cases where two I 2C master devices simultaneously attempt an I 2C transfer. For example, if one I 2C master detects that SDA is Logic 0 when it is intended to be Logic 1, it assumes that another I 2C master is active and immedi- ately terminates its own attempt to transfer data. Similarly, if one I 2C master detects that SCL is Logic 0 prior to entering a start state, it assumes that another I 2C master is active and stalls its own attempt to drive the bus. In either case, the prevailing I 2C master completes its current transaction before releasing the bus. Because the postponed I 2C master continuously monitors the bus for a stop condition, it attempts to seize the bus and carry out the postponed transaction on detection of such a stop condition. The EEPROM controller includes an arbitration timer to optimize the bus arbitration process. Specifically, when the EEPROM controller postpones an I 2C transfer as a result of detecting bus contention, it starts the arbitration timer. If the EEPROM controller fails to detect a stop condition within 255 SCL cycles, it attempts to force another transaction. If the bus is still busy, the EEPROM controller restarts the arbitration timer, and the process continues until the EEPROM controller eventually completes the pending transaction. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| 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 Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |