Skip to content

Add TI TPS51396A Step-Down Converter

Adding TPS51396A buck converter.

Datasheet: https://www.ti.com/lit/gpn/tps51396a

Symbol screenshot: image

Example usage: image

The new symbol violates - as many switching regulators - the KLC:

  • S4.2 Pins should be grouped by function

    • VIN power input is not on top, but on the left as in all voltage regulators.
    • VCC output is on the left. This may seem odd, but has good reasons: The VCC pin is not meant to be used as power source (though it could provide +5V 20mA), instead it is the basis for the voltage divider needed for the MODE pin. Putting VCC to the right would make otherwise simple schematics complicated and ugly, and/or require additional labels. See example screenshot...
    • BST (bootstrap) and FB (feedback) pins are inputs, but on the right side. Makes sense and seems to be standard for switching regulators.
  • S4.4 Pin electrical type should match pin function

    • KLC check script complains that VCC should be an power input pin. It is, in fact, a output pin for the internal reference voltage, e.g for the MODE pin voltage divider. Could rename the pin, but I think they should be named like in the datasheet?
  • S4.6 Hidden pins

    • NC pins are visible and marked as "passive". Datasheet says "Not connect. Can be connected to GND plane for better thermal achieved." This should be good reason to make them visible and accesible? I guess "passive" is the correct pin type because ERC would complain when connecting "not connected" pins to GND?

  • Remove the instructional content of this template
  • Provide a URL to a datasheet for the symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, provide link(s) as appropriate
  • Check the output of the automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.

Merge request reports