LPC1857JBD208E vs LPC1853JBD208E Comparison
Detailed side-by-side comparison of LPC1857JBD208E by NXP Semiconductors and LPC1853JBD208E by NXP Semiconductors. Compare key specifications, electrical parameters, packaging, lifecycle status, pricing, and availability to determine the best component for your design requirements.
Specification Comparison
| Parameter | LPC1857JBD208E | LPC1853JBD208E |
|---|---|---|
| Brand | NXP Semiconductors | NXP Semiconductors |
| Category | Microcontrollers | Microcontrollers |
| Lifecycle Status | Active | Active |
| Product Type | 32-bit ARM Cortex-M3 microcontroller | 32-bit microcontroller |
| Maximum CPU Frequency | 180 MHz | 180 MHz |
| Flash Memory | 1 MB (1M x 8) | 512 KB |
| SRAM | 136 kB | — |
| CPU Architecture | ARM Cortex-M3 | — |
| Pipeline | 3-stage | — |
| USB Interfaces | 2 HS USB | — |
| Ethernet Support | Yes | Supported in the LPC185x/3x/2x/1x family |
| LCD Support | Yes | — |
| Package | 208-LQFP (28 mm x 28 mm) | 208-pin LQFP |
| Number of Pins | 208 pins | — |
| Mounting Type | Surface mount | Surface mount |
| Data Bus Width | 32-bit | — |
| Operating Supply Voltage | [DATA_NEEDED: operating supply voltage] | — |
| Operating Temperature Range | [DATA_NEEDED: operating temperature range] | [DATA_NEEDED: LPC1853JBD208E temperature grade] |
| GPIO Count | [DATA_NEEDED: GPIO count] | [DATA_NEEDED: target-device GPIO count] |
| RoHS Compliance | [DATA_NEEDED: RoHS compliance status] | unknown |
| REACH Compliance | [DATA_NEEDED: REACH compliance status] | unknown |
| Processor Core | — | Arm Cortex-M3 |
| Flash Organization | — | 512K x 8 bits |
| Architecture | — | 32-bit ARM RISC |
| Supply Voltage | — | 3.3 V |
| Package Dimensions | — | 28 mm x 28 mm |
| High-Speed USB Interfaces | — | 2 in the LPC185x/3x/2x/1x family |
| LCD Connectivity | — | Supported in the LPC185x/3x/2x/1x family |
| EMC Features | — | EMC-oriented features in the LPC185x/3x/2x/1x family |
| SRAM Capacity | — | [DATA_NEEDED: target-device SRAM capacity] |
| AEC-Q100 Qualification | — | not_applicable |