PIC32MX564F064LT-I/PT - 80MHz 64KB Flash MCU w/ USB & CAN | Microchip
Référence : PIC32MX564F064LT-I/PT ✓ Actif| Qté | Prix unitaire | Total |
|---|---|---|
| 1 | $5.78 | $5,78 |
| 10 | $5.2 | $52,00 |
| 100 | $4.62 | $462,00 |
| 500 | $4.1 | $2 050,00 |
| 1 000 | $3.65 | $3 650,00 |
PIC32MX564F064LT-I/PT Présentation
A 32-bit microcontroller (MCU) is a single-chip computer that integrates a CPU core, program and data memory, and configurable peripherals around a unified internal bus. The PIC32MX5 family specifically belongs to the MIPS32 M4K processor lineage, sits within the broader PIC32 family of 32-bit PIC microcontrollers, and is part of Microchip Technology's microcontroller portfolio. Compared with 8-bit/16-bit MCUs, 32-bit parts offer significantly higher MIPS per mW, larger linear address space, and richer peripheral integration for connected embedded systems.
Key features of the PIC32MX564F064LT-I/PT include USB 2.0 full-speed On-The-Go (OTG) with integrated transceiver, CAN 2.0B active, Parallel Master Port (PMP) for external bus memory or graphics, I2S audio interface, up to 53 general-purpose I/O, and CTMU for capacitive touch / mTouch sensing. Industrial-grade -40C to +85C operation and 3.3V single-supply operation simplify power-tree design. Code protection and secure memory partitions protect firmware IP.
The MIPS32 M4K core implements a 5-stage pipeline with single-cycle multiply and hardware divide, supported by a configurable prefetch cache and 4-channel DMA that offloads peripheral-to-memory transfers. Dedicated peripherals such as the USB OTG controller and CAN module include DMA hooks, allowing sustained USB throughput and CAN traffic without CPU intervention - critical for real-time and connected designs.
Typical applications include USB peripherals (HID, CDC, MSD, audio class), CAN-connected industrial nodes (sensor aggregation, motor control, building automation), embedded HMI with graphics, and general-purpose connected IoT endpoints. The integrated USB and CAN peripherals eliminate external bridge ICs, reducing BOM and board area.
When designing with this part, observe the 3.3V supply requirement, provide adequate decoupling (0.1 uF + bulk), and follow Microchip's recommended PCB layout for the TQFP-100 exposed-pad variant if used. For migration to a lower-power PIC32MX1/2/3/4/5 series, verify peripheral differences in MPLAB X IDE before porting.
This page synthesizes distributor pricing, drop-in same-package alternatives, and design notes drawn from the manufacturer datasheet and reference designs, packaged for engineers selecting the PIC32MX564F064LT-I/PT for new designs or replacements.
Alternatives de remplacement direct pour PIC32MX564F064LT-I/PT — même boîtier, compatible broche à broche. Les références à boîtier différent nécessitant une retouche du PCB sont exclues.
Variantes de cette série
Modèles de la même série directement compatibles avec PIC32MX564F064LT-I/PT (même facteur de forme et même empreinte) — différant par ADC, Operating Temperature, USB, MSL Level, Package.
Outil de comparaison rapide — sélectionnez des références alternatives pour une comparaison côte à côte :
PIC32MX564F064L-I/PT
✅ Remplacement direct✓ En stock
$4.85 / unité
Voir la fiche technique →PIC32MX564F128LT-I/PT
✅ Remplacement direct✓ En stock
$4.78 / unité
Voir la fiche technique →PIC32MX564F064LT-I/PF
✅ Remplacement direct ⚠️ Spécifications non vérifiées✓ En stock
$5.8 / unité
Voir la fiche technique →PIC32MX470F512LT-I/PT
✅ Remplacement direct✓ En stock
$5.84 / unité
Voir la fiche technique →PIC32MX460F512L-80I/PT
✅ Remplacement direct ⚠️ Spécifications non vérifiées✓ En stock
$6.05 / unité
Voir la fiche technique →PIC32MX564F064LT-I/PT Valeurs maximales et caractéristiques électriques
| Core Architecture | MIPS32 M4K |
| Core Size | 32-bit Single-Core |
| Max CPU Clock | 80 MHz |
| Program Memory (Flash) | 64 KB (64K x 8) |
| RAM | 32 KB (32K x 8) |
| Operating Voltage | 3.3 V (2.3V-3.6V core range, per family datasheet) |
| Number of I/O | 53 |
| Boîtier / Format | 100-TQFP (12x12 mm) |
| Type de montage | Surface Mount |
| USB | USB 2.0 Full-Speed OTG with integrated transceiver |
| CAN | CAN 2.0B active |
| DMA Channels | 4 |
| ADC | 10-bit, 1 Msps, up to 16 channels |
| Timers | 5 x 16-bit |
| Température de fonctionnement | -40C to +85C (industrial) |
| Packaging | Tape & Reel (TR) |
| Series | PIC32MX564F064L |
| Connectivity | USB, CAN, I2C, SPI, UART, I2S, PMP |
| Niveau MSL | 3 (per JEDEC J-STD-020) |
| Statut RoHS | Compliant |
Configuration des broches de PIC32MX564F064LT-I/PT
| Broche 1 | RG15 — GPIO RG15 / SDA2 (I2C2 data) |
| Broche 2 | VDD — Supply voltage (3.3V) |
| Broche 3 | RA0 — GPIO RA0 / PGED3 (programming data) |
| Broche 4 | RA1 — GPIO RA1 / PGEC3 (programming clock) |
| Broche 5 | RB0 — GPIO RB0 / AN0 (ADC input) |
| Broche 6 | RB1 — GPIO RB1 / AN1 (ADC input) |
| Broche 7 | RB2 — GPIO RB2 / AN2 (ADC input) |
| Broche 8 | RB3 — GPIO RB3 / AN3 (ADC input) |
| Broche 9 | RB4 — GPIO RB4 / AN4 (ADC input) |
| Broche 10 | RB5 — GPIO RB5 / AN5 (ADC input) |
| Broche 11 | RB6 — GPIO RB6 / AN6 / PGEC2 |
| Broche 12 | RB7 — GPIO RB7 / AN7 / PGED2 |
| Broche 13 | RB8 — GPIO RB8 / AN8 |
| Broche 14 | RB9 — GPIO RB9 / AN9 |
| Broche 15 | RB10 — GPIO RB10 / AN10 |
| Broche 16 | RB11 — GPIO RB11 / AN11 |
| Broche 17 | VSS — Ground |
| Broche 18 | RB12 — GPIO RB12 / AN12 |
| Broche 19 | RB13 — GPIO RB13 / AN13 |
| Broche 20 | RB14 — GPIO RB14 / AN14 |
| Broche 21 | RB15 — GPIO RB15 / AN15 |
| Broche 22 | VSS — Ground |
| Broche 23 | RC0 — GPIO RC0 |
| Broche 24 | RC1 — GPIO RC1 |
| Broche 25 | RC2 — GPIO RC2 |
| Broche 26 | VDD — Supply voltage (3.3V) |
| Broche 27 | RC3 — GPIO RC3 |
| Broche 28 | RC4 — GPIO RC4 |
| Broche 29 | RC5 — GPIO RC5 |
| Broche 30 | RC6 — GPIO RC6 |
| Broche 31 | RC7 — GPIO RC7 |
| Broche 32 | RC8 — GPIO RC8 |
| Broche 33 | RC9 — GPIO RC9 |
| Broche 34 | VSS — Ground |
| Broche 35 | RD0 — GPIO RD0 |
| Broche 36 | RD1 — GPIO RD1 |
| Broche 37 | RD2 — GPIO RD2 |
| Broche 38 | RD3 — GPIO RD3 |
| Broche 39 | RD4 — GPIO RD4 |
| Broche 40 | RD5 — GPIO RD5 |
| Broche 41 | RD6 — GPIO RD6 |
| Broche 42 | RD7 — GPIO RD7 |
| Broche 43 | RD8 — GPIO RD8 |
| Broche 44 | VDD — Supply voltage (3.3V) |
| Broche 45 | RD9 — GPIO RD9 |
| Broche 46 | RD10 — GPIO RD10 |
| Broche 47 | RD11 — GPIO RD11 |
| Broche 48 | RD12 — GPIO RD12 |
| Broche 49 | RD13 — GPIO RD13 |
| Broche 50 | RD14 — GPIO RD14 |
| Broche 51 | RD15 — GPIO RD15 |
| Broche 52 | VSS — Ground |
| Broche 53 | RE0 — GPIO RE0 / PMD0 |
| Broche 54 | RE1 — GPIO RE1 / PMD1 |
| Broche 55 | RE2 — GPIO RE2 / PMD2 |
| Broche 56 | RE3 — GPIO RE3 / PMD3 |
| Broche 57 | RE4 — GPIO RE4 / PMD4 |
| Broche 58 | RE5 — GPIO RE5 / PMD5 |
| Broche 59 | RE6 — GPIO RE6 / PMD6 |
| Broche 60 | RE7 — GPIO RE7 / PMD7 |
| Broche 61 | VDD — Supply voltage (3.3V) |
| Broche 62 | RF0 — GPIO RF0 |
| Broche 63 | RF1 — GPIO RF1 |
| Broche 64 | RF2 — GPIO RF2 |
| Broche 65 | RF3 — GPIO RF3 |
| Broche 66 | RF4 — GPIO RF4 |
| Broche 67 | RF5 — GPIO RF5 |
| Broche 68 | RF6 — GPIO RF6 / U1RTS |
| Broche 69 | RF7 — GPIO RF7 / U1CTS |
| Broche 70 | VSS — Ground |
| Broche 71 | RF8 — GPIO RF8 / U2RTS |
| Broche 72 | RF9 — GPIO RF9 / U2CTS |
| Broche 73 | RG0 — GPIO RG0 |
| Broche 74 | RG1 — GPIO RG1 |
| Broche 75 | RG2 — GPIO RG2 / D+ (USB) |
| Broche 76 | RG3 — GPIO RG3 / D- (USB) |
| Broche 77 | RG6 — GPIO RG6 |
| Broche 78 | RG7 — GPIO RG7 |
| Broche 79 | RG8 — GPIO RG8 |
| Broche 80 | RG9 — GPIO RG9 |
| Broche 81 | VSS — Ground |
| Broche 82 | VDD — Supply voltage (3.3V) |
| Broche 83 | RA2 — GPIO RA2 |
| Broche 84 | RA3 — GPIO RA3 |
| Broche 85 | RA4 — GPIO RA4 |
| Broche 86 | RA5 — GPIO RA5 |
| Broche 87 | RA6 — GPIO RA6 / TRCLK |
| Broche 88 | RA7 — GPIO RA7 / TRDAT |
| Broche 89 | RA8 — GPIO RA8 |
| Broche 90 | RA9 — GPIO RA9 |
| Broche 91 | RA10 — GPIO RA10 |
| Broche 92 | RA11 — GPIO RA11 |
| Broche 93 | RA12 — GPIO RA12 |
| Broche 94 | RA13 — GPIO RA13 |
| Broche 95 | RA14 — GPIO RA14 |
| Broche 96 | RA15 — GPIO RA15 |
| Broche 97 | VSS — Ground |
| Broche 98 | RC12 — GPIO RC12 |
| Broche 99 | RC13 — GPIO RC13 |
| Broche 100 | RC14 — GPIO RC14 |
Applications typiques
PIC32MX564F064LT-I/PT convient pour 6 applications: USB Human Interface Device (HID), CAN-Based Industrial Sensor Node, Embedded Graphical HMI Controller, USB-to-CAN Bridge Gateway, Portable Data Logger with USB, Connected IoT Edge Node (USB/CAN).
USB Human Interface Device (HID)
The PIC32MX564F064LT-I/PT's integrated USB 2.0 Full-Speed OTG controller with on-chip transceiver is ideal for USB HID peripherals such as keyboards, mice, custom input controllers, and industrial keypads. At 80 MHz the M4K core services HID report generation without taxing USB bandwidth, while the 4-channel DMA offloads endpoint transfers, leaving CPU headroom for application logic. With 64 KB Flash it fits HID stacks plus custom firmware; with 53 I/O it can scan matrix keypads or drive LEDs directly. Pair it with the MCP2200 or USBLC6-2SC6 for isolated/compliant designs, and use the Microchip Harmony USB stack for production-ready class drivers.
Recommandé
CAN-Based Industrial Sensor Node
The PIC32MX564F064LT-I/PT integrates CAN 2.0B active with hardware acceptance filters and DMA hooks, making it well-suited for industrial sensor nodes on a CAN/CANopen or J1939 bus. The 80 MHz core runs the CAN stack and 10-bit ADC sampling without bottleneck; the 4-channel DMA moves ADC samples directly to memory, leaving the CPU free for filtering. With 53 I/O it can interface SPI/analog sensors (temperature, pressure, flow) and drive actuators. Industrial-grade -40C to +85C operation matches factory floor requirements. Add a TJA1050 or MCP2551 CAN transceiver, ISO 1050 for isolation, and 120-ohm termination as required by the bus topology.
Recommandé
Embedded Graphical HMI Controller
With its Parallel Master Port (PMP) capable of driving external TFT displays up to 8-bit parallel, and the I2S peripheral for audio feedback, the PIC32MX564F064LT-I/PT is well matched to entry-level embedded HMI panels. The 53 I/O pins provide spare capacity for capacitive touch sensing via the CTMU peripheral, eliminating a dedicated touch controller. The 80 MHz MIPS core comfortably runs lightweight graphics libraries (legato, MPLAB Harmony Graphics) for menus and gauges. Use a 3.3V TFT with integrated controller (e.g., HX8347-I based), and pair with the PIC32MX5 family graphics examples for fast HMI prototyping.
Recommandé
USB-to-CAN Bridge Gateway
A natural application for the PIC32MX564F064LT-I/PT is a USB-to-CAN bridge gateway: USB 2.0 FS OTG on one side, CAN 2.0B active on the other, with the M4K core handling protocol translation. Engineers use this topology for laptop-based vehicle diagnostics, factory-floor PC tools, and lab instrumentation. The 64 KB Flash fits the USB CDC + CAN stack with margin for vendor commands; 32 KB RAM is adequate for buffers. Reference firmware is available in the Microchip Harmony USB Device + CAN library, and pair with MCP2515 (external CAN) or use the on-chip CAN for simpler designs.
Recommandé
Portable Data Logger with USB
The PIC32MX564F064LT-I/PT's combination of 32 KB RAM, 10-bit 1 Msps ADC, USB 2.0 FS OTG, and 53 I/O fits portable USB data loggers. Sample sensors at up to 1 Msps into RAM (with DMA moving samples directly to memory), then dump the buffer over USB to a host PC. The 64 KB Flash holds the USB MSC class driver and logger application. Industrial temperature range enables outdoor/vehicle deployments. Add a Li-ion charger (MCP73831) and an SPI FRAM (FM25V02) for non-volatile storage; the 53 I/O can monitor multiple sensor channels.
Recommandé
Connected IoT Edge Node (USB/CAN)
For IoT edge nodes requiring both USB connectivity (configuration/update port) and CAN (backhaul to vehicle/industrial bus), the PIC32MX564F064LT-I/PT offers a single-chip solution. The 4-channel DMA lets the MCU handle concurrent USB traffic (e.g., MQTT-over-USB, OTA updates) while sampling CAN messages for local processing. The industrial -40C to +85C range supports harsh environments. With 64 KB Flash the device fits TLS-over-USB or a small MQTT client plus the CAN driver; consider PIC32MX470F512LT-I/PT (512 KB Flash) when running WolfSSL or richer TCP/IP stacks.
Recommandé
Récapitulatif des produits recommandés
Données de référence d'ingénierie pour PIC32MX564F064LT-I/PT — comparaison, recommandations de conception et informations de conformité.
Guide de sélection
Comparaison avec les alternatives
| Paramètre | Ce produit | PIC32MX564F064L-I/PT | PIC32MX564F128LT-I/PT | PIC32MX564F064LT-I/PF | PIC32MX470F512LT-I/PT | PIC32MX460F512L-80I/PT |
|---|---|---|---|---|---|---|
| Package | 100-TQFP (12x12 mm) | 100-TQFP (12x12 mm) - same | 100-TQFP (12x12 mm) - same | 100-TQFP (12x12 mm) - same | 100-TQFP (12x12 mm) - same | 100-TQFP (12x12 mm) - same |
| Brand | Microchip Technology | Microchip Technology | Microchip Technology | Microchip Technology | Microchip Technology | Microchip Technology |
| Core Architecture | MIPS32 M4K, 32-bit | MIPS32 M4K, 32-bit - same | MIPS32 M4K, 32-bit - same | MIPS32 M4K, 32-bit - same | MIPS32 M4K, 32-bit - same | MIPS32 M4K, 32-bit - same |
| Max CPU Clock | 80 MHz | 80 MHz | 80 MHz | 80 MHz | 120 MHz | 80 MHz |
| Flash | 64 KB | 64 KB | 128 KB | 64 KB | 512 KB | 512 KB |
| RAM | 32 KB | 32 KB | 32 KB | 32 KB | 64 KB | 32 KB |
| USB | USB 2.0 FS OTG | USB 2.0 FS OTG | USB 2.0 FS OTG | USB 2.0 FS OTG | USB 2.0 FS OTG | USB 2.0 FS (verify variant) |
| CAN | CAN 2.0B active | CAN 2.0B active | CAN 2.0B active | CAN 2.0B active | CAN 2.0B active | CAN 2.0B active |
| Operating Temperature | -40C to +85C (I grade) | -40C to +85C (I grade) | -40C to +85C (I grade) | -40C to +85C (I grade) | -40C to +85C (I grade) | -40C to +85C (I grade) |
| Approx. Unit Price @ qty 1 | $5.78 | ~$5.65 (tray variant) | ~$6.20 | ~$5.78 | ~$7.40 | ~$6.50 |
Principaux différenciateurs
- Tape & Reel shipping format optimized for SMT assembly (vs PIC32MX564F064L-I/PT)
- Doubles program memory headroom at same footprint (vs PIC32MX564F128LT-I/PT)
- Highest Flash and 50% faster core in the same package (vs PIC32MX470F512LT-I/PT)
- Migration path with larger memory, no board change (vs PIC32MX460F512L-80I/PT)
Notes de conception
The PIC32MX564F064LT-I/PT operates from a single 3.3V supply (2.3V-3.6V core range, per the family datasheet). Place a 0.1 uF decoupling capacitor close to every VDD pin, plus a 4.7 uF bulk capacitor near the supply input. The MCU's core runs at 80 MHz; switching noise can couple into analog rails, so place an additional ferrite bead + 10 uF cap on AVDD if you are sampling the 10-bit ADC at >500 ksps.
Route the USB D+ and D- lines (RG2/RG3) as a 90-ohm differential pair with matched length, kept short and isolated from noisy digital traces. Place the 48 MHz USB reference clock source as close to the MCU as possible and route it over a continuous ground reference. For CAN bus signals, place the MCP2551/ISO1050 transceiver near the bus connector and route the CAN_H/CAN_L pair as a 120-ohm differential.
Program/debug pins PGEDx/PGECx (RA0/RA1, RB6/RB7) must be accessible for MPLAB ICD/PICkit; do not route high-speed signals on these pins without bypass. If using trace, route TRCLK/TRDAT (RA6/RA7) to a header. The Parallel Master Port (PMP) pins PMD0-PMD7 on RE0-RE7 should be length-matched if driving a TFT directly to avoid skew.
Estimated: total Flash endurance is approximately 1000 erase/write cycles per row before wear. Implement wear-leveling if you plan to update configuration frequently. Do not exceed 3.6V on any VDD pin or 5V on any digital I/O - the part is NOT 5V tolerant. When migrating firmware from PIC32MX3/4 to PIC32MX5/6/7, recheck peripheral library versions because PPS pin mappings differ between sub-families.
Estimated: at maximum 80 MHz core clock and full peripheral activity, the PIC32MX564F064LT-I/PT draws approximately 70-90 mA from 3.3V (~250-300 mW). The 100-pin TQFP theta_JA is approximately 39 C/W (with standard JEDEC 4-layer test board), giving a ~10-12 C temperature rise - well within the industrial range. For forced-air or enclosed housings, verify with a thermocouple measurement.
Informations de conformité
RoHS and REACH compliant per Microchip product environmental compliance program. Halogen-free per Microchip policy. Not AEC-Q100 qualified - this is an industrial-grade MCU, not automotive-grade; for automotive designs use AEC-Q100-qualified variants from Microchip's PIC32 family.
