TPS549D22: SMB_ALRT control

Hi Carlo

     When the SMB_ALERT# is asserted, you can deassert it using the CLEAR_FAULTS command. The assertion is dependent on the faults.

Why do you want to control the SMB_ALERT#?

regards,

Gerold

Hi Gerold,

Our customer would like to verify their hardware design and make sure the interrupt can be asserted.What faults can assert the SMB_ALRT pin?

Regards,
Carlo

Hi Carlo,

Gerold will feedback to you on Monday.

Thanks,

Lishuang

Hello Gerold,

Do we have an update on this? Thanks.

Regards,
Carlo

Hi Kris,

According to our customer, the STATUS_VOUT and STATUS_IOUT are read-only. They change the test step and list as follows:

1. Disable WRITE_PROTECT
2. Adjust VOUT_MARGIN_HIGH/VOUT_MARGIN_LOW to trigger SMB_ALERT.
3. CLEAR FAULTS
4. Revert VOUT_MARGIN_HIGH/VOUT_MARGIN_LOW

Could you help to check the test steps?

Regards,
Carlo

Hi Carlo,

Yes, sorry if I was unclear. I did not mean they could set the STATUS_ registers directly, but that a condition that would trigger a flag in the STATUS registers would assert the SMB_ALERT#.

If they see SMB_ALERT assert when changing VOUT_MARGIN_HIGH or _LOW, have them check the STATUS_VOUT or STATUS_IOUT registers to check for an asserted bit. I expect something asserted in one of these two registers.