Contact Us

TMS5701114CPGEQQ1

Brand: Texas Instruments
Texas Instruments TMS5701114CPGEQQ1 is a power management component designed for general electronics and related applications. In stock at Superb Automation — request a quote for competitive pricing and fast delivery.
quote now

Product Specifications

TMS5701114CPGEQQ1 — Power Management & Signal Chain | Superb Automation

TMS5701114CPGEQQ1

Texas Instruments — Power Management & Signal Chain

Product Overview

The TMS5701114CPGEQQ1 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 VoltageV
Output VoltageV
Output CurrentA
Switching FrequencykHz
Efficiency%
Quiescent CurrentµA
Topology—
Package—
Operating Temp°C
Protection—

Applications

Industrial Automation Automotive Electronics Telecom Infrastructure Server & Data Center Power Medical Devices Consumer Electronics

Request Quote — In Stock, 100% New & Original, Full Warranty

TMS5701114CPGEQQ1: 180 MHz lockstep Cortex-R4F safety microcontroller, 144 pin QFP, C silicon revision

TMS5701114CPGEQQ1 is the C revision of the 180 MHz safety device in the 144 pin body, with its own JTAG identification and device identification codes in a LQFP body of 144 pins. Mechanically and electrically this is the LS1114 in the 144 pin QFP that the rest of the family uses: 1MB of ECC flash, 128K bytes of ECC RAM, 64K bytes of emulated EEPROM, two lockstep Cortex-R4F cores at up to 180 MHz, seven ePWM modules, two N2HET blocks and two 12 bit ADCs with 24 inputs. The C in the code is the silicon revision, and the revision history of the data sheet records that revision C carries its own JTAG identification and device identification codes.

Order code and package

Order codeTMS5701114CPGEQQ1
Coredual Cortex-R4F in lockstep, FPU, up to 180 MHz
PackageQFP, 144 pins, body code PGE
Flash1MB with ECC
RAM128K bytes with ECC
Emulated EEPROM64K bytes
PWMseven ePWM modules
Timerstwo N2HET blocks
ADCtwo MibADC, 24 inputs
Serialthree DCAN, three MibSPI, two SPI, LIN, SCI, I2C
Temperatureminus 40 to 125 C, automotive grade
DatasheetSPNS188B, revised February 2015

Electrical parameters that decide the application

Silicon revisionC, with its own JTAG ID and device identification code
Identificationreadable from the device, so a board can be checked for the revision it carries
Safetylockstep CPUs, ECC, parity on peripheral RAMs, BIST, error signalling module
DMA16 channels, 32 peripheral requests
Capture and encodersix eCAP, two eQEP
Interrupts128 channel vectored module
CRCtwo channel checker
ADC buffers64 per MibADC
General purpose I/Oup to 64 pins
ClockFMPLL with slip detector
GradeQ1 marking
Package thermal144 pin QFP, copper under the body required

Points to check before this part goes on a BOM

The revision is not cosmetic on a safety device. Each revision has an errata list, the firmware workarounds are tied to it, and a board built with a different revision than the one that was qualified is a change that has to be assessed. The C revision can be identified in circuit through its JTAG and device identification codes, which is how a returned board can be checked without trusting the label.

Where the earlier revision needed a workaround, moving to C can allow that code to be removed, but only after the change has been assessed. Removing a workaround that is still harmless is optional; removing one that also compensated for a board level timing margin is not. The errata list and the firmware change record have to be read together.

Two hundred and eighty eight kilobytes of program flash per megabyte is not the point; 1MB is, because the diagnostic library, the floating point code and a field update image all live in the same device. The 64K bytes of emulated EEPROM then holds calibration and fault history without borrowing space from the application.

The lockstep pair at 180 MHz has a real thermal cost. At 125 C ambient the junction is above that by the thermal resistance of the 144 pin QFP times the dissipation of two cores and the I/O ring, and the copper under the body is part of the specification. A board that passed at 25 C in the lab is not evidence for the top of the range.

Seven ePWM modules and two timer coprocessors allow several power stages on one device, and the trigger and sync resources between them have to be planned. Two converters starting on the same trigger produce interleaved results that look correct on a scope and are wrong in the buffer index, which is a class of bug that only appears under load.

These parts are bought for production and for spares, so traceability matters more than price. We check the marking, the revision, the date code and the dry pack seal on receipt, and we state the revision on the offer. A lot that cannot be traced to a distributor or to the original maker is not a lot we put on a safety board.

A revision change also touches the programming file, because the identification codes differ. A fixture that reads the device identification before programming will reject a lot with the wrong revision, which is the behaviour to want; a fixture that skips the check will program a file qualified against one revision into another and report a pass.

Where this order code fits

Production builds that have moved to the current silicon, safety controllers where the errata list of the earlier revision has required a firmware workaround that is no longer needed, and service or spares where the revision on the board has to match the file that was qualified. Boards comparing it with a neighbouring part start from our Supplier Quality Audit page, and boards replacing a part that has gone end of life start from the MCU Cross Reference page.

Questions buyers ask

How can I tell which revision a part is? From the order code and, in circuit, from the JTAG and device identification codes that revision C carries. The code on the package is the first check and the identification is the confirmation, which is what we use on a returned board.

Can I mix B and C revisions on one board? Electrically they are the same device, but the errata differ, so a mixed board carries two firmware assumptions. For a safety build the lot should be one revision, and the production file should state which one it was qualified against.

Is the C revision faster? No. The clock and the memory are unchanged. The revision changes the errata list and the identification codes, not the headline specification.

SUPERB holds and sources this Texas Instruments line for production and repair demand, quoted against the exact ordering string with date codes, packing and country of origin stated on the offer. When a line is moving, the Component Obsolescence Management page sets out the checks that keep a substitute from failing on the bench.