TMC4671 + TMC6200 Servo Drive: Architecture and Procurement Guide

Why this chipset keeps showing up in servo designs #

Field-oriented control (FOC) for BLDC and PMSM motors is unforgiving in real time. Running the current, velocity and position loops in software on a general-purpose MCU works for a lab demo, but it collapses the moment the MCU has to do anything else — communication, a display, safety checks. The TMC4671 + TMC6200 pairing from Analog Devices (originally TRINAMIC) is a purpose-built answer: one chip computes the control loop in hardware, the other drives the power stage. Add an STM32 as the system host and you have a compact, production-grade servo drive without writing a torque controller from scratch.

How the stack actually divides the work #

The clean part of this design is the strict separation between *computing* the loop and *driving* the bridge.

• STM32 host — Sets target speed, position or torque, runs the application logic, handles the UI, fieldbus or safety. It is not inside the control loop. Its job is to configure the TMC4671 once and then feed setpoints.
• TMC4671 — A hardware FOC engine. It carries eight delta-sigma ADC channels for motor current and voltage, accepts encoder and Hall feedback, and closes the full current/velocity/position loop in silicon. It supports BLDC, PMSM, stepper and voice-coil motors. Output is PWM toward the gate driver. Interfaces are SPI and UART. The orderable code stocked here is TMC4671-LA in a 76-pin QFN (10.5 × 6.5 mm, 0.4 mm pitch).
• TMC6200 — A 3-phase MOSFET gate driver that integrates the entire high-voltage section. It runs from 8 V to 60 V DC, drives external MOSFETs for coil currents up to 100 A, and carries three floating in-line current-sense amplifiers with programmable gain (5 / 10 / 20). Gate drive strength is programmable at 0.5 / 1 / 1.5 A. It offers SPI plus stand-alone operation, a charge pump for 100% duty cycle, break-before-make logic, and programmable short/overload detection with retry. Package is a 9 × 9 mm TQFP48.
• MOSFET bridge + motor — Six external MOSFETs and two or three sense resistors complete the power stage for a 12 V, 24 V or 48 V motor.

The feedback path is what makes the architecture tight: in-line current sense from the bridge and encoder/Hall position from the motor both return to the TMC4671, where the delta-sigma ADCs digitise them directly. In-line sensing is more resistant to PWM noise than low-side shunt measurement, which is exactly why the TMC6200's sense amps pair with the TMC4671's ADCs.

Selection dimensions that change the BOM #

The TMC4671 and TMC6200 are designed as a matched pair, but each has its own orderable code. TMC4671-LA and TMC6200-TA are the tray-packed versions; TMC6200-TA-T is the tape-and-reel variant for automated assembly.

A real-world pitfall: encoder alignment at power-up #

Engineers hitting this design for the first time often trip on initialization. In a published ADI/TRINAMIC forum case, an STM32 + TMC4671 + TMC6200 servo with a loaded shaft would sometimes "run away" during encoder/Hall alignment on power-up, and the team wanted to initialize only once and skip it afterwards because the alignment rotation disturbed the load.

The vendor position is clear: the encoder must be initialized every power-up, before closed-loop operation, because the controller has no memory of the commutation offset after a reset. The practical design takeaways:

• Plan an initialization routine that may rotate the shaft slightly; if the load cannot tolerate any movement at startup, use an absolute encoder or store the last commutation offset in non-volatile memory and validate it against the Hall pattern on each power-up.
• Do not assume you can skip alignment because the motor "hasn't moved." After any reset the FOC loop needs a known electrical angle.
• Treat the initialization as a documented commissioning step, not a firmware afterthought.

This is the kind of issue that decides whether a servo drive is demo-ready or field-ready, so it belongs in the sourcing conversation, not just the firmware one.

Sourcing and buyer risk checks #

For a two-chip servo core, the procurement discipline is the same as for any precision analog part:

• Confirm the exact order code. TMC4671-LA (QFN76) is not interchangeable with other TMC4671 variants; TMC6200-TA (tray) and TMC6200-TA-T (reel) differ only in packing, but mixing them on a line causes reel-vs-tray confusion.
• Verify date code and lot traceability, especially for industrial and robotics builds with long field life.
• Check grade and packing condition (MSL, moisture barrier, tray/reel) before order release.
• Watch the open market. Motor-driver and motion-control ICs are common targets for remarked or refurbished units. Require supplier documentation and, where volume justifies it, incoming inspection.
• Confirm availability per code. TMC4671-LA is listed in stock at LimChip; TMC6200 lead time and lot condition should be confirmed by RFQ, since it is sourced to order.

Practical RFQ notes #

Send the exact part number (TMC4671-LA and/or TMC6200-TA / TMC6200-TA-T), target quantity, acceptable date-code window, packing requirement (tray or reel) and shipment destination. If this is for an approved BOM, include the approved manufacturer and any substitution restrictions so the quote reflects your real constraints.

Conclusion #

The TMC4671 + TMC6200 combination is a mature, well-supported way to build a BLDC/PMSM servo drive: the TMC4671 closes the FOC loop in hardware, the TMC6200 drives the bridge with integrated in-line current sense, and an STM32 host supervises. The decisions that matter for buyers are the exact order codes, bus voltage and packing, plus a realistic plan for encoder alignment at power-up. Confirm those before committing to stock, and the servo core becomes the easy part of the design.

Sources:

• Analog Devices, TMC4671 product page and datasheet (hardware FOC servo controller, QFN76).
• TMC6200 datasheet and distributor highlights (8–60 V, ≤100 A external FETs, TQFP48, in-line current sense).
• Analog Devices EngineerZone / TRINAMIC forum: STM32 + TMC4671 + TMC6200 encoder initialization discussion.