TMS320F28032PNTR
Product Specifications
TMS320F28032PNTR
Texas Instruments — Power Management & Signal Chain
Product Overview
The TMS320F28032PNTR from Texas Instruments is a power management / signal chain IC delivering high efficiency, precision regulation, and robust protection. Texas Instruments (TI) is a global leader in analog ICs, power management solutions, and embedded processors.
Superb Automation partners with leading brands including Qorvo, TI, ADI, XILINX, NVIDIA, Intel, ST, MACOM, Renesas, and Coilcraft to provide complete BOM and supply-chain solutions.
Key Features
- High-efficiency power conversion with low quiescent current
- Wide input voltage range with precision output regulation
- Integrated over-current, over-temperature, and short-circuit protection
- Small footprint packaging for space-constrained designs
- AEC-Q100 qualified options available for automotive applications
- Flexible sequencing and soft-start control
Key Specifications
| Input Voltage | V |
| Output Voltage | V |
| Output Current | A |
| Switching Frequency | kHz |
| Efficiency | % |
| Quiescent Current | µA |
| Topology | — |
| Package | — |
| Operating Temp | °C |
| Protection | — |
Applications
Request Quote — In Stock, 100% New & Original, Full Warranty
TMS320F28032PNTR: a 60 MHz controller for power conversion
The TMS320F28032PNTR is a 32 bit real time microcontroller from the C28x family, running at 60 MHz with a single 3.3 V supply, 32 K words of embedded flash and 12 bit analog conversion on up to sixteen channels. It is ordered in the 80 pin low profile quad flat package at 12 mm square and rated from minus 40 to 125 C.
The part is built for control loops rather than for data processing. The instruction set handles 16 by 16 and 32 by 32 multiply and accumulate in one cycle, which is what a current loop at tens of kilohertz needs, and the enhanced PWM modules generate the complementary outputs with dead band that a half bridge requires.
Around that core sit the peripherals a motor drive or a power stage expects: a 12 bit converter with a sample and hold that can be triggered by the PWM, comparators that can trip the PWM without the CPU, enhanced capture for encoder inputs, a quadrature encoder interface, and serial ports including CAN, LIN, SPI, I2C and SCI.
Key data for the TMS320F28032PNTR
| Core | 32 bit C28x, 60 MHz, 16.67 ns cycle |
| Arithmetic | 16 by 16 and 32 by 32 multiply and accumulate in one cycle |
| Flash | 32 K words of embedded flash in eight 4 K sectors |
| RAM | Single access RAM with 1 K word OTP and boot ROM |
| Supply | Single 3.3 V rail, internal regulator for the core |
| Analog | 12 bit converter, up to 16 single ended channels, 0 to 3.3 V range |
| PWM | Enhanced PWM modules with dead band and trip zones |
| Capture | Enhanced capture modules and a quadrature encoder interface |
| Serial | CAN, LIN, SPI, I2C and SCI |
| Security | 128 bit key and lock on the flash |
| Package | 80 pin LQFP, 12.00 mm by 12.00 mm |
| Temperature | Minus 40 to 125 C on this order code |
| Ordering | TMS320F28032PNT, tray, nickel palladium gold finish |
Why the converter and the PWM are in the same block
A control loop is only as good as the moment the sample is taken. If the converter samples at a random point in the switching cycle, the current reading contains ripple and the loop has to be slowed down to ignore it. The converter in this part can be triggered by the PWM counter, at the middle of the on time, where the ripple current equals the average.
That single feature decides the achievable loop bandwidth more than the clock speed does. A 60 MHz core with synchronised sampling will outperform a faster core with an asynchronous converter, because the faster core is fighting noise that it created itself.
The trip zones are the second half of the arrangement. A comparator can force the PWM outputs into a safe state without the CPU, so an overcurrent event is handled in nanoseconds rather than in an interrupt. The CPU then reads what happened and decides whether to restart.
Thirty two K words of flash, and what fits in it
The flash is organised in eight 4 K sectors, which matters for a product that has to update code in the field: a boot loader in one sector can erase and write the application in the others. The security module protects the flash with a 128 bit key, so a competitor with physical access cannot read the code out.
Thirty two K words is enough for a field oriented control loop, a communication stack and a set of protections, and not enough for a graphical interface or a large logging buffer. A product that wants both uses the 64 K part in the same family or moves the logging to an external memory.
Code that is timing critical can be run from RAM, which is faster than flash at 60 MHz. The usual pattern is to copy the current loop into RAM at start up and leave the rest in flash, which keeps the loop deterministic without needing a bigger part.
Where it fits in a build
Motor drives, inverter stages, battery chargers, solar converters and appliance control. The 80 pin package with twelve analog inputs covers a three phase drive with two current shunts and a DC bus measurement without an external multiplexer.
These boards are usually built in volume and tested with a fixture that programs the flash and runs the drive at a low bus voltage. The MCU cross reference page covers how a replacement controller is compared on the analog front end and the PWM behaviour, and the PCBA test coverage strategy page sets out how the fixture coverage is decided for a board that has both power and logic on it.
The sourcing side of this part is covered on the NPI production launch checklist. For a controller that is programmed and tested on the line, that page covers what has to be in place before the first build.
Questions we get on this code
Can it run from 5 V? No. The supply is 3.3 V and the analog inputs are limited to that range. A 5 V sensor needs a divider or an external amplifier with a protected input.
How many PWM channels are available? Enough for two three phase inverters on the 80 pin package, with the dead band generated in hardware. The exact mapping of channels to pins is in the data sheet and changes between packages in the family.
Is the CAN controller the same as the one in the larger parts? It is the same module, with the same mailbox structure, so code moves across the family with little change.
What about the 125 C rating? It is the ambient rating of this order code, and at 60 MHz the device runs warm but not hot. The thermal calculation still has to include the regulator losses inside the package.