Post Go back to editing

brown-out damage to AD9102

Thread Summary

The user experienced irreversible damage to the AD9102 during power supply collapse, likely due to latch-up or back-powering through SPI or clock lines. The solution involves adding powered-off isolation for SPI and clock lines, using supervisors for proper power sequencing, and improving decoupling and ground layout. The AD9102 Evaluation Board schematic provides a reference for implementing these safeguards.
AI Generated Content
Category: Hardware
Product Number: AD9102

I am working on hardware that uses an AD9102.  The microcontroller is ESP32-S3.

During bring-up of the prototype PCBs, I ran into problems with shorting of the power supply due to mistakes I made in design or population of downstream circuitry.  Briefly, the signal chain is AD9102 -> ADA4932 -> (single-ended output using only +OUT) -> unity-gain buffer -> transconductance amplifier with class AB booster in control loop.  Resistors from IOUTP to ground and IOUTN to ground are used to convert the current output signal to voltage prior to the ADA4932 FDA.  I am using an XLL536160 differential clock source for the AD9102.

The circuit power supply is a bipolar output +/-5V switched-mode module; the +5V rail feeds a linear 3.3V regulator that supplies the ESP32 and AD9102.  That power module is supplied with 12V from a bench supply.

What I've noticed is that when the downstream problem apparently shorts the power supply system, the AD9102 gets damaged, seemingly irreversibly.  I observed this on the first prototype PCB, where a different problem collapsed the power supply.  In denial, I tried to write this off as some kind of fluke.

On the current version of the board I'm working on, the power supply collapse led to loss of the output signal.  I tried reading back the registers after writing over SPI, but reading back returns 0x0000 in every case.  In probing the bus with a logic analyzer, I see the commands being sent; these look correct, but SDO shows all zeros, so this looks real.  I probed the clock lines CLKP and CLKN and the clock signal looks OK.  Prior to damage, the AD9102 and my firmware were working fine, but as I built out and tested downstream circuitry, this is where I ran into failure.  There certainly seems to be correlation between loss of output from the AD9102 and power supply collapse.


Seeing as how these parts are fairly expensive, a pain to manually solder, and this problem looks real, I would really like to keep this from happening again.  What is it about power supply collapse that is leading to damage of the AD9102?  Finally, what kind of safe guards can I add to my circuit for development to try to keep this from happening again?


  • Hi  ,

    Thanks for using AD9102.

    Based on your signal chain and the symptoms you described, the failure suggests latch-up or back-powering during a power supply collapse. Please see below for the breakdown:

    • What’s likely damaging the AD9102
      • Improper power sequencing or rapid rail collapse triggering latch-up
      • Back-powering through SPI or clock pins when the DAC is unpowered
      • Output compliance violations at IOUT pins during faults
      • Large transient currents through shared grounds during shorts.
        • Please refer again to "Winning the Battle Against Latchup in CMOS Analog Switches" for reference.
    • How to confirm on the bench
      • Scope power rails and I/O signals during a forced brown-out
      • Check if SPI/clock remain active after DVDD drops
      • Verify IOUT voltages stay within compliance limits
    • Safeguards to prevent damage
      • Add powered-off isolation for SPI and clock lines
      • Use supervisors for proper power sequencing and clock enable control.  Follow ADI’s AN‑932 power‑supply sequencing guidance.
      • Implement eFuse or hot-swap protection on supply rails
      • Add series resistors and clamp diodes at DAC outputs
      • Improve decoupling and ground layout to handle transients

    Thanks and kind regards,

    Alex

  • Hi Alex,

    Thank you for your detailed response, including the safeguards summary.  I have heard of this concept of latch-up, but have not run into this before, so it's very helpful that you confirmed that this is the most likely explanation.  I must confess, this feels like voodoo to me, just because I have not run into this problem before, and I never gave any thought to things like the importance of what order the power rails come up.

    I will read your references in detail. 

    As far as the SPI bus isolator, I'm getting the idea is that this is basically an electronic switch that connects the SPI lines from the uC to the AD9102 only when the AD9102 has power - so the AD9102 power is basically an "enable" that closes the switch for each line?  So this would prevent back-powering the AD9102 via SPI bus lines (like SCK) in the case that the AD9102 doesn't have enough power to operate, but the uC still can toggle SPI lines?

  • Hi  ,

    Yes, that’s exactly the idea. A powered-off isolation device (or bus switch) acts like an electronic gate for each SPI line. It only connects the microcontroller to the AD9102 when the AD9102’s supply is valid.
    This prevents the microcontroller from driving signals into the AD9102 when the DAC is unpowered or in brown-out, which would otherwise forward-bias the ESD diodes and back-power internal circuits.

    Typical implementations:

    • Analog switches or bus isolators on SCLK, MOSI, CS, and optionally MISO.
    • Enable pin tied to AD9102’s DVDD/CLKVDD power-good or a dedicated supervisor.

    You can cross reference your circuit to the schematic of the AD9102 Evaluation Board (found in the "Helpful Files" section).

    Thanks and kind regards,

    Alex

  • Hi Alex,

    Thank you for confirming my understanding of what the power-off isolation switch does.

    I looked at the AD9102 eval board schematic, and I see the block labeled level translation that implements the bus isolation during power-off state.

    I appreciate your help.