MSP430FR5987IPMR — MSP430 FRAM MCU, 64KB / 16MHz, 64-LQFP, EOL
Texas Instruments MSP430 FRAM series, 16-bit MSP430 CPUXV2 core at 16MHz, 64KB FRAM / 2KB RAM, 48 I/O, 12-ch 12-bit ADC, I²C/SPI/UART, 1.8–3.6V supply, 64-LQFP, −40°C to 85°C, Tape & Reel.
- 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
| Parameter | Value |
|---|---|
| Series | MSP430™ FRAM |
| Mounting type | Surface Mount |
| Oscillator type | Internal |
| Program memory type | FRAM |
| Voltage - supply (Vcc (Vdd)) | 1.8V ~ 3.6V |
| Operating temperature | -40°C~85°C(TA) |
| Speed | 16MHz |
| Package | Tape & Reel (TR) |
| RAM size | 2K x 8 |
| Core size | 16-Bit |
| Peripherals | Brown-out Detect/Reset, DMA, POR, PWM, WDT |
| Connectivity | I²C, IrDA, SPI, UART/USART |
| Number of i (O) | 48 |
| Core processor | MSP430 CPUXV2 |
| Case | 64-LQFP |
| Data converters | A/D 12x12b |
| Program memory size | 64KB (64K x 8) |
Frequently asked questions
Is the MSP430FR5987IPMR obsolete and what replaces it?
The lifecycle entry shows eol_hot. No successor order code is listed in the available cross-reference. Sourcing requires an RFQ against remaining stock or broker channels — this is not a standard active-part replenishment situation.
Does the 64KB FRAM need linker or memory-map changes when porting code from a Flash-based MSP430?
The MSP430 CPUXV2 core is common across both Flash and FRAM MSP430 families, and TI's driverlib abstracts the memory type. FRAM regions map into the standard linker command-file layout the same way Flash does — the port typically requires adjusting the memory origin and length definitions for the FRAM region size, not a rewrite of peripheral initialization. Verify the specific driverlib version for FRAM-aware API calls if using the FRAM controller (FRCTL) for write-cycle optimization.