Skip to main content
Texas Instruments CC2640R2FRGZR — RF & Wireless ICs

CC2640R2FRGZR Bluetooth 5.0 MCU, 128kB Flash

MPNCC2640R2FRGZR
Active

Texas Instruments SimpleLink™ CC2640R2FRGZR, Bluetooth v5.0 TxRx + MCU, 2.4GHz, 128kB Flash, 20kB RAM, -97dBm sensitivity, 5dBm output, 31 GPIO, I²C/I²S/SPI/UART, 1.8V–3.8V, -40°C–85°C, 48-VFQFN Exposed Pad.

$5.3300Ref. price · indicative, final on quote
StockContact for availability
MOQ1 pcs
  • 100% new & originalTraceable channels only — no refurbs, no pulls, no remarked parts.
  • Date & lot codes on quoteStated per line before you commit; label photos on request.
  • MSL-compliant ESD packingMoisture-sealed bags with indicator cards; reels photo-verified.
  • PayPal buyer protectionPay by T/T, PayPal or Payoneer — card payments covered end to end.

Specifications

CC2640R2FRGZR Technical Specifications
ParameterValue
TypeTxRx + MCU
SeriesSimpleLink™
Mounting typeSurface Mount
RF familyBluetooth
Voltage1.8V ~ 3.8V
Current - receiving5.9mA
Current - transmitting9.1mA
Power - output5dBm
Frequency2.4GHz
ProtocolBluetooth v5.0
InterfaceI²C, I²S, SPI, UART
Operating temperature-40°C~85°C
GPIO31
PackageTape & Reel (TR); Cut Tape (CT)
ModulationGFSK
Memory size128kB Flash, 20kB RAM
Sensitivity-97dBm
Case48-VFQFN Exposed Pad
Data rate2Mbps

Product details

Bluetooth 5.0 wireless MCU with integrated transceiver

The Texas Instruments CC2640R2FRGZR is a Bluetooth v5.0-qualified wireless MCU from the SimpleLink™ family, combining a 2.4GHz transceiver with an ARM Cortex-M3 core. It carries 128kB of Flash and 20kB of RAM, enough for a BLE application stack plus a sensor profile or control loop. The receiver hits -97dBm sensitivity, and the transmitter delivers up to 5dBm output power — a combination that gives a clean link budget for indoor IoT nodes, wearable peripherals, and industrial sensor tags. Thirty-one GPIO lines bring out I²C, I²S, SPI, and UART interfaces, so the part can talk to external sensors, codecs, or displays without a separate host MCU. The supply range spans 1.8V to 3.8V, letting it run from a single Li-ion cell or two alkaline batteries without an extra regulator.

The 48-VFQFN with exposed pad (7x7 mm footprint) provides a low-inductance ground path for the RF section and helps pull heat away from the PA during continuous transmission. The exposed pad needs a solid via stitch to the ground plane on the PCB — without it, the junction temperature rises faster under sustained TX at 5dBm.

For BOM planning, the base product number CC2640 covers multiple Flash and RAM density variants in the same 48-VQFN footprint, giving a drop-in migration path if a future firmware revision needs more memory.

Current draw and battery-life planning

Receiving current is 5.9mA and transmitting current is 9.1mA at the 5dBm output setting. For a coin-cell-powered beacon that transmits a 30-byte advertisement packet every second, the average current settles well under 100 µA when the device spends most of its time in sleep. The 20kB RAM is enough to hold connection state and a small sensor buffer during standby, keeping the active current draw short. If the design needs longer range at the cost of battery life, the 5dBm output can be reduced via software to a lower power level to save current.

Programming and debugging interface

The CC2640R2FRGZR is programmed through the standard ARM Serial Wire Debug (SWD) interface, accessible on dedicated pins. TI provides a royalty-free BLE-Stack SDK that includes the Bluetooth 5.0 protocol stack, sample applications, and a flash programmer utility. No external programmer is required beyond a standard JTAG/SWD debug probe such as the XDS110 or J-Link. The 128kB Flash holds both the application code and the stack image, so the firmware update process uses an internal bootloader that can receive new images over the air or through the UART.

Frequently asked questions

What is the maximum data rate of CC2640R2FRGZR?

The CC2640R2FRGZR supports a maximum data rate of 2Mbps, as defined by the Bluetooth 5.0 standard. This is the PHY-level rate; actual application throughput depends on connection interval and packet overhead.