MCUdude
commented
1 year ago It would be really neat to have something like this. However, the table width has to be calculated by finding the longest memory name and memory size:
avrdude> part
AVR Part : ATmega4808
Serial number : 0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09
Prog. interfaces : UPDI, SPM
Flash size: : 48 kiB
EEPROM size: : 256 bytes
Memories :
| Memory: | Size: | Page size: | Read/write: |
|-----------------|-------|------------|-------------|
| fuses | 1 | 1 | R/W |
| fuse0/wdtcfg | 1 | 1 | R/W |
| fuse1/bodcfg | 1 | 1 | R/W |
| fuse2/osccfg | 1 | 1 | R/W |
| fuse5/syscfg0 | 1 | 1 | R/W |
| fuse6/syscfg1 | 1 | 1 | R/W |
| fuse7/append | 1 | 1 | R/W |
| fuse8/bootend | 1 | 1 | R/W |
| lock | 1 | 1 | R/W |
| prodsig/sigrow | 128 | 128 | R/W |
| signature | 3 | 1 | R |
| tempsense | 2 | 1 | R |
| sernum | 10 | 1 | R |
| osccal16 | 2 | 1 | R |
| osccal20 | 2 | 1 | R |
| osc16err | 2 | 1 | R |
| osc20err | 2 | 1 | R |
| data | 0 | 0 | |
| io | 4352 | 1 | R/W |
| sib | 32 | 1 | R |
| userrow/usersig | 64 | 64 | R/W |
| eeprom | 256 | 64 | R/W |
| flash | 49152 | 128 | R/W |
avrdude> part
AVR Part : ATtiny13
Prog. interfaces : ISP, SPM
Flash size: : 1 kiB
EEPROM size: : 64 bytes
Memories :
| Memory: | Size: | Page size: | Read/write: |
|-------------|-------|------------|-------------|
| eeprom | 64 | 4 | R/W |
| flash | 1024 | 32 | R/W |
| lfuse | 1 | 1 | R/W |
| hfuse | 1 | 1 | R/W |
| lock | 1 | 1 | R/W |
| signature | 3 | 1 | R |
| calibration | 2 | 1 | R |
| io | 64 | 1 | |
stefanrueger
askn37
The terminal
partcommand outputs information about the connected part. This command, however, was developed when there were only "classic" AVRs, but now we got "modern ones" (with UPDI) and Xmegas.This is the current output for a measly ATtiny13:
And this is the output for an ATmega4808:
Both contains tons of information, and most of it isn't really useful others than Avrdude developers that cares about chip erase delays and min/max write delays.
How about we redo the entire thing, and only prints "useful information" for the average enthusiast? If more detailed information are needed, use the developer options instead, or read the avrdude.conf.
Now I need to know what you guys think are "necessary information" for the
partcommand.