CC2640R2FRHBR
Product Specifications
CC2640R2FRHBR
Texas Instruments — Power Management & Signal Chain
Product Overview
The CC2640R2FRHBR 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
CC2640R2FRHBR: 275 KB of nonvolatile memory in a 5 mm by 5 mm body
CC2640R2FRHBR is the 5 mm by 5 mm VQFN32 member of the CC2640R2F family, a Bluetooth 5.1 Low Energy wireless microcontroller built on an Arm Cortex-M3 core that runs to 48 MHz. The RHB suffix is the body, not the feature set: the same die is offered in a 4 mm by 4 mm VQFN32 with 10 general purpose pins, a 7 mm by 7 mm VQFN48 with 31 pins, and a chip scale body, and the 5 mm body sits in the middle with 15 pins brought out.
The number that sells this part is 275 KB of nonvolatile memory, of which 128 KB is in system programmable flash and the rest is ROM holding the radio drivers, the TI-RTOS kernel and the Bluetooth stack. That split is the reason a 128 KB flash part can carry a full protocol stack plus an application: the stack is not in the flash. It is also the reason a firmware image cannot simply be moved to another vendor part with the same flash size.
The figures below come from SWRS204C, revised September 2020, and from the orderable addendum at the back of that document. They are the ones we check against a customer BOM before a quotation leaves the desk, because the two mistakes that cost money on this family are ordering the wrong body and assuming the automotive window applies to a part that stops at 85 degrees.
What the RHB body keeps and what it gives up
The RHB body brings out 15 general purpose pins against 31 on the RGZ body and 10 on the RSM body. Fifteen is enough for a sensor node with a serial port, a couple of interrupts, a battery monitor and a two wire bus, and it is not enough for a board that wants to drive a display, a keypad and a radio front end at the same time. That single difference decides which body a project can use, and it is decided long before the first purchase order.
Pin compatibility is printed in the feature list and it is worth reading carefully. The part is pin compatible with the CC2640 and CC2650 in all VQFN packages, and with the CC2642R and CC2652R in the 7 mm by 7 mm VQFN package, which is the RGZ body and therefore not this one. A board laid out for the 5 mm body can take a CC2640R2F in the RHB body without a change, and it cannot take the newer multiprotocol parts without a change, so an upgrade path through this body is a dead end by silicon, not by software.
| Function | Bluetooth 5.1 Low Energy wireless microcontroller |
| Core | Arm Cortex-M3, up to 48 MHz, EEMBC CoreMark score 142 |
| Nonvolatile memory | 275 KB total, of which 128 KB is in system programmable flash |
| System memory | 28 KB SRAM, of which 20 KB is ultra-low leakage, plus 8 KB cache SRAM |
| Sensor controller | 16-bit autonomous core with 2 KB of its own SRAM |
| Radio | 2.4 GHz transceiver, Bluetooth 5.1 and proprietary 2.4 GHz modes |
| Receiver sensitivity | minus 97 dBm for Bluetooth Low Energy, minus 103 dBm for 125 kbps coded PHY |
| Link budget | 102 dB for Bluetooth Low Energy |
| Output power | up to plus 5 dBm, programmable |
| Supply range | 1.8 V to 3.8 V, internal DC/DC converter, 1.7 V to 1.95 V external regulator mode |
| Receive current | 5.9 mA active |
| Transmit current | 6.1 mA at 0 dBm, 9.1 mA at plus 5 dBm |
| Standby current | 1.1 microamps with RTC running and RAM retained |
| Shutdown current | 100 nA, wake on external event |
| Analog | 12-bit ADC at 200 kSamples per second, 8 channel multiplexer, analog comparator |
| Serial | UART, I2C, I2S, two synchronous serial interfaces |
| Security | AES-128 accelerator, true random number generator |
| Package | VQFN32, RHB, 5 mm by 5 mm, 15 GPIO |
| Ambient range | minus 40 to plus 85 degrees Celsius |
| Carrier | large tape and reel, quantity printed in the addendum row |
The radio numbers behind the antenna decision
Receiver sensitivity of minus 97 dBm on the 1 Mbps PHY and minus 103 dBm on the 125 kbps coded PHY is the pair that decides whether a product needs an external front end. With plus 5 dBm of output the link budget is 102 dB on the standard PHY, which at 2.4 GHz buys roughly 40 metres indoors through two walls and several hundred metres in open air with a good antenna. A product that needs more than that is not asking for a different resistor, it is asking for the CC2592 range extender, which the feature list names explicitly as a supported pairing.
The transmit current rises from 6.1 mA at 0 dBm to 9.1 mA at plus 5 dBm, so the last 5 dB costs 3 mA. In a sensor that reports once a minute the difference is invisible in the average, and in a device that streams audio or continuous waveform data it is a third of the radio budget. We see customers set plus 5 dBm by default and then wonder why a 220 mAh cell lasts nine months instead of a year, and the answer is usually that the link worked fine at 0 dBm.
The single ended or differential RF interface is a real choice rather than a formality. A single ended port needs a balun and a matching network, four to six parts and a small amount of board area, and it accepts a printed antenna or a chip antenna directly. A differential port removes the balun and saves the loss and the parts, at the cost of a tighter board arrangement and an antenna that is balanced. For a module this is an engineering decision inside the module. For a discrete build it is the first decision on the radio side.
Where the 275 KB goes, and why 128 KB of flash is not the whole story
The ROM holds the Bluetooth Low Energy stack and the RTOS kernel for the qualified configuration that TI ships. An application that uses the stack in the supported configuration therefore pays only for its own code in flash, which is how a 128 KB flash part supports a product that would otherwise need twice that. The moment the application needs a stack configuration outside the ROM image, the stack moves into flash and the arithmetic changes: a few tens of kilobytes of flash disappear before any application code is added.
The 28 KB of SRAM is split, with 20 KB described as ultra-low leakage and 8 KB usable as cache or as ordinary system memory. In a beacon that sleeps most of the time this is generous. In a device that buffers sensor samples at 200 kSamples per second it is not, and the sensor controller with its own 2 KB is what makes the difference: it can sample, threshold and wake the main core only when something changed, which is why the family quotes 1 Hz ADC sampling at about 1 microamp of system current.
Over the air upgrade is supported, and that has a memory consequence worth stating in a quotation discussion. A bootloader and a second image slot both consume flash, so a product that must support field upgrade should be planned against the 128 KB figure minus the bootloader, not against the headline number.
Power arithmetic for a battery node
A reporting node that wakes every 60 seconds, transmits for 3 ms at 0 dBm and sleeps in between spends about 18 microamp seconds per hour in transmit, which is 0.005 microamp hours, and the rest of the budget belongs to the standby current of 1.1 microamps. Over a year that is roughly 9.6 mAh of standby plus a negligible transmit share, so a 220 mAh coin cell is limited by shelf life, not by the radio. The same node with the part held in shutdown at 100 nA and woken by a reed switch reaches years of life, at the cost of losing RAM contents.
The internal DC/DC converter is what makes the 1.8 V to 3.8 V range usable from a single lithium cell without an external regulator, and it is also why the external regulator mode exists: a system that already regulates to 1.8 V can bypass the converter and connect the supply pins directly, which removes switching noise from a sensitive analog rail. Boards that mix a radio and a low noise analog front end often take that second route for exactly this reason.
Replacing a module built around this die
Most of the CC2640R2F volume we see is inside modules, and the question that arrives with it is whether the module can be replaced by the bare part. The answer depends on three things that the module hid: the crystal and its load capacitors, the matching network and antenna, and the certification. The bare part needs a 24 MHz crystal within the tolerance printed in the reference documents, a matching network built for the chosen antenna, and a fresh radio certification for the end product. A module that already carries certification is often cheaper than a bare part plus a test house visit.
When the replacement is a module for a module, the work is in the pin map and the firmware image, and our MCU cross reference page describes how we compare two candidates parameter by parameter before a build is committed. For a drone or a handheld tracker the radio and the antenna arrangement usually dominate, and the drone and UAV component page collects the parts we hold for that class of build.
Where a customer is moving a product from a CC2640 module to the CC2640R2F, the software path is real: the stack is qualified for the newer part, and the register map is close enough that most application code moves without change. Where the move is from the CC2640R2F to a multiprotocol part, the software path is a port rather than a recompile, and the flash arithmetic above is the reason.
Ordering and incoming checks
The orderable row prints the part as active and in production, VQFN32 with 5 mm by 5 mm body, large tape and reel, NIPDAU lead finish and moisture level 3 at 260 degrees, which means a 168 hour floor life after the bag is opened and a bake decision if the reel sits on the shelf. That is the single most common scheduling surprise on this family: the part is not level 1, and a line that treats it like level 1 will discover it at reflow.
Incoming inspection is short. Check the reel label against the full order code including the RHB body and the reel size, check the marking against the addendum row, confirm the moisture indicator card, and read the radio on a sample of five pieces in a fixture if the build is for a certified product. The part has no calibration step at the factory that a customer can repeat, so a sample that transmits at the wrong power is a counterfeit signal rather than a process drift.
For a build that needs the parts kitted with the rest of the board, the one stop BOM sourcing route holds this string and the passives around it on a single line, which matters when the crystal and the matching network come from a different supplier with a different lead time.
Three questions buyers ask about this string
Is 128 KB of flash enough for a product with over the air upgrade? Usually yes, because the stack lives in ROM, but the bootloader and the second image slot have to come out of the same 128 KB. Plan against 100 KB of application space and the answer stays yes.
Can this part run from a 1.8 V rail without an external regulator? Yes, in external regulator mode, with the supply pins connected together, but the internal converter cannot be used in that mode and the transmit current then flows from the 1.8 V rail directly.
Is the automotive grade available in this body? No. The automotive qualified members of the family carry their own order codes and their own temperature windows, and a purchase order that names only the family can land on an industrial row. The component traceability report is the document we produce when a build has to prove which grade went onto which serial number.