CC2640R2FRSMR
Product Specifications
CC2640R2FRSMR
Texas Instruments — Power Management & Signal Chain
Product Overview
The CC2640R2FRSMR 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
CC2640R2FRSMR Bluetooth 5.1 low energy wireless MCU in the 4 by 4 mm 32 pin VQFN body
The CC2640R2FRSMR is a 2.4 GHz wireless microcontroller built around an Arm Cortex M3 running at 48 MHz, with a radio that supports Bluetooth 5.1 Low Energy and proprietary 2.4 GHz traffic. The 4 by 4 mm VQFN32 body brings out 10 GPIO, which is the small end of the family and the right choice for a sensor tag or a beacon where every square millimetre of board counts. The larger bodies in the same family carry the same silicon with more pins.
The architecture is what separates this part from a general purpose microcontroller with a radio bolted on. A dedicated Cortex M0 radio core runs the physical layer and the timing, the main Cortex M3 runs the application, and a third small processor, the sensor controller, runs the analogue sampling while both other cores sleep. On a product that wakes once a second to read a sensor and sends a packet once a minute, the sensor controller is the difference between one microamp of average current and twenty. That is why the part sits in medical patches, asset tags and building sensors rather than in products that stay awake.
Key parameters taken from the CC2640R2FRSMR document
| Processor | Arm Cortex M3 at 48 MHz, CoreMark score 142, with a separate Cortex M0 radio core and a 16 bit sensor controller |
| Memory | 275 KB of non volatile memory including 128 KB of in system programmable flash, up to 28 KB of system SRAM of which 20 KB is ultra low leakage, and 8 KB of SRAM usable as cache or general purpose memory |
| Radio | 2.4 GHz transceiver compatible with Bluetooth 5.1 and earlier low energy specifications, with LE Coded PHY, LE 2 Mbit PHY, advertising extensions and multiple advertising sets |
| Sensitivity | Minus 97 dBm for Bluetooth low energy at 1 Mbps, minus 103 dBm on the 125 kbps LE Coded PHY, with a link budget of 102 dB |
| Output power | Programmable up to +5 dBm |
| Receive current | 5.9 mA active, 6.1 mA in transmit at 0 dBm, 9.1 mA in transmit at +5 dBm |
| Microcontroller current | 61 microamps per MHz active, 48.5 CoreMark per milliamp |
| Sensor controller current | 0.4 mA plus 8.2 microamps per MHz, capable of 1 Hz ADC sampling at 1 microamp of system current |
| Sleep states | Standby 1.1 microamps with RTC running and RAM retained, shutdown 100 nA with wake on an external event |
| Supply | 1.8 to 3.8 V in normal operation, 1.7 to 1.95 V in external regulator mode, with an on chip DC to DC converter |
| Peripherals | 12 bit 200 ksample per second ADC with eight channel multiplexer, four general purpose timer modules, UART, I2C, I2S, two SSI ports, AES 128 accelerator, true random number generator, eight capacitive sensing buttons, integrated temperature sensor |
| Pin compatibility | Drops into the CC2640 and CC2650 footprint in every VQFN body, and into the CC2642R and CC2652R footprint in the 7 by 7 mm body |
| Body | VQFN 32 pins, 4 by 4 mm, 10 GPIO, in a family that also offers 2.7 by 2.7 mm DSBGA34, 5 by 5 mm VQFN32 with 15 GPIO and 7 by 7 mm VQFN48 with 31 GPIO |
| Order code facts | CC2640R2FRSMR, VQFN RSM 32 pins, 3000 pieces on a large reel, NIPDAU or tin finish, moisture level 3 with a 168 hour floor life, minus 40 to plus 85 C |
The table above is read from the vendor document, not from a distributor summary. Where a window is printed, the window is what a production test should use, and the typical value is only a starting point for the first article.
Where the numbers matter in a real build
The 10 GPIO in this body is the constraint that decides whether the part fits an application, and it is easy to misjudge on paper. Two pins go to the 24 MHz crystal and two more to the 32 kHz crystal if a low frequency clock is used, the debug port takes two, the SPI flash lines take four when the product boots from external memory, and the radio needs one or two for the front end control. That leaves very few for the application. Products that need a display, several sensors and a button matrix belong in the 5 by 5 mm or 7 by 7 mm body, and the silicon is the same, so the decision is made on pins rather than on features.
The external regulator mode is worth understanding before the power tree is frozen. In the default configuration the internal DC to DC converter runs from the battery and produces the core rail, which is efficient. In external regulator mode the supply window narrows to 1.7 to 1.95 V and the internal converter is bypassed, which is what a product does when it already has a 1.8 V rail and wants to avoid a second switching stage. Feeding 3.3 V into the part while it is configured for external regulator mode damages it, so the configuration has to match the board, not the other way round.
The sensor controller is the feature that is most often left unused and most often missed when it is. It is a separate 16 bit processor with its own 2 KB of SRAM, able to run an ADC sampling loop, compare against a threshold and wake the main core only when the reading is interesting. On a wearables or a medical patch, that turns a 200 microamp average into a 5 microamp average with the same measurement rate. The cost is firmware complexity: the sampling routine lives in its own small program, and the handover to the main application has to be defined carefully, because the two cores share memory and a badly defined mailbox shows up as a corrupted reading rather than as a crash.
The radio figures are quoted at the antenna, so the front end still has to be built. The part supports a single ended or a differential interface, and the vendor reference boards use a balun plus a harmonic filter for the single ended case. On a module that has to pass ETSI EN 300 328 or FCC Part 15, the filter and the matching are what stand between the chip and the compliance report, and a copy of a reference network onto a different stack up usually needs retuning. The +5 dBm maximum output is enough for a link of tens of metres indoors and not enough for a warehouse, where the same part is normally paired with a range extender.
- Average current on the assembled product over a full duty cycle, with the sensor controller running the sampling loop.
- Wake latency from standby to a transmitted packet, since the 1.1 microamp standby figure only holds if the wake path is short.
- Radio output power and harmonic levels at the antenna connector, on the final stack up rather than on the development kit.
- Crystal accuracy over temperature, because the low energy protocol depends on the sleep clock as well as the radio clock.
- GPIO count with every function assigned, including the debug port, before the board is committed to this body.
- Flash and RAM headroom with the protocol stack linked in, since the stack and the application share the 128 KB of flash.
Which projects this part fits
This part fits Bluetooth low energy sensor tags, asset trackers, electronic shelf labels, medical patches and patient monitors, building automation sensors, access control and point of sale peripherals, and proprietary 2.4 GHz links that need a full protocol stack in one body. It also fits products that started on the CC2640 or CC2650 and need a firmware path forward, because the pin compatibility in the VQFN bodies allows a board to keep its footprint while the silicon moves. Customers building a product that must last ten years on a coin cell use this family together with the sensor controller, which is the combination the part was built for.
Questions that come up before a purchase order is released
Why choose the 4 by 4 mm body when it has only 10 GPIO?
Because the board is small and the application is simple. A beacon, a tag or a two sensor node fits in 10 pins once the crystals and the debug port are accounted for, and the smaller body has a shorter RF path and less parasitics around the matching network. Products that need more pins move to the 5 by 5 mm or 7 by 7 mm body with the same silicon and the same firmware, so the decision can be revisited late without a software port.
Does the part need an external flash?
No for most applications, because the 128 KB of in system programmable flash holds the stack and the application. Products that need over the air update with two images, or that store a log, use external SPI flash and boot from it through the ROM bootloader. The 8 KB of cache RAM can be used as general purpose memory when the cache is not needed, which is often the case on a product with a small hot loop.
How is the 102 dB link budget used in practice?
It is the difference between the receiver sensitivity and the transmitter output, minus the losses in the matching network and the antenna. On a product with a chip antenna and a plastic enclosure, the practical budget is 10 to 15 dB below the headline, and the range falls accordingly. A link that works at 50 metres on the bench often works at 20 metres in a building with people and metal in the path, so the budget should be built with the losses included rather than from the data sheet alone.
What changes when the part is used at 1.8 V?
The radio still works, the output power falls slightly and the current consumption falls with the rail. The supply window in normal operation starts at 1.8 V, so a product running from a 3 V coin cell is inside the window for its whole life, and a product running from a lithium ion cell through a regulator is well inside it. Below 1.8 V the part is outside its published range, and the brown out behaviour is not guaranteed.
How is a lot verified at incoming inspection?
Visual check of the reel and the moisture bag, marking check on a sample, and a functional check on a known good board that advertises and connects. The radio performance itself cannot be verified without a shield box and a tester, so the practical screen is a connect and range test against a reference unit. We record the firmware version used in the test with the lot, because a stack change can move the connect behaviour without any change to the silicon.
How SUPERB handles this line
We supply the CC2640R2FRSMR and the other bodies of the same family from original reels with lot traceability, and we check the body and the reel quantity against the order because the part number differs only in the package letters. The MCU cross reference page lists the wireless microcontroller families we carry with their package options, RF component sourcing covers the front end and matching parts that go around a 2.4 GHz radio, and pin to pin cross reference is the page to start from when a board has to move between bodies without a respin.