ATMEGA128-16AU vs ATMEGA64-16AU 비교
다음의 상세 나란히 비교: ATMEGA128-16AU 제조: Microchip Technology 및 ATMEGA64-16AU 제조: Microchip Technology. 주요 사양, 전기적 파라미터, 패키징, 수명 주기 상태, 가격 및 재고를 비교하여 설계 요구 사항에 가장 적합한 부품을 결정하십시오.
Microchip Technology
ATMEGA128-16AU - 8-Bit AVR MCU, 128KB Flash, 16MHz | Microchip
ATMEGA128-16AU ✓ 활성
사양 비교
| 파라미터 | ATMEGA128-16AU | ATMEGA64-16AU |
|---|---|---|
| 브랜드 | Microchip Technology | Microchip Technology |
| 카테고리 | Microcontrollers | Microcontrollers |
| 수명 주기 상태 | 활성 | 활성 |
| 재고 상태 | In Stock | In Stock |
| 단가 (USD) | $14.30 | $7.23 |
| Core Architecture | 8-bit AVR RISC | 8-bit AVR RISC |
| Flash Memory | 128 KB (64K x 16) In-System Programmable | — |
| SRAM | 4 KB | 4 KB |
| EEPROM | 4 KB | 2 KB |
| 최대 클록 주파수 | 16 MHz | — |
| Throughput | 16 MIPS at 16 MHz (approx. 1 MIPS per MHz) | Up to 16 MIPS at 16 MHz |
| Supply Voltage Range | 4.5 V to 5.5 V (16 MHz speed grade) | — |
| ADC | 8-channel 10-bit | 8-channel, 10-bit |
| Debug Interface | JTAG for on-chip debugging | — |
| 패키지 | 64-TQFP (14x14 mm) | 64-TQFP (14x14 mm, 0.8 mm pitch) |
| 실장 유형 | Surface Mount | Surface Mount |
| Temperature Grade | Industrial (IND TEMP) | — |
| External Memory Interface | Supported (up to 64 KB external data memory) | — |
| Serial Interfaces | 2x USART, SPI, Two-Wire Interface (I2C-compatible) | — |
| RoHS 상태 | Compliant (RoHS Y) | Compliant (GREEN) |
| MSL 레벨 | [DATA_NEEDED: MSL rating] | — |
| 동작 온도 범위 | [DATA_NEEDED: exact min/max operating temperature] | — |
| Program Memory Size | — | 64 KB Flash (32K x 16) |
| Flash Endurance | — | 10,000 write/erase cycles |
| Maximum CPU Speed | — | 16 MHz |
| General Purpose I/O Pins | — | 53 |
| General Purpose Working Registers | — | 32 |
| Operating Voltage | — | 4.5 V to 5.5 V (16 MHz); 2.7 V to 5.5 V (8 MHz) |
| Timer/Counters | — | 4 (two 8-bit, two 16-bit) with compare modes and PWM |
| USART Interfaces | — | 2 |
| Two-wire Serial Interface | — | 1 (byte oriented) |
| Real Time Counter | — | Yes (RTC) |
| 동작 온도 | — | -40 C to +85 C |
| JTAG Debug Interface | — | Yes (IEEE 1149.1 boundary-scan) |