ATMEGA128-16ANR vs ATMEGA64-16AU 비교
다음의 상세 나란히 비교: ATMEGA128-16ANR 제조: Microchip Technology 및 ATMEGA64-16AU 제조: Microchip Technology. 주요 사양, 전기적 파라미터, 패키징, 수명 주기 상태, 가격 및 재고를 비교하여 설계 요구 사항에 가장 적합한 부품을 결정하십시오.
Microchip Technology
ATMEGA128-16ANR - 8-Bit AVR MCU 128KB 16MHz TQFP-64 | Microchip (Tape & Reel)
ATMEGA128-16ANR ✓ 활성
사양 비교
| 파라미터 | ATMEGA128-16ANR | ATMEGA64-16AU |
|---|---|---|
| 브랜드 | Microchip Technology | Microchip Technology |
| 카테고리 | Microcontrollers | Microcontrollers |
| 수명 주기 상태 | 활성 | 활성 |
| 재고 상태 | In Stock | In Stock |
| 단가 (USD) | $7.44 | $7.23 |
| Core Architecture | 8-bit AVR RISC | 8-bit AVR RISC |
| Core Size | 8-bit | — |
| Max Clock Frequency | 16 MHz | — |
| Peak Throughput | 16 MIPS at 16 MHz | — |
| Flash Memory | 128 KB (64K x 16) | — |
| SRAM | 4 KB | 4 KB |
| EEPROM | 4 KB | 2 KB |
| Operating Voltage Range | 4.5 V to 5.5 V | — |
| General Purpose I/O | 53 lines | — |
| Timers/Counters | 4 with compare modes and PWM | — |
| ADC | 8-channel, 10-bit | 8-channel, 10-bit |
| USART | 2 | — |
| Communication Interfaces | 2x USART, TWI (I2C), SPI | — |
| Debug / Boundary Scan | JTAG (IEEE 1149.1 interface for on-chip debugging) | — |
| Instructions | 131 instructions, most single-cycle | — |
| 패키지 | 64-TQFP (14x14 mm) | 64-TQFP (14x14 mm, 0.8 mm pitch) |
| 실장 유형 | Surface Mount | Surface Mount |
| 동작 온도 | -40C to +85C | -40 C to +85 C |
| Working Registers | 32 general purpose | — |
| RoHS 상태 | unknown | Compliant (GREEN) |
| Program Memory Size | — | 64 KB Flash (32K x 16) |
| Flash Endurance | — | 10,000 write/erase cycles |
| Maximum CPU Speed | — | 16 MHz |
| Throughput | — | Up to 16 MIPS at 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) |
| JTAG Debug Interface | — | Yes (IEEE 1149.1 boundary-scan) |