CC1312R74T0RGZR
Product Specifications
CC1312R74T0RGZR
Texas Instruments — Power Management & Signal Chain
Product Overview
The CC1312R74T0RGZR 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
CC1312R74T0RGZR: the 704 kilobyte member of the sub 1 GHz family
CC1312R74T0RGZR is a sub 1 GHz wireless microcontroller with 704 kilobytes of flash, 144 kilobytes of SRAM, a 48 MHz Cortex-M4F core and a radio that reaches minus 121 dBm in long range mode at 2.5 kbps. The RGZ suffix is the 7 mm by 7 mm VQFN48 body with 30 general purpose pins, on a 2500 piece reel.
The number that separates this part from its smaller siblings is the memory. 704 kilobytes of flash and 144 kilobytes of SRAM is enough for a full protocol stack, an application and an over the air update image with room to spare. A node that has to support Wi-SUN or a multiprotocol stack, keep a bootloader and still leave space for a year of field upgrades needs that much, and the 352 kilobyte parts do not have it.
The SRAM matters as much as the flash. A radio stack with a queue of packets, a cryptographic session and an application buffer will use 60 to 80 kilobytes before the application does anything clever, and 144 kilobytes leaves room for the application to hold a history, a display buffer or a file system.
The radio numbers and the thermal envelope
The output power is plus 14 dBm with temperature compensation, drawing 24.9 mA at that setting and 8.0 mA at 0 dBm. The receive current is 5.8 mA. Sensitivity is minus 121 dBm at 2.5 kbps, minus 110 dBm at 50 kbps in the 802.15.4 arrangement, and the blocking figure at 10 MHz is 88 dB with selectivity of 56 dB at 100 kHz.
The output power in boost mode reaches plus 14 dBm with the internal regulator at 1.95 V, and the document notes that the power amplifier is fed from an internal regulated rail, so the output does not vary with the supply voltage. That is a useful property for a battery product: the link budget does not shrink as the cell discharges.
The operating range is minus 40 to plus 105, which is narrower than the 125 degree parts and wider than a commercial part. That ceiling is set by the flash and the package rather than by the radio, and a product that needs 125 degrees has to look at the wider temperature members of the family.
| Function | sub 1 GHz wireless microcontroller |
| Core | Arm Cortex-M4F at 48 MHz |
| Flash | 704 kilobytes |
| SRAM | 144 kilobytes of ultra low leakage memory with parity |
| ROM | 256 kilobytes for protocols and drivers |
| Radio | 2-FSK, 4-FSK, GFSK, MSK, OOK and 802.15.4 |
| Sensitivity | minus 121 dBm at 2.5 kbps long range |
| Sensitivity, 802.15.4 | minus 110 dBm at 50 kbps at 868 MHz |
| Output power | plus 14 dBm with temperature compensation |
| Transmit current | 24.9 mA at plus 14 dBm, 8.0 mA at 0 dBm |
| Receive current | 5.8 mA |
| Standby current | 0.8 microamps with the clock running and RAM retained |
| Supply range | 1.8 V to 3.8 V |
| Security | AES 128 and 256, ECC and RSA accelerator, SHA2, true random generator |
| Package | VQFN, RGZ body, 48 pins, 7 mm by 7 mm, 30 general purpose pins |
| Carrier | 2500 pieces on a large reel |
| Operating range | minus 40 to plus 105 degrees Celsius |
Where 704 kilobytes is not an extravagance
A Wi-SUN stack is a large piece of software. It carries a full IPv6 stack, a mesh routing protocol, a security layer and a certificate store, and it does not fit comfortably in 352 kilobytes alongside an application. The 704 kilobyte part exists because that stack plus an application plus an update image is a real requirement in the metering market.
The over the air update is the second consumer. An update image is a copy of the application, and a device that has to hold both the running image and the incoming one needs twice the flash. Some parts solve that with an external flash chip, which adds a part, four pins and a failure mode. 704 kilobytes solves it inside the package.
The third is multiprotocol. The document lists a dynamic multiprotocol manager, which allows a device to run two stacks by time slicing the radio. That is a software trick that costs memory, and the larger part is what makes it comfortable rather than tight.
The security block is part of the offer
AES 128 and 256, an ECC and RSA public key accelerator, a SHA2 accelerator up to SHA-512 and a true random number generator are all on chip. On a metering product those are not optional: the meter has to authenticate to the network, sign its readings and store a key that cannot be extracted.
The value of a hardware accelerator is not just speed. A software AES implementation on a Cortex-M4 costs flash, costs cycles and is vulnerable to timing analysis. A hardware block does the same work in a fixed number of cycles and is not.
The key storage is the other half. The document describes the security enablers and the SDK describes how keys are held, and a product that keeps its key in plain flash has a security story that ends at the first physical attack. That is a system decision, and this part provides the primitives rather than the answer.
Our MCU cross reference page covers the wireless microcontroller families by memory and package, and the component allocation management page describes what we do when the large memory member of a family is the one on allocation.
Where the large memory part is the right answer
The document lists grid communications, smart meters, building automation and security, EV charging, solar micro inverters, HVAC, factory automation, fire safety and medical telemetry. The large memory part is chosen in the segments where the protocol is heavy and the product life is long.
Grid communications and metering are the obvious ones. A concentrator or a meter that speaks Wi-SUN, holds certificates and updates in the field needs the memory, and the 105 degree ceiling is acceptable inside a cabinet that is ventilated.
An EV charge point is the second, and there the multiprotocol capability matters. A charge point that speaks a local protocol to the vehicle and a wide area protocol to the operator is running two stacks, and the memory is what makes that possible without an external flash.
The 144 kilobytes of SRAM also changes how the application is written. A stack that runs in 36 kilobytes forces every buffer to be shared and every queue to be short, and the code that manages those buffers is where most field bugs live. With 144 kilobytes the application can hold a packet queue, a session state and a display buffer at the same time, and the firmware becomes simpler as well as more capable.
That simplification has a cost in current. SRAM retention in standby is part of the 0.8 microamp figure only because the memory is built for it, and a product that keeps a large buffer alive in standby still meets the budget. A product that has to keep nothing can drop into shutdown for 0.1 microamps, which is where a battery life of ten years becomes possible.
For a product that has to hold a certificate of its own, that difference is the one that decides which memory point is qualified, and it is worth confirming in the qualification record rather than assuming that the larger memory part inherits the smaller one's file.
Three questions buyers ask about this string
Is it the same package as the 352 kilobyte part? Same RGZ body and pinout, different memory. That is what makes a product family able to offer two memory options on one board.
Does it need an external flash for over the air update? No, the 704 kilobytes hold both images if the application is disciplined about size.
Why 105 degrees and not 125? The ceiling is set by the memory and the package. A 125 degree product needs a different family member.