CAN FD controller, transceiver or SBC: select the missing function

1. Draw the controller/physical-layer boundary first

The CAN controller handles framing, arbitration, bit timing and error handling; the transceiver converts between TXD/RXD logic and the CANH/CANL differential bus. Replacing a transceiver with a CAN FD-capable device does not give an MCU with a classical-CAN-only controller the ability to process CAN FD frames. Devices such as TCAN1042-Q1 and TCAN1044A-Q1 solve the electrical-interface problem, not a missing protocol controller.

TCAN4550-Q1 exposes its integrated CAN FD controller and transceiver to the processor over SPI, making it a candidate for port expansion or a host without CAN FD. TCAN1145-Q1 and TCAN1167-Q1 also have SPI, but their normal CAN data path still connects to an external controller through TXD/RXD. Label the CAN frame path and configuration-register path separately in the schematic review; the presence of SPI does not establish a SPI-to-CAN controller function.

2. Compare control, wake, power and isolation responsibilities

This is an architecture-role table, not a pin-replacement matrix. Two CAN FD devices can require different control signals, rails, software initialization and footprints. Choose the required function first, then check the exact orderable's pinout, electrical conditions and temperature limits; sorting only by maximum Mbps can hide the larger redesign risk.

Scroll wide tables horizontally; column headers remain visible within the table.

3. Translate Mbps into topology, timing and logic-level requirements

Budget the arbitration and data phases of CAN FD separately. Propagation delay, harness length, stubs, node loading, termination and controller sample points jointly determine margin; a transceiver's headline rate is not a vehicle-network guarantee. TI describes TCAN1044A-Q1 for CAN FD networks up to 5 Mbps, with up to 8 Mbps possible in simpler networks. A heavily branched topology needs waveform and error-rate validation rather than an assumed 8 Mbps operating point.

The TCAN1044AV-Q1 variant supplies VIO level translation in the TCAN1044A-Q1 family; its 1.7–5.5 V I/O conditions must not be applied to every A orderable. TCAN4550-Q1 also needs a SPI transfer budget: its maximum 18 MHz SPI clock is not the usable CAN payload throughput. Register commands, transmit/receive buffers, shared-SPI occupancy and interrupt latency all consume host service time. Validate worst-case frame bursts against the longest host service interval to prevent overflow.

4. WUF, WUP and SBC power are three different questions

TCAN1145-Q1 supports selective wake based on a wake-up frame, WUF, enabling partial networking with some nodes active and others asleep. Identifier, mask, data matching and configuration validity must be managed as system configuration, not merely as a WAKE-pin connection. The shared TCAN114x datasheet covers several devices: its watchdog and advanced bus-fault diagnostics belong to TCAN1144-Q1/TCAN1146-Q1, not TCAN1145-Q1.

The TCAN1167-Q1 datasheet specifies remote bus wake through WUP, a time-filtered dominant/recessive pattern, not identifier-filtered WUF selective wake. It is an SBC with a watchdog and LDO, but more integrated functions do not imply a superset of TCAN1145 wake behavior. If unrelated traffic must not wake the ECU, prove the WUF matching and network-management design rather than selecting TCAN1167 from a Selective Wake label in a parametric summary.

TCAN1167-Q1 has a recommended VSUP range of 5.5–28 V and an integrated 5 V LDO with 100 mA output capability under datasheet conditions. Section 5.6 specifies VCCOUT of 4.9–5.1 V at IL = 0–100 mA under stated VSUP, TXD and other test conditions. Do not extend that conditional specification to every supply and operating state, or interpret 100 mA as a total budget from which internal CAN current must automatically be subtracted. Section 7.3.2 states that available external current depends on CAN operation, temperature and bus faults; evaluate the actual load together with VSUP and thermal conditions. The LDO is off in sleep and VCCOUT requires a nearby 10 µF capacitor, so also verify startup inrush, fault loading and recovery after sleep power-off.

5. Redraw power and fault paths when isolation is required

ISO1042-Q1 integrates an isolation barrier and CAN transceiver, not an isolated power converter. Logic-side VCC1 and bus-side VCC2 sit on opposite sides of the barrier, with VCC2 specified for 4.5–5.5 V operation. A galvanically isolated system therefore also needs isolated-side power, spacing and return-path planning; a common ground connection across the barrier defeats the intended separation.

It supports CAN FD up to 5 Mbps but remains a physical-layer device, not an external-controller replacement. Verify isolation classification and package for the exact orderable rather than applying one basic/reinforced option to the whole family. Bus-fault voltage likewise describes CAN-pin tolerance under specified conditions, not a recommended supply input or a complete board-level surge solution. Validate protection components and isolated power together.

6. Turn part selection into repeatable bench acceptance

Acceptance should demonstrate ECU recovery under worst-case traffic, supply disturbances and sleep transitions, not just successful exchange of one frame between two boards. Record the following conditions together with bit timing, full device identifiers, harness and software versions so that a package or wake-policy change has an explicit retest scope.

• Confirm that the MCU controller supports the required CAN FD mode; for TCAN4550-Q1, budget the clock, SPI service, buffers and interrupt latency.
• Check TXD/RXD levels, VIO, mode pins and power-up defaults for the full orderable, explicitly separating TCAN1044A from AV.
• Validate arbitration and data phases with the target harness, longest stubs and full node loading; do not generalize a simple-network 8 Mbps result.
• Test ordinary WUP, matching/nonmatching TCAN1145 WUF, local wake and recovery after configuration loss; record which power domains actually wake.
• For TCAN1167, measure VCCOUT external-load margin during normal operation and bus faults, then verify MCU restart and watchdog initialization after sleep power-off.
• Exercise undervoltage, unpowered nodes, TXD stuck dominant and bus recovery; design supply protection independently of bus-fault voltage ratings.
• For isolation, validate isolated power, PCB spacing, protection networks and fault returns, not only ISO1042 communication connectivity.

Frequently asked questions

Related parts and complete OPNs

Continue reading