CC2543RHBR
Product Specifications
CC2543RHBR
Texas Instruments — Power Management & Signal Chain
Product Overview
The CC2543RHBR 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
CC2543RHBR 2.4 GHz radio system on chip with an 8051 core in a 32 pin QFN
The CC2543RHBR is a single chip 2.4 GHz transceiver and microcontroller, built around an 8051 core with 32 KB of flash and 1 KB of SRAM. It covers 250 kbps, 500 kbps, 1 Mbps and 2 Mbps data rates, transmits up to 5 dBm, and receives at minus 98 dBm for the 250 kbps rate and minus 90 dBm at 2 Mbps. The radio and the core share a body, so a product can be a sensor node with a battery, a crystal, a matching network and almost nothing else.
The part belongs to the generation of 2.4 GHz systems that put the protocol work in hardware and leave the application in an eight bit core. Baseband automation, address decoding, auto acknowledgement, the AES coprocessor and a 40 bit radio timer all sit in the radio block, so the firmware writes a payload and reads a payload rather than bit banging a modem. That is why this family is still found in proprietary 2.4 GHz links that predate the Bluetooth low energy ecosystem.
Key parameters taken from the CC2543RHBR document
| Core | 8051 with code prefetch, 32 KB of in system programmable flash and 1 KB of SRAM |
| Radio | 2.4 GHz transceiver covering 250 kbps, 500 kbps, 1 Mbps and 2 Mbps, with programmable output power up to 5 dBm |
| Sensitivity | Minus 98 dBm at 250 kbps and minus 90 dBm at 2 Mbps, which sets the link budget without an external front end |
| Security | AES security coprocessor in hardware, with a true random number generator |
| Baseband | Auto acknowledgement, address decoding, clear channel assessment and a 40 bit radio timer |
| Interfaces | UART, SPI and I2C on one serial block, two channel DMA, general purpose timers and an infrared generation block |
| Inputs and outputs | 16 general purpose pins, three of them with 20 mA drive, the rest at 4 mA |
| Clocks | 32 MHz crystal oscillator, 16 MHz and 32 kHz internal oscillators, and a 32 kHz sleep timer with capture |
| Supply | 2.0 V to 3.6 V on all supply pins, which allows a pair of alkaline cells or a single lithium cell without a regulator |
| Temperature | Minus 40 to plus 85 C |
| Body | VQFN RHB 32 pins, 5 mm by 5 mm, suitable for a single layer board with the reference matching network |
| Order code facts | CC2543RHBR, 3000 pieces on a large reel, moisture level 3 with a 168 hour floor life, marking CC2543, with a 250 piece small reel row as CC2543RHBT |
| Regulatory | Suitable for systems targeting ETSI EN 300 328, EN 300 440 class 2, FCC part 15 and ARIB STD-T66 |
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 link budget is the first calculation to make, and this part makes it easy because both ends are printed. Minus 98 dBm of sensitivity at 250 kbps and 5 dBm of output give 103 dB of budget before any antenna gain, which covers a factory floor with margin at a slow rate. At 2 Mbps the budget falls to 95 dB, which is still workable indoors but not through two concrete walls. A product that needs range should run at the slow rate and accept the latency, and a product that needs throughput should plan for more nodes rather than more power.
The 2.0 V supply floor is unusual in a 2.4 GHz part and it is the reason this family turns up in battery products with no regulator. Two alkaline cells at 1.5 V each sit above the floor for most of their life, and a single lithium cell sits inside the window from fresh to nearly empty. The catch is that the radio performance tables are specified at 3.0 V, and the output power and the sensitivity both degrade as the rail falls, so a product that runs to 2.0 V has to check its link budget at that rail rather than at 3 V.
The 8051 core is a deliberate choice for a sensor node, not a limitation to work around. It runs at 32 MHz, it has enough flash for a proprietary protocol stack and an application, and it draws little enough that a coin cell lasts years at a low duty cycle. The constraint is arithmetic: a CRC heavy protocol or an encryption layer beyond the hardware AES block will eat the core, and that is the point where a Cortex based part becomes the better answer. For a simple star network with a few hundred bytes a minute, the 8051 is not the bottleneck.
The QFN32 body with a reference matching network is friendly to a single layer board, which is worth noting for cost. The vendor reference boards show the balun and the filter built from discrete parts on the same layer as the module, so a two layer board is enough. That matters in a sensor that has to be cheap, and it also matters in a product with a metal enclosure, where the antenna and the matching network are the hardest part of the certification and the part that is easiest to get wrong.
- Sensitivity and output power at the lowest supply rail the product will actually reach.
- Link budget over the real distance and through the real enclosure, measured rather than calculated.
- Crystal accuracy against the regulatory limit, since the 2.4 GHz band is narrow at the edges.
- Matching network values from the reference board, adjusted for the actual board thickness.
- Current in each mode at the duty cycle the product will use, not at continuous receive.
- Firmware timing for the radio timer and the sleep mode, measured on the assembled board.
Which projects this part fits
This part fits proprietary 2.4 GHz sensor networks, wireless remote controls and human interface devices, industrial monitoring nodes, wireless audio accessories at the lower rates, active RFID tags and building automation endpoints. It is the right selection where the protocol is proprietary, where the data rate is modest and where the supply has to run from a battery without a regulator. For customers with a product already in the field on this family, the useful question is not a replacement but a supply position, because the pinout and the firmware are what the installed base depends on.
Questions that come up before a purchase order is released
Is this part compatible with Bluetooth low energy?
No. It is a 2.4 GHz transceiver with a proprietary baseband, and it does not run the Bluetooth low energy link layer. The IEEE 802.15.4 and Bluetooth low energy families are separate parts with different cores and different radio blocks. A product that needs to interoperate with a phone needs the other family, and a product that owns both ends of the link can use this one and keep the simpler firmware.
How much flash does a protocol stack need?
A proprietary star network with acknowledgement, address filtering and a small application fits in the 32 KB with room to spare. A mesh or a full standard stack does not, which is why the mesh products in this class use parts with more flash and a 32 bit core. The honest answer is that the stack, not the application, decides the flash size.
Why does the sensitivity change with the data rate?
Because the receiver bandwidth has to widen to pass a faster signal, and a wider bandwidth admits more noise. The ten decibel difference between 250 kbps and 2 Mbps is almost exactly the bandwidth ratio, which is the physics of every radio. A product that needs both range and throughput uses the slow rate for the link and sends less data, or uses a higher gain antenna.
What is the 40 bit radio timer for?
It timestamps radio events with a resolution fine enough to schedule transmit and receive windows without intervention from the core. That is what makes a low duty cycle protocol possible, because the core can sleep while the radio timer wakes it for the next window. In a beaconing or a time slotted network this block is the difference between a workable current budget and one that misses the target.
Is the part still available for new programs?
It is active in the vendor catalogue, and the reels are stocked. It is an older generation part, so a new program should confirm the long term supply position before it commits, and should keep the pin compatible members of the family in the approved vendor list. That is standard practice for any eight bit radio in 2026, and it is the kind of thing we check before quoting a multi year schedule.
How SUPERB handles this line
We supply the CC2543RHBR from original reels with lot traceability and keep both the 3000 piece reel and the 250 piece small reel in view, because a prototype build rarely needs a full reel. The RF component sourcing page lists the 2.4 GHz and sub 1 GHz families we carry, MCU cross reference covers the cores and the memory sizes side by side, and component obsolescence management is the page we open when an eight bit radio reaches the end of its life and the installed base still needs parts.