ADM1064ACP

Super Sequencer with Voltage Readback ADC ADM1064 FEATURES FUNCTIONAL BLOCK DIAGRAM AUX1 AUX2 REFIN REFOUT REFGND ADM1064 MUX VX1 VX2 VX3 VX4 VX5 VREF 12-BIT SAR ADC SDA SCL A1 A0 SMBus INTERFACE EEPROM PDO1 DUALFUNCTION INPUTS CONFIGURABLE OUTPUT DRIVERS (LOGIC INPUTS OR SFDs) (HV CAPABLE OF DRIVING GATES OF N-FET) PDO4 CONFIGURABLE OUTPUT DRIVERS PDO7 (LV CAPABLE OF DRIVING LOGIC SIGNALS) PDO9 PDO2 PDO3 PDO5 PDO6 SEQUENCING ENGINE VP1 VP2 VP3 VP4 PROGRAMMABLE RESET GENERATORS (SFDs) VH AGND PDO8 PDO10 PDOGND VDD ARBITRATOR VCCP GND VDDCAP 04633-001 Complete supervisory and sequencing solution for up to 10 supplies 10 supply fault detectors enable supervision of supplies to 2.5V) Figure 30. Configuration Update Flow Diagram UPDATING THE SEQUENCING ENGINE Sequencing engine (SE) functions are not updated in the same way as regular configuration latches. The SE has its own dedicated 512-byte nonvolatile, electrically erasable, programmable, readonly memory (EEPROM) for storing state definitions, providing 63 individual states, each with a 64-bit word (one state is reserved). At power-up, the first state is loaded from the SE EEPROM into the engine itself. When the conditions of this state are met, the next state is loaded from the EEPROM into the engine, and so on. The loading of each new state takes approximately 10 μs. To alter a state, the required changes must be made directly to the EEPROM. RAM for each state does not exist. The relevant alterations must be made to the 64-bit word, which is then uploaded directly to the EEPROM. INTERNAL REGISTERS The ADM1064 contains a large number of data registers. The principal registers are the address pointer register and the configuration registers. The major differences between the EEPROM and other registers are as follows: • • • The first EEPROM is split into 16 (0 to 15) pages of 32 bytes each. Page 0 to Page 6, starting at Address 0xF800, hold the configuration data for the applications on the ADM1064 (such as the SFDs and PDOs). These EEPROM addresses are the same as the RAM register addresses, prefixed by F8. Page 7 is reserved. Page 8 to Page 15 are for customer use. Data can be downloaded from the EEPROM to the RAM in one of the following ways: • • Address Pointer Register The address pointer register contains the address that selects one of the other internal registers. When writing to the ADM1064, the first byte of data is always a register address that is written to the address pointer register. An EEPROM location must be blank before it can be written to. If it contains data, the data must first be erased. Writing to the EEPROM is slower than writing to the RAM. Writing to the EEPROM should be restricted because it has a limited write/cycle life of typically 10,000 write operations, due to the usual EEPROM wear-out mechanisms. At power-up, when Page 0 to Page 6 are downloaded By setting Bit 0 of the UDOWNLD register (0xD8), which performs a user download of Page 0 to Page 6 SERIAL BUS INTERFACE The configuration registers provide control and configuration for various operating parameters of the ADM1064. The ADM1064 is controlled via the serial system management bus (SMBus) and is connected to this bus as a slave device under the control of a master device. It takes approximately 1 ms after power-up for the ADM1064 to download from its EEPROM. Therefore, access to the ADM1064 is restricted until the download is complete. EEPROM Identifying the ADM1064 on the SMBus The ADM1064 has two 512-byte cells of nonvolatile EEPROM from Register Address 0xF800 to Register Address 0xFBFF. The EEPROM is used for permanent storage of data that is not lost when the ADM1064 is powered down. One EEPROM cell contains the configuration data of the device; the other contains the state definitions for the SE. Although referred to as read-only memory, the EEPROM can be written to, as well as read from, using the serial bus in exactly the same way as the other registers. The ADM1064 has a 7-bit serial bus slave address (see Table 10). The device is powered up with a default serial bus address. The five MSBs of the address are set to 01001; the two LSBs are determined by the logical states of Pin A1 and Pin A0. This allows the connection of four ADM1064s to one SMBus. Configuration Registers Table 10. Serial Bus Slave Address A1 Pin Low Low High High 1 A0 Pin Low High Low High Hex Address 0x48 0x4A 0x4C 0x4E 7-Bit Address 0100100x1 0100101x1 0100110x1 0100111x1 x = Read/Write bit. The address is shown only as the first 7 MSBs. Rev. C | Page 23 of 32 ADM1064 The device also has several identification registers (read-only) that can be read across the SMBus. Table 11 lists these registers with their values and functions. All other devices on the bus remain idle while the selected device waits for data to be read from or written to it. If the R/W bit is a 0, the master writes to the slave device. If the R/W bit is a 1, the master reads from the slave device. Table 11. Identification Register Values and Functions Name MANID Address 0xF4 Value 0x41 REVID MARK1 MARK2 0xF5 0xF6 0xF7 0x02 0x00 0x00 Step 2 Function Manufacturer ID for Analog Devices Silicon revision Software brand Software brand Data is sent over the serial bus in sequences of nine clock pulses: eight bits of data followed by an acknowledge bit from the slave device. Data transitions on the data line must occur during the low period of the clock signal and remain stable during the high period because a low-to-high transition when the clock is high could be interpreted as a stop signal. If the operation is a write operation, the first data byte after the slave address is a command byte. This command byte tells the slave device what to expect next. It may be an instruction telling the slave device to expect a block write, or it may be a register address that tells the slave where subsequent data is to be written. Because data can flow in only one direction, as defined by the R/W bit, sending a command to a slave device during a read operation is not possible. Before a read operation, it may be necessary to perform a write operation to tell the slave what sort of read operation to expect and/or the address from which data is to be read. General SMBus Timing Figure 31, Figure 32, and Figure 33 are timing diagrams for general read and write operations using the SMBus. The SMBus specification defines specific conditions for different types of read and write operations, which are discussed in the Write Operations and Read Operations sections. The general SMBus protocol operates as follows: Step 1 The master initiates data transfer by establishing a start condition, defined as a high-to-low transition on the serial data line SDA, while the serial clock-line SCL remains high. This indicates that a data stream follows. All slave peripherals connected to the serial bus respond to the start condition and shift in the next eight bits, consisting of a 7-bit slave address (MSB first) plus an R/W bit. This bit determines the direction of the data transfer, that is, whether data is written to or read from the slave device (0 = write, 1 = read). Step 3 When all data bytes have been read or written, stop conditions are established. In write mode, the master pulls the data line high during the 10th clock pulse to assert a stop condition. In read mode, the master device releases the SDA line during the low period before the ninth clock pulse, but the slave device does not pull it low. This is known as a no acknowledge (NACK). The master then takes the data line low during the low period before the 10th clock pulse, and then high during the 10th clock pulse to assert a stop condition. The peripheral whose address corresponds to the transmitted address responds by pulling the data line low during the low period before the ninth clock pulse, known as the acknowledge bit, and by holding it low during the high period of this clock pulse. 1 9 1 9 SCL 1 0 0 1 A1 A0 D7 R/W D6 D5 SDA (CONTINUED) D3 D2 D1 FRAME 2 COMMAND CODE 1 D7 9 D6 D5 D4 D3 D0 ACK. BY SLAVE FRAME 1 SLAVE ADDRESS SCL (CONTINUED) D4 ACK. BY SLAVE START BY MASTER D2 FRAME 3 DATA BYTE D1 D0 1 D7 ACK. BY SLAVE 9 D6 D5 D4 D2 FRAME N DATA BYTE Figure 31. General SMBus Write Timing Diagram Rev. C | Page 24 of 32 D3 D1 D0 ACK. BY SLAVE STOP BY MASTER 04633-036 0 SDA ADM1064 1 9 1 9 SCL 1 0 0 1 A1 A0 R/W D7 D6 D5 D4 D3 D2 D1 ACK. BY SLAVE START BY MASTER 1 SCL (CONTINUED) SDA (CONTINUED) D7 FRAME 1 SLAVE ADDRESS D6 D5 D4 D3 9 D2 FRAME 3 DATA BYTE D1 D0 ACK. BY MASTER D0 1 D7 FRAME 2 DATA BYTE D6 D5 ACK. BY MASTER D4 9 D3 D2 FRAME N DATA BYTE D1 D0 NO ACK. STOP BY MASTER Figure 32. General SMBus Read Timing Diagram tR tF t HD; STA t LO W SCL t HI G H t HD; STA t HD; DAT t SU; STA t SU; STO t SU; DAT t BUF P S S Figure 33. Serial Bus Timing Diagram Rev. C | Page 25 of 32 P 04633-038 SDA 04633-037 0 SDA ADM1064 • The ADM1064 contains volatile registers (RAM) and nonvolatile registers (EEPROM). User RAM occupies Address 0x00 to Address 0xDF; the EEPROM occupies Address 0xF800 to Address 0xFBFF. Data can be written to and read from both the RAM and the EEPROM as single data bytes. Data can be written only to unprogrammed EEPROM locations. To write new data to a programmed location, the location contents must first be erased. EEPROM erasure cannot be done at the byte level. The EEPROM is arranged as 32 pages of 32 bytes each, and an entire page must be erased. The master sends a command code telling the slave device to erase the page. The ADM1064 command code for a page erasure is 0xFE (1111 1110). Note that for a page erasure to take place, the page address must be given in the previous write word transaction (see the Write Byte/Word section). In addition, Bit 2 in the UPDCFG register (Address 0x90) must be set to 1. Page erasure is enabled by setting Bit 2 in the UPDCFG register (Address 0x90) to 1. If this bit is not set, page erasure cannot occur, even if the command byte (0xFE) is programmed across the SMBus. 1 S S W P In the ADM1064, the write byte/word protocol is used for three purposes: • 3 4 5 6 A RAM ADDRESS (0x00 TO 0xDF) A P To write a single byte of data to the RAM. In this case, the command byte is RAM Address 0x00 to RAM Address 0xDF, and the only data byte is the actual data, as shown in Figure 36. 1 2 3 4 5 6 7 8 RAM SLAVE W A S ADDRESS ADDRESS A DATA A P (0x00 TO 0xDF) Figure 36. Single Byte Write to the RAM 04633-039 2 SLAVE ADDRESS A The master device asserts a start condition on SDA. The master sends the 7-bit slave address followed by the write bit (low). 3. The addressed slave device asserts an ACK on SDA. 4. The master sends a command code. 5. The slave asserts an ACK on SDA. 6. The master sends a data byte. 7. The slave asserts an ACK on SDA. 8. The master sends a data byte or asserts a stop condition. 9. The slave asserts an ACK on SDA. 10. The master asserts a stop condition on SDA to end the transaction. To write a register address to the RAM for a subsequent single byte read from the same address, or for a block read or a block write starting at that address, as shown in Figure 34. 1 A Figure 34. Setting a RAM Address for Subsequent Read Rev. C | Page 26 of 32 04633-041 The master device asserts a start condition on SDA. The master sends the 7-bit slave address followed by the write bit (low). The addressed slave device asserts an acknowledge (ACK) on SDA. The master sends a command code. The slave asserts an ACK on SDA. The master asserts a stop condition on SDA, and the transaction ends. In the ADM1064, the send byte protocol is used for two purposes: • 6 1. 2. In a send byte operation, the master device sends a single command byte to a slave device, as follows: 4. 5. 6. 5 In a write byte/word operation, the master device sends a command byte and one or two data bytes to the slave device, as follows: Send Byte 3. W 4 COMMAND BYTE (0xFE) Write Byte/Word The ADM1064 uses the following SMBus write protocols. 1. 2. SLAVE ADDRESS 3 As soon as the ADM1064 receives the command byte, page erasure begins. The master device can send a stop command as soon as it sends the command byte. Page erasure takes approximately 20 ms. If the ADM1064 is accessed before erasure is complete, it responds with a no acknowledge (NACK). The SMBus specification defines several protocols for different types of read and write operations. The following abbreviations are used in Figure 34 to Figure 42: S = Start P = Stop R = Read W = Write A = Acknowledge A = No acknowledge 2 Figure 35. EEPROM Page Erasure WRITE OPERATIONS • • • • • • To erase a page of EEPROM memory. EEPROM memory can be written to only if it is unprogrammed. Before writing to one or more EEPROM memory locations that are already programmed, the page(s) containing those locations must first be erased. EEPROM memory is erased by writing a command byte. 04633-040 SMBus PROTOCOLS FOR RAM AND EEPROM ADM1064 1 2 3 4 5 7 8 6 EEPROM EEPROM SLAVE ADDRESS ADDRESS S ADDRESS W A A A P HIGH BYTE LOW BYTE (0xF8 TO 0xFB) (0x00 TO 0xFF) 7. 8. 9. 10. 1 S 2 3 SLAVE S ADDRESS W A 4 5 6 7 8 9 10 EEPROM EEPROM ADDRESS ADDRESS P A HIGH BYTE LOW BYTE A DATA A (0xF8 TO 0xFB) (0x00 TO 0xFF) 04633-043 2 4 5 6 8 7 9 10 Figure 39. Block Write to the EEPROM or RAM To write a single byte of data to the EEPROM. In this case, the command byte is the high byte of EEPROM Address 0xF8 to EEPROM Address 0xFB. The first data byte is the low byte of the EEPROM address, and the second data byte is the actual data, as shown in Figure 38. 1 3 SLAVE W A COMMAND 0xFC A BYTE A DATA A DATA A DATA A P ADDRESS (BLOCK WRITE) COUNT 1 2 N Figure 37. Setting an EEPROM Address Because a page consists of 32 bytes, only the three MSBs of the address low byte are important for page erasure. The lower five bits of the EEPROM address low byte specify the addresses within a page and are ignored during an erase operation. • The slave asserts an ACK on SDA. The master sends N data bytes. The slave asserts an ACK on SDA after each data byte. The master asserts a stop condition on SDA to end the transaction. Figure 38. Single Byte Write to the EEPROM Unlike some EEPROM devices that limit block writes to within a page boundary, there is no limitation on the start address when performing a block write to EEPROM, except when • • There must be at least N locations from the start address to the highest EEPROM address (0xFBFF) to avoid writing to invalid addresses. An address crosses a page boundary. In this case, both pages must be erased before programming. Note that the ADM1064 features a clock extend function for writes to EEPROM. Programming an EEPROM byte takes approximately 250 μs, which limits the SMBus clock for repeated or block write operations. The ADM1064 pulls SCL low and extends the clock pulse when it cannot accept any more data. Block Write READ OPERATIONS In a block write operation, the master device writes a block of data to a slave device. The start address for a block write must have been set previously. In the ADM1064, a send byte operation sets a RAM address, and a write byte/word operation sets an EEPROM address, as follows: The ADM1064 uses the following SMBus read protocols. 3. 4. 5. 6. The master device asserts a start condition on SDA. The master sends the 7-bit slave address followed by the write bit (low). The addressed slave device asserts an ACK on SDA. The master sends a command code that tells the slave device to expect a block write. The ADM1064 command code for a block write is 0xFC (1111 1100). The slave asserts ACK on SDA. The master sends a data byte that tells the slave device how many data bytes are being sent. The SMBus specification allows a maximum of 32 data bytes in a block write. Receive Byte In a receive byte operation, the master device receives a single byte from a slave device, as follows: 1. 2. 3. 4. 5. 6. The master device asserts a start condition on SDA. The master sends the 7-bit slave address followed by the read bit (high). The addressed slave device asserts an ACK on SDA. The master receives a data byte. The master asserts a NACK on SDA. The master asserts a stop condition on SDA, and the transaction ends. In the ADM1064, the receive byte protocol is used to read a single byte of data from a RAM or EEPROM location whose address has previously been set by a send byte or write byte/word operation, as shown in Figure 40. 1 2 S SLAVE ADDRESS R 3 4 5 6 A DATA A P 04633-045 1. 2. 04633-044 To set up a 2-byte EEPROM address for a subsequent read, write, block read, block write, or page erase. In this case, the command byte is the high byte of EEPROM Address 0xF8 to EEPROM Address 0xFB. The only data byte is the low byte of the EEPROM address, as shown in Figure 37. 04633-042 • Figure 40. Single Byte Read from the EEPROM or RAM Rev. C | Page 27 of 32 ADM1064 Block Read Error Correction In a block read operation, the master device reads a block of data from a slave device. The start address for a block read must have been set previously. In the ADM1064, this is done by a send byte operation to set a RAM address, or a write byte/word operation to set an EEPROM address. The block read operation itself consists of a send byte operation that sends a block read command to the slave, immediately followed by a repeated start and a read operation that reads out multiple data bytes, as follows: The ADM1064 provides the option of issuing a packet error correction (PEC) byte after a write to the RAM, a write to the EEPROM, a block write to the RAM/EEPROM, or a block read from the RAM/ EEPROM. This option enables the user to verify that the data received by or sent from the ADM1064 is correct. The PEC byte is an optional byte sent after the last data byte has been written to or read from the ADM1064. The protocol is the same as a block read for Step 1 to Step 12 and then proceeds as follows: 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 1 The master device asserts a start condition on SDA. The master sends the 7-bit slave address followed by the write bit (low). The addressed slave device asserts an ACK on SDA. The master sends a command code that tells the slave device to expect a block read. The ADM1064 command code for a block read is 0xFD (1111 1101). The slave asserts an ACK on SDA. The master asserts a repeat start condition on SDA. The master sends the 7-bit slave address followed by the read bit (high). The slave asserts an ACK on SDA. The ADM1064 sends a byte-count data byte that tells the master how many data bytes to expect. The ADM1064 always returns 32 data bytes (0x20), which is the maximum allowed by the SMBus Version 1.1 specification. The master asserts an ACK on SDA. The master receives 32 data bytes. The master asserts an ACK on SDA after each data byte. The master asserts a stop condition on SDA to end the transaction. 2 3 4 5 6 7 8 9 10 11 13. The ADM1063 issues a PEC byte to the master. The master checks the PEC byte and issues another block read if the PEC byte is incorrect. 14. A NACK is generated after the PEC byte to signal the end of the read. 15. The master asserts a stop condition on SDA to end the transaction. Note that the PEC byte is calculated using CRC-8. The frame check sequence (FCS) conforms to CRC-8 by the polynomial C(x) = x8 + x2 + x1 + 1 See the SMBus Version 1.1 specification for details. An example of a block read with the optional PEC byte is shown in Figure 42. 1 3 4 5 6 7 8 9 10 11 13 14 15 DATA 32 A PEC A P Figure 42. Block Read from the EEPROM or RAM with PEC SLAVE COMMAND 0xFD SLAVE BYTE DATA S ADDRESS W A (BLOCK READ) A S ADDRESS R A COUNT A A 1 04633-046 13 P 12 SLAVE SLAVE BYTE DATA COMMAND 0xFD A S ADDRESS W A (BLOCK READ) A S ADDRESS R A COUNT A 1 12 DATA A 32 2 Figure 41. Block Read from the EEPROM or RAM Rev. C | Page 28 of 32 04633-047 1. 2. ADM1064 OUTLINE DIMENSIONS 6.00 BSC SQ 0.60 MAX 0.60 MAX PIN 1 INDICATOR 31 30 PIN 1 INDICATOR TOP VIEW 0.50 BSC 5.75 BCS SQ 4.25 4.10 SQ 3.95 (BOT TOM VIEW) 21 20 10 11 0.25 MIN 4.50 REF 0.80 MAX 0.65 TYP 0.05 MAX 0.02 NOM SEATING PLANE 0.30 0.23 0.18 0.20 REF COPLANARITY 0.08 101306-A 1.00 0.85 0.80 1 EXPOSED PAD 0.50 0.40 0.30 12° MAX 40 COMPLIANT TO JEDEC STANDARDS MO-220-VJJD-2 Figure 43. 40-Lead Lead Frame Chip Scale Package [LFCSP_VQ] 6 mm × 6 mm Body, Very Thin Quad (CP-40-1) Dimensions shown in millimeters 0.75 0.60 0.45 1.20 MAX 9.00 BSC SQ 37 36 48 1 PIN 1 1.05 1.00 0.95 0.15 0.05 SEATING PLANE 0.20 0.09 7° 3.5° 0° 0.08 MAX COPLANARITY 7.00 BSC SQ TOP VIEW 0° MIN (PINS DOWN) 12 13 25 24 VIEW A 0.50 0.27 BSC 0.22 LEAD PITCH 0.17 VIEW A ROTATED 90° CCW COMPLIANT TO JEDEC STANDARDS MS-026ABC Figure 44. 48-Lead Thin Plastic Quad Flat Package [TQFP] (SU-48) Dimensions shown in millimeters ORDERING GUIDE Model ADM1064ACP ADM1064ACP-REEL ADM1064ACP-REEL7 ADM1064ACPZ 1 ADM1064ASU ADM1064ASU-REEL ADM1064ASU-REEL7 ADM1064ASUZ1 EVAL-ADM1064LFEBZ1 EVAL-ADM1064TQEBZ1 1 Temperature Range −40°C to +85°C −40°C to +85°C −40°C to +85°C −40°C to +85°C −40°C to +85°C −40°C to +85°C −40°C to +85°C −40°C to +85°C Package Description 40-Lead LFCSP_VQ 40-Lead LFCSP_VQ 40-Lead LFCSP_VQ 40-Lead LFCSP_VQ 48-Lead TQFP 48-Lead TQFP 48-Lead TQFP 48-Lead TQFP Evaluation Kit [LFCSP Version] Evaluation Kit [TQFP Version] Z = RoHS Compliant Part. Rev. C | Page 29 of 32 Package Option CP-40-1 CP-40-1 CP-40-1 CP-40-1 SU-48 SU-48 SU-48 SU-48 ADM1064 NOTES Rev. C | Page 30 of 32 ADM1064 NOTES Rev. C | Page 31 of 32 ADM1064 NOTES ©2004–2008 Analog Devices, Inc. All rights reserved. Trademarks and registered trademarks are the property of their respective owners. D04633-0-5/08(C) Rev. C | Page 32 of 32