NXP LPC1549JBD64, ARM Cortex-M3 single-core at 72MHz, 256KB Flash / 36KB SRAM / 4KB EEPROM, 24-channel 12-bit ADC, USB/CANbus/SPI/I²C/UART, 2.4–3.6 V supply, -40°C to 105°C, 64-LQFP.
- 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 | LPC15xx |
| Mounting type | Surface Mount |
| Oscillator type | Internal |
| Program memory type | FLASH |
| Voltage - supply (Vcc (Vdd)) | 2.4V ~ 3.6V |
| Operating temperature | -40°C~105°C(TA) |
| Speed | 72MHz |
| Package | Bulk |
| RAM size | 36K x 8 |
| Core size | 32-Bit Single-Core |
| EEPROM size | 4K x 8 |
| Peripherals | Brown-out Detect/Reset, DMA, POR, PWM, WDT |
| Connectivity | CANbus, I²C, SPI, UART/USART, USB |
| Number of i (O) | 44 |
| Core processor | ARM® Cortex®-M3 |
| Case | 64-LQFP |
| Data converters | A/D 24x12b |
| Program memory size | 256KB (256K x 8) |
Frequently asked questions
Does the LPC1549JBD64 work as a drop-in replacement for the LPC1764 in an existing design?
The two parts are both NXP ARM Cortex-M3 MCUs in LQFP-64 packages, but the LPC1549JBD64 runs at 72MHz with 256KB Flash, integrated USB PHY, CANbus, and a 24-channel 12-bit ADC on a 2.4–3.6 V rail, while the LPC1764 targets a different peripheral map and voltage range. Direct drop-in compatibility cannot be assumed — a full peripheral and pinout review against the respective datasheets is required before substituting.
What debug interface does the LPC1549 use — is it compatible with SEGGER J-Link and PE Micro Cyclone programmers?
The ARM Cortex-M3 core standard debug interface is SWD (Serial Wire Debug); JTAG is also available on this part. SEGGER J-Link and PE Micro Cyclone both support ARM SWD natively, so standard firmware download and debug access should be available through the standard debug connector without requiring a proprietary adapter. Confirm the specific pin-strapping on the target board matches the debug header layout before connecting.