CABLE-SMBUS-3PIN Analog Devices Inc, CABLE-SMBUS-3PIN Datasheet - Page 20

• Manufacturer Part Number: CABLE-SMBUS-3PIN
• Description: CABLE SMBUS 3PIN
• Manufacturer: Analog Devices Inc

Specifications of CABLE-SMBUS-3PIN

• Rohs Status: RoHS non-compliant
• Accessory Type: SMBus Cable
• For Use With/related Products: EVALADM106x Boards

EVAL-ADM106x
.
Figure 28 four ADM1069 devices at addresses 98 9A 9C and 9E
As with working in offline mode devices can be toggled using the
device select drop-down menu in the Top level. When another
device is selected none of the other devices on the SMBus are reset.
This allows the user to program one device and allow this to run
while using the configuration tool to interact with another device.
COMMUNICATIONS STATUS
In all the windows in the software except the SE window, Pin names
and Top level there is a comms status area at the bottom right hand
corner of the window. In normal operation the Analog Devices
symbol will spin indicating a successful SMBus transaction.
However, if the comms are lost the red indicator will appear as
shown in figure 29 below. If the comms cable has become
disconnected, plugging it back in will resolve the problem with no
loss of data. (Parallel port operation only). However, the same
message will be displayed if there is a loss of power to the
ADM106x but it must be remembered that if the power to the
ADM106x is cycled the data that was last saved to EEPROM will
be uploaded to the software.
Figure 29. Lost Comms indicator
CHECKSUM INFORMATION
To verify data integrity, the ADM106x software reports the
checksum of the two EEPROM’s on board. The checksum window
is displayed in the bottom right corner of the Top Level screen in
online mode. It splits out the information into four, reporting a value
for :-
1.
The configuration Registers checksum which holds the
Rev. PrB | Page 20 of 38
The figure below shows how these values are reported:-
Figure 30. ADM1062 Top Level, software in offline mode
The values reported are directly out of EEPROM registers on
the device. The actual checksum calculation takes place when
the user selects <Copy Entire configuration to EEPROM> or
when saving to file when a dialog box will ask the user if they
want the controlling registers saved to EEPROM. The
configuration registers checksum will indicate the checksum
for the current configuration tool settings (input, output etc)
however the configuration EEPROM checksum, User
checksum and SE EEPROM are representations of what is
currently in the device (i.e. when power is first applied to the
device in its current configuration this is what will be present).
In offline mode the checksum window is not displayed.
PIN NAMES
The ADM106x provides the facility to rename the pins of the
device, thus altering them from their default, datasheet names.
This allows the user to have meaningful references to the inputs
and outputs in their own board design. For example, if the pin
VP1 was being used to supervise a 5V supply, the pin could be
2.
3.
4.
checksum of the current configuration in use
The Configuration EEPROM which is stored on the
device. While the configuration register checksum
will change as settings are modified within the
configuration tool the configuration EEPROM will
only change when the current configuration is copied
to the device.
The User EEPROM is 256 bytes of space accessible
via the SMBus where the user can store data.The User
EEPROM checksum reflects the current data in the
device and this will again only change when data is
copied from the configuration tool down to the
device. Even if the User EEPROM is modified in the
configuration tool via the Registers Tab and then
saved to file the checksum will still reflect the
contents of the device. The saved file will contain a
checksum which reflects this modified data.
The Sequencing Engine EEPROM (stores the
sequencing/monitoring configuration of the device)
will reflect the current SE program in the device and
will only change if a new SE program is copied to the
device. Again if changes are made and saved to a file
but not copied to the device then the displayed
checksum will not be modified even though the
appropriate checksum of the SE program in the
configuration tool will be saved in the file.
Preliminary Technical Data