Skip to main content
Log in
Texas Instruments MSP430G2203IRHB32R — Microcontrollers & Processors (MCU / MPU / DSP)

TI MSP430G2203IRHB32R 16-Bit MCU, 16MHz, 2KB Flash, 32-VQFN

MPNMSP430G2203IRHB32R
Active

Texas Instruments MSP430G2xx series MSP430G2203IRHB32R, 16-Bit Microcontroller, MSP430 CPU16 core, 16MHz, 2KB Flash, 256 x 8 RAM, 24 I/O, I²C/SPI/UART/USART, 1.8V~3.6V, -40°C~85°C, 32-VFQFN Exposed Pad, Tape & Reel.

$1.1664Ref. price · indicative, final on quote
Texas Instruments MSP430G2203IRHB32R datasheet (PDF)
Independent supplier — new & surplus stockAuthenticity-screened · ESD-safe packingListing updated Jul 2026

Specifications

MSP430G2203IRHB32R specifications
ParameterValue
SeriesMSP430G2xx
MountingSurface Mount
Oscillator typeInternal
Program memory typeFLASH
Voltage - supply (Vcc (Vdd))1.8V ~ 3.6V
Operating temperature-40°C~85°C(TA)
Speed16MHz
PackageTape & Reel (TR)
RAM size256 x 8
Core size16-Bit
PeripheralsBrown-out Detect/Reset, PWM, WDT
ConnectivityI²C, IrDA, LINbus, SCI, SPI, UART/USART
Number of i (O)24
Core processorMSP430 CPU16
Case32-VFQFN Exposed Pad
Program memory size2KB (2K x 8)

Product details

2 KB Flash and 256 B RAM — sizing the control task

The MSP430G2203IRHB32R is a 16-bit ultra-low-power microcontroller from TI's MSP430G2xx family, built around the MSP430 CPU16 core.

32-VQFN package — rework and layout notes

The 32-VFQFN with exposed pad (5x5 mm body) is a compact, low-profile package. The 24 I/O lines are all accessible on the peripheral pads.

For dual-sourcing resilience, the MSP430G2xx family includes several pin-compatible Flash-density variants (e.g., 1 KB to 8 KB options) that share the same 32-VQFN footprint, though the exact memory and peripheral mix should be verified against the target application's code size.

Frequently asked questions

What are the equivalents for MSP430G2203IRHB32R?

Within the MSP430G2xx series, pin-compatible 32-VQFN variants with different Flash densities (e.g., 1 KB, 4 KB, 8 KB) share the same footprint and peripheral set. The closest fit depends on your code size and I/O requirements — verify the exact memory and peripheral match against the datasheet before substituting.