Contact Us

CC2652R74T0RGZR

Brand: Texas Instruments
Texas Instruments CC2652R74T0RGZR is a power management component designed for AI Servers & Low-Altitude Economy (Drone and UAV) and related applications. In stock at Superb Automation — request a quote for competitive pricing and fast delivery.
quote now

Product Specifications

CC2652R74T0RGZR — Power Management & Signal Chain | Superb Automation

CC2652R74T0RGZR

Texas Instruments — Power Management & Signal Chain

Product Overview

The CC2652R74T0RGZR 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

CC2652R74T0RGZR: 704 KB of flash and parity checked SRAM in a multiprotocol part

CC2652R74T0RGZR is the 7 mm by 7 mm VQFN48 member of the CC2652R7 family, a multiprotocol 2.4 GHz wireless microcontroller with an Arm Cortex-M4F core at 48 MHz, 704 KB of flash and 144 KB of SRAM with parity. It runs Thread, Zigbee, Matter, Bluetooth 5.2 Low Energy, IEEE 802.15.4 and 6LoWPAN, and it can run two of them at once through the dynamic multiprotocol manager.

The RGZ suffix is the body and the T0R suffix is the reel and the product revision, and neither changes the radio. What does change between this part and the older CC2652R is memory: 704 KB of flash against 352 KB, and 144 KB of SRAM against 80 KB. That doubling is the reason a Matter device with an over the air image slot fits on one die, and it is the number to check first when a customer forwards a BOM that was written for the earlier part.

The values below come from SWRS253B, revised March 2023, and from the orderable addendum. Two of them decide whether a build works at temperature: the ambient window of minus 40 to plus 105 degrees, which is wider than the Bluetooth parts in the same family, and the 1.8 V to 3.8 V supply range with an on-chip buck converter.

Memory, parity and the Matter image slot

Parity on the SRAM is not a marketing line. A 2.4 GHz radio next to a switching supply produces single event upsets in SRAM at a low but non zero rate, and a parity error turns a silent wrong value into a trap the firmware can handle. In a building sensor that is a nuisance log entry. In a lock or a medical accessory it is the difference between a reset and a wrong decision. The 32 KB of additional SRAM that becomes available when parity is disabled is the trade a customer makes when the image needs the room more than the check.

A Matter image with a bootloader, a running slot and a download slot needs roughly three times the application size. With 704 KB of flash that arithmetic works for an application of about 200 KB, which is a comfortable size for a thermostat or a smart lock with a display. The same product on a 352 KB part needs an external flash for the download slot, and that is a BOM line plus a board change.

Functionmultiprotocol 2.4 GHz wireless microcontroller
CoreArm Cortex-M4F, 48 MHz
Flash704 KB program memory
ROM256 KB for protocols and library functions
SRAM144 KB ultra-low leakage with parity, plus 8 KB cache
Sensor controllerautonomous core with 4 KB SRAM
ProtocolsThread, Zigbee, Matter, Bluetooth 5.2 Low Energy, IEEE 802.15.4, 6LoWPAN, TI 15.4-Stack
Frequency band2360 MHz to 2500 MHz
Receiver sensitivityminus 104 dBm for Bluetooth Low Energy 125 kbps coded PHY
Output powerup to plus 5 dBm with temperature compensation
Receive current6.4 mA
Transmit current7.3 mA at 0 dBm, 9.7 mA at plus 5 dBm
Active current3.10 mA in CoreMark, 65 microamps per MHz
Standby current0.9 microamps with RTC and 144 KB retention
Shutdown current0.1 microamps, wake on pin
Supply range1.8 V to 3.8 V, on-chip buck converter
Analog12-bit ADC at 200 kSamples per second, 8 bit DAC, two comparators
Serialtwo UART, two synchronous serial, I2C, I2S
SecurityAES 128 and 256 bit, ECC and RSA accelerator, SHA2 up to SHA-512, TRNG
PackageVQFN48, RGZ, 7 mm by 7 mm, 31 GPIO
Ambient rangeminus 40 to plus 105 degrees Celsius

What 65 microamps per MHz means in a real duty cycle

The active current of 65 microamps per MHz is the figure that decides how long a wake window may be. At 48 MHz the core draws about 3.1 mA, so a 10 ms processing window costs about 31 microamp seconds. A sensor that wakes once a second and spends 10 ms awake therefore averages 31 microamps, which dominates the 0.9 microamp standby figure by a factor of thirty. The lesson is not to make the radio cheaper, it is to make the wake window shorter, and the sensor controller exists for exactly that: it can collect and threshold samples while the M4F stays asleep.

The receive current of 6.4 mA and the transmit current of 9.7 mA at plus 5 dBm are close enough that a router which receives most of the time is not much cheaper to run than one that transmits. In a mains powered router that is irrelevant. In a battery powered end device the receive window is the thing to shorten, which is what the 125 kbps coded PHY and its minus 104 dBm sensitivity buy: the same link closes at a lower transmit power, and the radio spends less time at 7.3 mA.

Multiprotocol in one image

The dynamic multiprotocol manager lets a Zigbee or Thread network run alongside Bluetooth Low Energy, with the radio switching between them. The advantage is a product that joins a mesh and also accepts a phone connection for commissioning, without a second radio and without a second certification. The cost is memory and a scheduler that has to be understood: both stacks live in RAM at the same time, and the 144 KB of SRAM is what makes that possible.

For a Matter product the important line is that the stack is qualified for the part and shipped in the SDK, so the application links against a tested image rather than a port. That is worth money at certification time, because a radio that behaves on the bench and fails a conformance test costs a reschedule, and the test house does not care that the datasheet promised the feature.

Thermal and supply notes for a sealed enclosure

The ambient window of minus 40 to plus 105 degrees is wider than most of the plastic that surrounds it. A sealed enclosure in a plant room can sit at 70 degrees ambient, and the part will run, but the crystal and the plastic housing become the limit rather than the silicon. The junction temperature rise at 3.1 mA in the RGZ body is small, so the practical constraint is the crystal tolerance over temperature, not self heating.

The on-chip buck converter accepts 1.8 V to 3.8 V, which covers a lithium cell and a 3.3 V rail without an external regulator, and it is why this part appears in products that run from a single cell for years. A board that already has a 3.3 V rail can still use the converter and take the efficiency, as long as the rail can supply the peak transmit current of about 10 mA plus margin.

Comparing it with the parts it replaces

Against the CC2652R, the differences that matter are flash and SRAM, and the body is the same 7 mm RGZ, so a board can take either part if the firmware fits. Against the CC2652P, which carries an integrated power amplifier, this part has the same core and the same memory but a lower maximum output, so the choice is made by link budget rather than by memory.

Against a CC2640R2F, this is a different class of part: more memory, a floating point core, multiprotocol support and a 105 degree window. A product that only needs Bluetooth and 128 KB of flash should not pay for the extra silicon. The MCU cross reference page is where we put that comparison in writing before a customer commits a board revision.

Where a build is waiting on a lead time, the honest answer is that the RGZ body is the one most often quoted long, because it shares a package with several family members. The component lead time solutions page sets out the three routes we use: buffer stock against a forecast, a second source that is electrically close, and a build that splits the board into two orders.

Ordering, carrier and incoming checks

The orderable row prints this string as active and in production, VQFN48 with 7 mm by 7 mm body, large tape and reel, NIPDAU lead finish, moisture level 3 at 260 degrees with a 168 hour floor life. The T0R part of the string is the product revision and the reel, and it is worth keeping on the purchase order: a row without it can be filled from a different reel size or an earlier revision.

Incoming inspection covers the label, the marking, the moisture indicator, and a radio check on a sample if the product is going to a certification house. The part has no user calibration, so a sample that draws 3.1 mA at 48 MHz but transmits at the wrong power is a sourcing problem rather than a process problem, and it is the one thing worth measuring on a new reel.

For a build that needs the MCU, the crystal, the matching network and the passives on one line, the one stop BOM sourcing route keeps them together, which shortens the critical path when the crystal is the item with the long lead time rather than the microcontroller.

Three questions buyers ask about this string

Does this part run Matter out of the box? The stack is in the SDK and qualified for the device, so the answer is yes for the supported configuration, and the memory arithmetic above is what decides whether an over the air slot fits beside it.

Is 105 degrees ambient real or a marketing figure? It is the printed ambient range in the recommended operating conditions, and it is the reason this part appears in outdoor enclosures where the Bluetooth only family at 85 degrees is not acceptable.

Can the same board take the CC2652R? Yes, the body is the same, and the firmware has to be rebuilt against the smaller memory map. A board that takes either part gives a purchasing team an alternative during an allocation, which is the cheapest kind of second source there is.