SFFSAX5 December 2025 TCAN1476-Q1
4.1 TCAN1476-Q1 (VSON (14, DMT) Package)
Figure 4-1 shows the TCAN1476-Q1 pin diagram for the VSON (14, DMT) package. For a detailed description of the device pins, see the Pin Configuration and Functions section in the TCAN1476-Q1 datasheet.
Figure 4-1 Pin Diagram (VSON (14, DMT) Package)Table 4-2 Pin FMA for Device Pins Short-Circuited to Ground
| Pin Name | Pin No. | Description of Potential Failure Effects | Failure Effect Class |
|---|---|---|---|
| TXD1 | 1 | The CAN1 driver enters dominant timeout, disabling the driver. Data cannot be transmitted on the CAN1 bus. | B |
| GND1 | 2 | None. | D |
| VCC1 | 3 | The CAN1 transceiver becomes unpowered and a high system-level supply current potentially occurs. | B |
| RXD1 | 4 | By default, the RXD pin is high-side FET ON. With a pin short-circuit to ground, a direct path forms between supply and ground, causing high current flow. | A |
| TXD2 | 5 | The CAN2 driver enters dominant timeout, disabling the driver. Data cannot be transmitted on the CAN2 bus. | B |
| GND2 | 6 | None. | D |
| VCC2 | 7 | The CAN2 transceiver becomes unpowered and a high system-level supply current potentially occurs. | B |
| RXD2 | 8 | By default, the RXD pin is high-side FET ON. With a pin short-circuit to ground, a direct path forms between supply and ground, causing high current flow. | A |
| CANL2 | 9 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| CANH2 | 10 | The device cannot drive a dominant signal to the CAN2 bus, so communication on the CAN2 bus is not possible. | B |
| STB2 | 11 | The STB2 pin is stuck low, so the CAN2 transceiver is unable to enter low-power mode. | B |
| CANL1 | 12 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| CANH1 | 13 | The device cannot drive a dominant signal to the CAN1 bus, so communication on the CAN1 bus is not possible. | B |
| STB1 | 14 | The STB1 pin is stuck low, so the CAN1 transceiver is unable to enter low-power mode. | B |
| Thermal Pad | - | None. | D |
Table 4-3 Pin FMA for Device Pins Open-Circuited
| Pin Name | Pin No. | Description of Potential Failure Effects | Failure Effect Class |
|---|---|---|---|
| TXD1 | 1 | The TXD1 pin defaults high; the CAN1 driver is always recessive and unable to transmit data. | B |
| GND1 | 2 | The CAN1 transceiver is not powered. | B |
| VCC1 | 3 | The CAN1 transceiver is not powered. | B |
| RXD1 | 4 | There is no RXD1 pin connection to the MCU. The MCU is unable to read data from the CAN1 bus using the RXD1 pin. | B |
| TXD2 | 5 | The TXD2 pin defaults high; the CAN2 driver is always recessive and unable to transmit data. | B |
| GND2 | 6 | The CAN2 transceiver is not powered. | B |
| VCC2 | 7 | The CAN2 transceiver is not powered. | B |
| RXD2 | 8 | There is no RXD2 pin connection to the MCU. The MCU is unable to read data from the CAN2 bus using the RXD2 pin. | B |
| CANL2 | 9 | The device cannot drive a dominant signal on the CAN2 bus, so communication on the CAN2 bus is not possible. | B |
| CANH2 | 10 | The device cannot drive a dominant signal on the CAN2 bus, so communication on the CAN2 bus is not possible. | B |
| STB2 | 11 | The STB2 pin defaults high; the CAN2 transceiver is stuck in low-power mode. | B |
| CANL1 | 12 | The device cannot drive a dominant signal on the CAN1 bus, so communication on the CAN1 bus is not possible. | B |
| CANH1 | 13 | The device cannot drive a dominant signal on the CAN1 bus, so communication on the CAN1 bus is not possible. | B |
| STB1 | 14 | The STB1 pin defaults high; the CAN1 transceiver is stuck in low-power mode. | B |
| Thermal Pad | - | None. | D |
Table 4-4 Pin FMA for Device Pins Short-Circuited to Adjacent Pin
| Pin Name | Pin No. | Shorted to | Description of Potential Failure Effects | Failure Effect Class |
|---|---|---|---|---|
| TXD1 | 1 | GND1 | The CAN1 driver enters dominant timeout, disabling the driver. Data cannot be transmitted on the CAN1 bus. | B |
| GND1 | 2 | VCC1 | The CAN1 transceiver becomes unpowered, and high ICC current flow is possible. | B |
| VCC1 | 3 | RXD1 | The output of the RXD1 pin becomes stuck high. The MCU is unable to receive data from the CAN1 bus using the RXD1 pin. | B |
| RXD1 | 4 | TXD2 | The output of the RXD1 pin reflects the input to the TXD2 pin, a separate CAN channel. Information from the CAN1 bus is not received correctly by the MCU, or information from the MCU to the CAN2 bus is potentially disrupted, or both. | B |
| TXD2 | 5 | GND2 | The CAN2 driver enters dominant timeout, disabling the driver. Data cannot be transmitted on the CAN2 bus. | B |
| GND2 | 6 | VCC2 | The CAN2 transceiver becomes unpowered and a high system-level supply current potentially occurs. | B |
| RXD2 | 8 | CANL2 | The messages on the RXD2 pin are corrupted by the CANL2 pin. The reception of data from the CAN2 bus using the RXD2 pin is not possible. IOS current is potentially reached. | B |
| CANL2 | 9 | CANH2 | The CAN2 bus becomes stuck recessive and no communication is possible. IOS current is potentially reached when the CAN2 driver is transmitting. | B |
| CANH2 | 10 | STB2 | The CAN2 transceiver potentially turns off when a dominant signal is driven on the CAN2 bus. The device potentially does not enter or stay in the desired mode for the CAN2 bus. | B |
| STB2 | 11 | CANL1 | The CAN2 transceiver potentially turns off when the CAN1 bus is recessive. The device potentially does not enter or stay in the desired mode for the CAN2 bus. | B |
| CANL1 | 12 | CANH1 | The CAN1 bus becomes stuck recessive and no communication is possible. IOScurrent is potentially reached when the CAN1 driver is transmitting. | B |
| CANH1 | 13 | STB1 | The CAN1 transceiver potentially turns off when a dominant signal is driven on the CAN1 bus. The device potentially does not enter or stay in the desired mode for the CAN1 bus. | B |
Table 4-5 Pin FMA for Device Pins Short-Circuited to VCC
| Pin Name | Pin No. | Description of Potential Failure Effects | Failure Effect Class |
|---|---|---|---|
| TXD1 | 1 | The TXD1 pin becomes stuck high. The device is unable to transmit data on the CAN1 bus. | B |
| GND1 | 2 | The CAN1 transceiver becomes unpowered, and high ICC is possible. | B |
| VCC1 | 3 | None | D |
| RXD1 | 4 | The RXD1 pin becomes stuck high. The MCU is unable to read data from the CAN1 bus using the RXD1 pin. | B |
| TXD2 | 5 | The TXD2 pin becomes stuck high. The device is unable to transmit data on the CAN2 bus. | B |
| GND2 | 6 | The CAN2 transceiver becomes underpowered, and high ICC is possible. | B |
| VCC2 | 7 | None | D |
| RXD2 | 8 | The RXD2 pin becomes stuck high. The MCU is unable to read data from the CAN2 bus using the RXD2 pin. | B |
| CANL2 | 9 | The device cannot drive a dominant signal to the CAN2 bus, so no communication is possible. The CAN2 bus potentially becomes stuck recessive during the fault. | B |
| CANH2 | 10 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| STB2 | 11 | The STB2 pin is stuck high. The CAN2 transceiver becomes stuck in low-power mode. | B |
| CANL1 | 12 | The device cannot drive a dominant signal to the CAN1 bus, so no communication is possible. The CAN1 bus potentially becomes stuck recessive during the fault. | B |
| CANH1 | 13 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| STB1 | 14 | The STB1 pin is stuck high. The CAN1 transceiver becomes stuck in low-power mode. | B |
Table 4-6 Pin FMA for Device Pins Short-Circuited to VBAT
| Pin Name | Pin No. | Description of Potential Failure Effects | Failure Effect Class |
|---|---|---|---|
| TXD1 | 1 | An absolute maximum violation occurs. The device is potentially damaged. The device potentially cannot transmit data on the CAN1 bus. | A |
| GND1 | 2 | The device becomes unpowered. High IBAT current is possible. | B |
| VCC1 | 3 | An absolute maximum violation occurs. The device is potentially damaged. The CAN1 bus potentially cannot communicate. | A |
| RXD1 | 4 | An absolute maximum violation occurs. The device is potentially damaged. The MCU potentially cannot receive data from the CAN1 bus. | A |
| TXD2 | 5 | An absolute maximum violation occurs. The device is potentially damaged. The device potentially cannot transmit data on the CAN2 bus. | A |
| GND2 | 6 | The device becomes unpowered. High IBAT current is possible. | B |
| VCC2 | 7 | An absolute maximum violation occurs. The device is potentially damaged. The CAN1 bus potentially cannot communicate. | A |
| RXD2 | 8 | An absolute maximum violation occurs. The device is potentially damaged. The MCU potentially cannot receive data from the CAN2 bus. | A |
| CANL2 | 9 | The CAN2 bus becomes stuck recessive. No communication is possible. IOS current is potentially reached. | B |
| CANH2 | 10 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| STB2 | 11 | An absolute maximum violation occurs. The device is potentially damaged. The CAN2 transceiver becomes stuck in low-power mode. | A |
| CANL1 | 12 | The CAN2 bus becomes stuck recessive. No communication is possible. IOS current is potentially reached. | B |
| CANH1 | 13 | The VCANL(R) specification is violated. The EMC performance of the transceiver potentially degrades. | C |
| STB1 | 14 | An absolute maximum violation occurs. The device is potentially damaged. The CAN1 transceiver becomes stuck in low-power mode. | A |