This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83822I: TI recommended power delivery network is poor - why was this recommended?

Part Number: DP83822I
Other Parts Discussed in Thread: TLK105

Hi,

I'm working on an EtherCAT design spin I inherited from another engineer which previously had the TLK105 PHY on board.  I'm in the process of migrating it to the DP83822 since I've gathered from other posts on e2e that the TLK105 is NRND, and the DP83822 also seems to offer some worthwhile enhancements.

In combing through the datasheets EVM docs, and layout guides, I keep encountering this combination of bypass caps on the part's power rails:

This particular snippet is from the "TLK1XX Design and Layout Guide" (SLVA531A).  To be blunt: this PDN leaves a lot to be desired.  In my view, a simplistic combination of caps spaced one decade apart in value like this is always bad practice with low-impedance MLCCs because of the large anti-resonant impedance peaks such a combination produces.  Furthermore, this kind of network contradicts specific design advice from TI given in several other design resource documents (e.g. SWPA222A "Power Delivery Network Analysis" or section 2.4 "Decoupling Capacitors" of SCAA082A).  I realize TI is a sprawling organization and probably not all of the engineers who author datasheets and app notes are aware of everything put out by the company as a whole, but I see this kind of bad advice given frequently and felt the need to question it.

Here a plot of impedance vs frequency for this recommended network (black trace, and horizontal black line shows the DP83822's target impedance):

First, some caveats: this is a pretty simple sim I threw together in a few minutes to illustrate my point, and it doesn't model the impedance of any power plane distributed capacitance.  I also had to make an assumption about the 10uF cap's inductance and ESR, but I think I'm reasonably close based on experience.  This said, there's a lot that could be done to improve this network.  As a quick example, I also modeled converting all three 0402 caps to .1uF parts (red trace) or to 1uF parts (green trace), which avoids the high-frequency resonances.  Arguably, the 3x .1uF network is better in almost all respects, unless TI was shooting for low Z at the three specific impedance minima shown in the graph, but that seems unlikely to me.  Adding some damping in the form of resistors or using controlled ESR ceramic caps would certainly help.  There's a lot more written about this subject from people like Brooks, Archambault, Bogatin, Ott, Ritchey, and other EMC / PCB layout gurus.

Can anyone at TI comment on why this specific network was recommended?  I realize the answer may come down to something like "it worked, it's inexpensive, and it passed EMI tests."  That might be fine for some, but I'm shooting for a higher standard of performance.  Of course one could pour an inordinate amount of time and effort into improving this single aspect of the design, and such efforts must always be balanced with performance yield, but based on experience I think this network could be improved significantly with minimal effort.

Thanks,

Josh

  • Hi Josh,

    This is good information for everyone to see that the decoupling network has quite a few nuances to consider when designing.

    The answer to your question of "why this network?" does come down to your assumption; it worked, it's inexpensive, and passed EMI tests.

    There are a few PDN strategies being used. We commonly see the 3x .1uF network, the spaced decade network, as well as a network where the maximum value cap is chosen per case size to reduce parasitic inductance.

    Yet in the design, characterization, qualification, and testing for EMI(all this happening concurrently), we must choose a network that is simple, robust, easily obtained for multiple ICs, and effective across a wide variety of PCB variants.

    I can only speak for Ethernet ICs at this point. The complexity of the devices, which results in a high complexity of characterization, plus the variability of customer specific applications, limits our freedom to make specific optimizations on a per device basis.

    If a customer sees an opportunity for improvement, we recommend that the design be thoroughly validated by the customer with the optimized PDN as it may cause the device to operate outside of our characterized data.

    Best Regards,
  • Thanks for the comments Rob - that makes sense and confirmed my suspicions as to the "why" of this network. I was planning to implement my own network but wanted to check with you guys first to ensure I didn't miss anything.