NXP Kinetis KL0 series, ARM Cortex-M0+ core at 48MHz, 32KB Flash, 4KB RAM, 14-channel 12-bit A/D and 1-channel 12-bit D/A converters, 28 I/O, surface-mount 32-HVQFN (5×5mm) wettable flank, tray, -40°C to 105°C operating temperature, ROHS3 compliant.
- 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 | Kinetis KL0 |
| Mounting type | Surface Mount, Wettable Flank |
| Oscillator type | Internal |
| Program memory type | FLASH |
| Voltage - supply (Vcc (Vdd)) | 1.71V ~ 3.6V |
| Operating temperature | -40°C ~ 105°C (TA) |
| Speed | 48MHz |
| Package | Tray |
| RAM size | 4K x 8 |
| Core size | 32-Bit Single-Core |
| Peripherals | Brown-out Detect/Reset, DMA, LVD, POR, PWM, WDT |
| Connectivity | I²C, SPI, UART/USART |
| Number of i (O) | 28 |
| Core processor | ARM® Cortex®-M0+ |
| Case | 32-VFQFN Exposed Pad |
| Data converters | A/D 14x12b; D/A 1x12b |
| Program memory size | 32KB (32K x 8) |
Frequently asked questions
Is the MKL05Z32VFM4 drop-in compatible with the MKL05Z16 in the same 32-HVQFN package?
Mechanically yes — same pinout and package. Flash size does not affect pinout. The step up from 16KB to 32KB Flash requires only a firmware rebuild against the correct device header; no schematic or layout change.
Are any of the 28 GPIOs 5V-tolerant for direct connection to 24V industrial sensors?
No — the I/O voltage domain is tied to VDD at 1.71V to 3.6V. KL-series GPIOs are not 5V-tolerant on this supply range. Interfacing to 24V signals requires external level-shifting or clamping.
Can the 14-channel 12-bit ADC run continuously via DMA while PWM outputs update independently?
Structurally yes — the DMA controller moves ADC results to SRAM autonomously, and PWM runs on its own hardware timer. Bus contention under simultaneous heavy peripheral load is a function of clock configuration detailed in the device datasheet, not an architectural block.