MFS5600AMBAFES datasheet(54/118 Pages) NXP

54 / 118 page

NXP Semiconductors

FS5600

Automotive buck regulator and controller with voltage monitors and watchdog timer

PGOODx is toggled, FLT_ERR_CNT incremented and the watchdog restarted. The state machine will return

to INIT_RUN state or deep fail-safe based on the watchdog fault impact settings (independent of PGOODx

behavior).

17.7 FS0B pin

The FS0B pin indicates to the system status of the various safety mechanisms being handled by the FS5600.

This includes indication of health of internal circuitry (via ABIST), a valid watchdog, valid SW1, SW2, VMON1,

VMON2, VMON3, and VMON4, valid ERRMON, valid FCCU, and monitoring of PGOOD1/2.

The FS0B pin is released high in the NORMAL state. It is asserted low in all other states.

The FS0B pin is internally held low when a valid VIN is present with EN1 and EN2 = Low. It is also asserted low

if the VIN pin has a disconnection, provided SW1IN pin is connected.

FS0B is a global pin, and can be pulled up to VIN if required in the system.

17.7.1 FS0B pin electrical specifications

All parameters are specified at TA = –40 °C to 125 °C, VIN = 12 V, and typical external component values,

unless otherwise noted. Typical values are specified at 25 °C, unless otherwise noted.

Parameter

Symbol

Min

Typ

Max

Unit

FS0B_VOH (10 kohm pullup to VDDIO)

FS0B_VOH —

—

VDDIO – 0.5

FS0B_VOL(10 kohm pullup to VDDIO)

FS0B_VOL

0.4

—

Table 46. FS0B pin electrical specifications

17.8 PGOOD1, PGOOD2, FS0B stuck at fault check

PGOOD1, PGOOD2, and FS0B pins are continually monitored by digital to catch 'stuck-at' faults. The output at

these pins is compared to the internal digital command in real time.

PGOOD1_STUCK_AT_1 = 1 indicates that PGOOD1 pin is stuck at 1.

PGOOD1_STUCK_AT_0 = 1 indicates that PGOOD1 pin is stuck at 0.

PGOOD2_STUCK_AT_1 = 1 indicates that PGOOD2 pin is stuck at 1.

PGOOD2_STUCK_AT_0 = 1 indicates that PGOOD2 pin is stuck at 0.

FS0B_STUCK_AT_1 = 1 indicates that FS0B pin is stuck at 1.

FS0B_STUCK_AT_0 = 1 indicates that FS0B pin is stuck at 0.

During ABIST, the PGOOD1, PGOOD2, and FS0B are to be checked to ensure they are at logic low. If any of

them is not at logic low during ABIST, the corresponding 'STUCK_AT_1' bit is set.

When the FS56 releases PGOOD1, PGOOD2 or FS0B high, it monitors the pin to ensure it is at logic high. If

not, the corresponding 'STUCK_AT_0' bit is set set.

Note: There is no state transition due to stuck-at-faults. The FS5600 only reports stuck at faults via the

corresponding I2C bits. System software should evaluate the status of these bits to control state transitions.

17.9 I2C robustness

17.9.1 I2C CRC verification

When this feature is enabled, a selectable CRC verification is performed on each I2C transaction.

FS5600

All information provided in this document is subject to legal disclaimers.

Product data sheet

Rev. 4 — 29 April 2024

54 / 118

MFS5600AMBAFES Datasheet(PDF) 54 Page - NXP Semiconductors

MFS5600AMBAFES Datasheet(HTML) 54 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL