Post Go back to editing

AD4130-8 — IEXC/VBIAS behavior during falling common AVDD/IOVDD rail and POR

Category: Hardware

Subject: AD4130-8 — IEXC/VBIAS behavior during falling common AVDD/IOVDD rail and POR

I am using an AD4130-8 LFCSP in a high-impedance DC voltage measurement application.

AVSS = DGND = 0 V. AVDD and IOVDD are tied to the same nominal 3.3 V rail, so they rise and fall together.

AIN0 is connected to an approximately 9.44 MΩ / 10 kΩ passive divider, with 47 nF from AIN0 to AVSS. AIN1 is tied to AVSS.

During normal operation:

  • I_OUT0_n = OFF
  • I_OUT1_n = OFF
  • BURNOUT_n = OFF
  • VBIAS on AIN0/AIN1 = OFF
  • STBY_IEXC_EN = 0
  • STBY_VBIAS_EN = 0
  • STBY_BURNOUT_EN = 0
  • SPI is configured for 4-wire operation
  • FIFO is disabled
  • CONT_READ = 1
  • DIN is held LOW during normal continuous-read operation

I am trying to prove safe behavior during abrupt or slow loss of the common 3.3 V AVDD/IOVDD supply.

The datasheet states that a POR occurs when IOVDD or the digital LDO falls below its specified operating range, and that POR resets the user configuration registers. CONFIG_n, VBIAS_CONTROL and MISC reset to states in which IEXC, VBIAS, burnout and their standby-retention enables are OFF.

Could you please clarify the following:

  1. With CONT_READ = 1 and DIN held continuously LOW, is it guaranteed that no sequence of CS/SCLK activity can modify a configuration register or enable IEXC/VBIAS/burnout unless Continuous Read is first exited using one of the two documented mechanisms (0x42 while data-ready is low, or the 64-one software reset)?
  2. During a monotonic or abrupt fall of a common AVDD = IOVDD rail from 3.3 V toward 0 V, are IEXC0, IEXC1, VBIAS and burnout outputs guaranteed to remain in their programmed OFF states until POR/reset forces their default OFF states?
  3. Is there any interval during falling supply—particularly between the minimum specified operating voltage and POR assertion—in which the user configuration registers or the IEXC/VBIAS output controls can become indeterminate or briefly enable/glitch even though they were programmed OFF beforehand?
  4. Can you provide the guaranteed falling POR assertion threshold (min/max if available) and maximum POR assertion delay for IOVDD/digital-LDO undervoltage?
  5. When POR asserts, are the IEXC/VBIAS/burnout analog outputs forced OFF immediately/asynchronously, or only after the register-reset/initialization sequence completes? Does tRESET_DELAY have any relationship to analog-output disable timing, or is it only the delay before subsequent SPI access?

The reason for the question is that the external AIN0 node contains 47 nF. If an excitation or bias output could momentarily become active during brownout, that capacitor could retain voltage after AVDD falls and potentially challenge the AIN ≤ AVDD + 0.3 V absolute-maximum requirement.

I am specifically trying to determine whether the combination of safe programmed state + Continuous Read/DIN LOW + common AVDD/IOVDD POR makes that condition unreachable, or whether an external discharge/clamp is still required.

Thank you.

  • Hi  ,

    Below are some of the answers to your questions, but in any case,  could add some insights as well.

    With CONT_READ = 1 and DIN held continuously LOW, is it guaranteed that no sequence of CS/SCLK activity can modify a configuration register or enable IEXC/VBIAS/burnout unless Continuous Read is first exited using one of the two documented mechanisms (0x42 while data-ready is low, or the 64-one software reset)?

    1. Yes, configuration registers are not writable while continuous read mode is active, and the device cannot exit continuous read mode unless one of the two mechanisms you mentioned is used.

    During a monotonic or abrupt fall of a common AVDD = IOVDD rail from 3.3 V toward 0 V, are IEXC0, IEXC1, VBIAS and burnout outputs guaranteed to remain in their programmed OFF states until POR/reset forces their default OFF states?

    2. If IOVDD drops below the specified operating range, POR occurs. IEXC, VBIAS and burnout currents will retain to OFF since after POR, it will reset to default state.

    Is there any interval during falling supply—particularly between the minimum specified operating voltage and POR assertion—in which the user configuration registers or the IEXC/VBIAS output controls can become indeterminate or briefly enable/glitch even though they were programmed OFF beforehand?

    3. As long as the operating voltage is within the specified operating voltage, the device is expected to operate according to the datasheet specs, and IEXC/VBIAS control states will remain as programmed.

    Can you provide the guaranteed falling POR assertion threshold (min/max if available) and maximum POR assertion delay for IOVDD/digital-LDO undervoltage?

    4. The IOVVD's valid operating range is 1.71V to 3.6V. According to the datasheet, once it falls below the valid operating range, POR occurs and the datasheet does not give a guaranteed assertion threshold or assertion delay.

    When POR asserts, are the IEXC/VBIAS/burnout analog outputs forced OFF immediately/asynchronously, or only after the register-reset/initialization sequence completes? Does tRESET_DELAY have any relationship to analog-output disable timing, or is it only the delay before subsequent SPI access?

    5. As mentioned in number 2, POR reset these in their default OFF state, and this should happen as soon as the device is operating again. Since there is no characterization or documented behavior about something like brownout condition, an external discharge or clamp network could help solve this possible scenario.

    Thanks,
    Francis

  • Thanks, Francis. Your answers were very helpful and they resolved the Continuous Read / configuration-write portion of the question.

    The only remaining point I am trying to close is the interval after the common AVDD/IOVDD rail falls below the guaranteed operating range but before POR/reset has fully established the default OFF state.

    Since   was mentioned, could either of you clarify whether ADI has any internal characterization or design knowledge indicating that IEXC, VBIAS, or burnout currents cannot briefly enable/glitch during that brownout interval when they were programmed OFF before the supply fell?

    If that behavior is genuinely uncharacterized, that is also a useful answer for me — I would then treat it as requiring an external discharge/clamp or a hardware qualification test rather than continuing to look for a datasheet guarantee.

    Thank you again.

  • Hi  ,

    Unfortunately, this behavior has not been characterized.

    Thanks,
    Francis

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.