AS1854/44/34/24
Akros Silicon, Inc.
6399 San Ignacio Avenue, Suite 250, San Jose, CA 95119 USA
408.746.9000 http://www.AkrosSilicon.com 34
To service the watchdog via hardware (a valid operation in
Software mode) the WDOG pin must be pulsed for at least
100ns (continuous pulse of either polarity after the 1st
edge). Correct platform usage is to service before the
watchdog timeout period expires.
Watchdog Timeout Period
At startup the watchdog timeout counter defaults to the
maximum period of 32 seconds. The current user
programmed value in the Watchdog Timeout register (07h)
is always used for watchdog timeouts. A value of FFh in
this register gives the maximum timeout of 32 seconds. A
value 01h sets the minimum period of 125ms. Note that
00h is reserved and is not to be used. Intervening values
are multiples of 125ms (e.g. a value of 04h = 500ms).
Watchdog Timeout
If the Watchdog times out, the following occur:
– The Watchdog Timeout bit in the History register
(05h) is set.
– If the Watchdog Interrupt mask bit is set (register 04h)
and interrupts are enabled, the Watchdog Timeout bit
in the Interrupt Status register (02h) is set and the
INTB pin is driven Low.
– If the Watchdog PGOOD mask bit is set (register
04h), a 10ms (min.) Low pulse is output at the
PGOOD pin. If coincident with other voltage fault
events the PGOOD output pulse could be extended.
– If the Watchdog Register Reset mask bit is NOT set
(register 04h), the AS1854/34 registers are reset. This
resets the Watchdog Timeout register value to 32
seconds. (Note that an independent PGOOD fault will
also reset the registers unless bit 4 in device control
register, Reg 06h, is set).
– If the Watchdog Register Reset mask bit is set
(register 04h), operation of the Watchdog timer is
automatically initialized, with the currently
programmed value, and restarted.
SW Mode Interrupt Operation
Interrupts are disabled after a device power on. The
Device Control register (06h) is used to enable (or disable)
interrupts at a global device level.
The Interrupt Mask (01h) and Interrupt Status (02h)
registers are used to enable alarms and service any
resulting alarms.
InterruptMasking
Positive masking is used; therefore a “1” indicates that the
specified fault or alarm will cause an interrupt. Interrupts
(except for watchdog timeout) are level-driven, thus if a
fault condition is active upon enabling it will immediately
generate an interrupt.
InterruptStatus
A read from the Interrupt Status register will return the
conditions which have caused an interrupt, and will
immediately clear all such pending interrupts. Note that
interrupts (except for watchdog timeout) are level driven,
so if a fault condition still exists upon interrupts being
cleared an interrupt will be re-asserted after a minimum off
time of 10µs.
I2C INTERFACE
The AS1854/34 provides a standard I2C compatible slave
interface that allows a host controller (master) to access
its single-byte registers. Note the requirement of
“Repeated Start” for I2C reads.
The Primary-side GPIO pin read/write or ADCIN pin
conversion read/write have a 10ms (maximum) pin-
to/from-register timing.
The AS1854/34 registers are summarized in Table 22 and
described in Table 23 through Table 38.
The I2C interface is active when the AS1854/34 is in
Software mode. There are four pins associated with the
I2C interface:
– SDIO: bi-directional serial data
– SCL: clock input
– INTB: interrupt output
– I2C_ADR: device address configuration
Start/Stop Timing
The master device initiates and terminates all I2C interface
operations by asserting Start and Stop conditions
respectively.
As shown in Figure 24, a START condition is specified
when the SDIO line transitions from High-to-Low while the
clock (SCL) is High. A STOP condition is specified when
SDIO transitions from Low-to-High while SCL is High.
Data Timing
As shown in Figure 23, data on the SDIO line may change
only when SCL is Low and must remain stable during the
High period of SCL. All address and data words are
serially transmitted as 8-bit words with the MSB sent first.
Acknowledge (ACK)
ACK and NACK are generated by the addressed device
that receives data on SDIO. After each byte is transmitted,
the receiving interface sends back an ACK to indicate the
byte was received. As shown in Figure 24, to generate an
ACK, the transmitter first releases the SDIO line (High)
during the Low period of the ACK clock cycle. The receiver
then pulls the SDIO line Low during the High period of the
clock cycle.
A NACK occurs when the receiver does NOT pull the
SDIO line Low during the High period of the clock cycle.