MKL27Z64VLH4 vs MKL27Z32VLH4 Vergleich
Detaillierter Direktvergleich von MKL27Z64VLH4 von NXP Semiconductors und MKL27Z32VLH4 von NXP Semiconductors. Vergleichen Sie die wichtigsten Spezifikationen, elektrischen Parameter, Gehäuse, Lebenszyklusstatus, Preise und Verfügbarkeit, um das beste Bauteil für Ihre Designanforderungen zu ermitteln.
Spezifikationsvergleich
| Parameter | MKL27Z64VLH4 | MKL27Z32VLH4 |
|---|---|---|
| Marke | NXP Semiconductors | NXP Semiconductors |
| Kategorie | Microcontrollers | Microcontrollers |
| Lebenszyklusstatus | Aktiv | Aktiv |
| Core Architecture | ARM Cortex-M0+ (32-bit) | — |
| Core Frequency | 48 MHz | — |
| Program Flash Memory | 64 KB | — |
| SRAM | 8 KB | — |
| Gehäuse | 64-pin LQFP (10x10 mm) | 64-LQFP (10 x 10 mm) |
| Montageart | Surface Mount | Surface Mount |
| Supply Voltage (VDD) | 1.71 V to 3.6 V | — |
| USB Controller | USB 2.0 Full-Speed Device (crystal-less) | — |
| Betriebstemperatur | -40 C to +105 C | — |
| ADC | 12-bit SAR ADC (number of channels [DATA_NEEDED: ADC channel count]) | — |
| GPIO Count | [DATA_NEEDED: GPIO count] | — |
| Low-Power Modes | VLLS, VLLSx, LLS, HSRUN | — |
| Communication Interfaces | UART, SPI, I2C, USB | — |
| RoHS-Status | Compliant | — |
| MSL-Level | [DATA_NEEDED: MSL level] | — |
| Manufacturer | — | NXP Semiconductors |
| Product Type | — | 32-bit ARM Cortex-M0+ microcontroller |
| Product Family | — | Kinetis KL2 |
| Maximum CPU Frequency | — | 48 MHz |
| Flash Memory | — | 32 KB (32K x 8) |
| Core | — | ARM Cortex-M0+ |
| Bit Width | — | 32-bit |
| USB Connectivity | — | USB 2.0 |
| Crystal-Less USB Operation | — | Supported |
| Operating Supply Levels | — | 1.8 V, 2.5 V, or 3.3 V |
| Shipping Format | — | Tray |
| Lebenszyklusstatus | — | Active |
| RAM | — | [DATA_NEEDED: RAM capacity] |
| EEPROM | — | [DATA_NEEDED: EEPROM capacity] |
| Betriebstemperaturbereich | — | [DATA_NEEDED: operating temperature range] |
| RoHS Compliance | — | [DATA_NEEDED: RoHS compliance statement] |
| REACH Compliance | — | [DATA_NEEDED: REACH compliance statement] |