CC1310F128RGZR
Product Specifications
CC1310F128RGZR
Texas Instruments — Power Management & Signal Chain
Product Overview
The CC1310F128RGZR 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
CC1310F128RGZR: the 7 mm body with thirty general purpose pins
CC1310F128RGZR is a sub 1 GHz wireless microcontroller with 128 kilobytes of flash, a 48 MHz Arm Cortex-M3 core, a dedicated sensor controller, and a radio that reaches minus 124 dBm in long range mode at 50 kbps. The RGZ suffix is the 7 mm by 7 mm VQFN48 body with 30 general purpose input output pins, on a 2500 piece reel.
The reason to choose the RGZ over the smaller bodies in the same family is pin count, not performance. The 4 mm by 4 mm body brings out 10 general purpose pins and the 5 mm by 5 mm body brings out 15. A node that has to drive an LCD, read four sensors, keep two serial ports and still leave room for a debug header needs the 30 pin body, and no amount of clever firmware recovers a pin that is not bonded out.
The device is a system rather than a radio. The Cortex-M3 runs the application, the sensor controller runs the analog sampling autonomously at very low current, and the radio runs the protocol. That split is what lets a battery node wake once a second, take a 12 bit conversion at 0.95 microamps average, and go back to sleep without waking the main core.
What the numbers on the first page actually say
The supply range is 1.8 V to 3.8 V, which covers a pair of alkaline cells, a single lithium cell and a 3.3 V rail. The receive current is 5.4 mA and the transmit current at plus 10 dBm is 13.4 mA. Standby with the real time clock running and RAM retained is 0.7 microamps, and shutdown with wake on an external event is 185 nanoamps.
Sensitivity is minus 124 dBm in long range mode at 50 kbps and minus 110 dBm at 50 kbps in the 802.15.4 arrangement. Selectivity at 100 kHz is 56 dB and blocking at 10 MHz is 90 dB. Those three numbers together decide whether a node survives a site with a strong interferer nearby, and they are the reason this family is used in metering and building automation rather than only in consumer toys.
The output power is programmable up to plus 15 dBm, which at 868 MHz is close to the regulatory ceiling for a duty cycled device and at 915 MHz is inside the American limit for frequency hopping systems.
| Function | sub 1 GHz wireless microcontroller |
| Core | Arm Cortex-M3 at 48 MHz |
| CoreMark score | 142, and 158 on the ULPBench benchmark |
| Flash | 128 kilobytes in the F128 variant |
| SRAM | 8 kilobytes of cache SRAM plus 20 kilobytes of ultra low leakage SRAM |
| Sensor controller | 16 bit, autonomous, 2 kilobytes of its own SRAM |
| Radio range | sub 1 GHz, 2-FSK, GFSK, OOK and 802.15.4g |
| Sensitivity | minus 124 dBm long range at 50 kbps |
| Output power | up to plus 15 dBm |
| Receive current | 5.4 mA |
| Transmit current | 13.4 mA at plus 10 dBm |
| Standby current | 0.7 microamps with the clock running and RAM retained |
| Shutdown current | 185 nanoamps with wake on an external event |
| ADC | 12 bit, 200 thousand samples per second, 8 channel multiplexer |
| Supply range | 1.8 V to 3.8 V |
| Package | VQFN, RGZ body, 48 pins, 7 mm by 7 mm, 30 general purpose pins |
| Carrier | 2500 pieces on a large reel |
| Debug | 2 pin cJTAG and JTAG |
Thirty pins is a system decision
The pin budget on a wireless node is spent faster than most people expect. A segment LCD takes eight to twelve pins. Two UART ports take four. An SPI flash takes four. A debug header takes two, and the radio's own control lines take a few more. That is already twenty five, and the body with 15 pins cannot do it.
The RGZ body also carries more analog channels and more timer outputs, which matters when the application needs three pulse width modulated outputs for an LED driver or a valve. The smaller bodies share the same die but not the same bonding, so the peripheral set is the same and the accessible pins are not.
The cost is area. 7 mm by 7 mm against 4 mm by 4 mm is 49 square millimetres against 16, and on a module that has to fit inside a sensor housing that difference decides the mechanical envelope. We see both choices in our order book, and the split is almost always decided by the display rather than by the radio.
Where this family is used, and why
The document lists the 802.15.4g smart utility network, wireless M-Bus, building automation, metering, alarm and security, and long range sensor networks. The common structure is a node that has to run for years on a battery, report at a low duty cycle, and survive an RF environment that is not under anyone's control.
Electricity and water meters are the largest segment. The meter has a display, a metering front end, a radio and a tamper switch, which is a 30 pin budget, and it has to last fifteen years on a lithium cell. The 0.7 microamp standby and the autonomous sensor controller are what make that arithmetic close.
Building automation is the second segment, and there the radio has to coexist with lighting ballasts and variable speed drives. The 90 dB blocking figure at 10 MHz is what keeps a node working when a drive is switching nearby, and it is a specification that a cheaper radio does not print because it does not meet it.
Alarm and security is the third, and it is the segment where the standby current decides the product. A door sensor that reports once a day and otherwise sleeps has to run three years on a coin cell. At 0.7 microamps of standby the arithmetic is dominated by the cell's self discharge rather than by the radio, which is the point at which power stops being the constraint.
Our MCU cross reference page covers the wireless microcontroller families we hold, and the component lead time solutions page describes the route when one flash size of a family is on allocation and another is not.
The sensor controller deserves one more paragraph because it is the feature that separates this family from a plain wireless microcontroller. It is a 16 bit processor with its own 2 kilobytes of SRAM that runs while the main core sleeps, and it can sample the 12 bit converter, compare a threshold and wake the main core only when something changed. At 24 MHz it draws 0.4 mA plus 8.2 microamps per megahertz, and at 2 MHz it draws a fraction of that.
The arithmetic that matters is the average. A node that samples a strain gauge once a second, filters the reading and only wakes the main core when the value moves outside a band spends almost all of its life in the sensor controller at low clock, and the main core sees an interrupt a few times an hour. That is how a battery powered bridge sensor reaches a multi-year life without a low power analog front end.
The radio itself is unchanged across the three bodies, which is what lets a product family offer three sizes on one firmware image. The pin count and the thermal path are the differences, and both are mechanical decisions rather than electrical ones.
Three questions buyers ask about this string
Is it pin compatible with the 5 mm body? No. Same family, different pin count and different pin functions. A board change is required.
Does the F128 mean 128 kilobytes usable? The flash is 128 kilobytes and the ROM carries the drivers and the bootloader, so the application has most of the flash for itself.
Can it run from a 3.6 V lithium cell directly? Yes, 3.8 V is the ceiling and a fresh cell is 3.6 V, which leaves little margin for a transient but is inside the window.