Remove section about memories from avrdude.1

This section breaks the flow of the man page on the options.
It is reasonable to refer to a longer manual for that.
This commit is contained in:
Stefan Rueger
2024-08-23 23:17:42 +01:00
parent 3e9672481c
commit a9c692ed71

View File

@@ -808,161 +808,8 @@ of that by erasing pages before programming them unless -e (chip erase) or
absence of the -e chip erase option any ATxmega or UPDI flash pages not
affected by the programming will retain their previous content.
.Pp
Classic devices may have the following memories in addition to eeprom, flash, signature and lock:
.Bl -tag -width " calibration" -compact
.It calibration
One or more bytes of RC oscillator calibration data
.It efuse
Extended fuse byte
.It fuse
Fuse byte in devices that have only a single fuse byte
.It hfuse
High fuse byte
.It lfuse
Low fuse byte
.It lock
Lock byte
.It prodsig
Signature, calibration byte(s) and serial number in a small read-only memory,
which is only documented to be available for ATmega324PB, ATmega328PB,
ATtiny102 and ATtiny104;
.Nm
generally tries to make this memory available, also for parts where it is
not documented, but not all programmers may be able to read this memory
.It sigrow
Memory alias for prodsig
.It sernum
The serial number part of prodsig; owing to scarce documentation this may not
actually turn out to be a serial number or be readable by some programmers
.It usersig
Three extra flash pages for firmware settings; this memory is not erased
during a chip erase. Only some classic parts,
ATmega(64|128|256|644|1284|2564)RFR2, have a usersig memory. Usersig is
different to flash in the sense that it can neither be accessed with ISP
serial programming nor written to by bootloaders;
.Nm
offers JTAG programming of classic-part usersig memories. As with all
flash-type memories the -U option can only write 0-bits but not 1-bits.
Hence, usersig needs to be erased before a file can be uploaded to this
memory region, e.g., using -T "erase usersig" -U
usersig:w:parameters.hex:i
.It io
Volatile register memory; it cannot be accessed by external programming
methods only by bootloaders, which has limited use unless the bootloader
jumps to the application directly, i.e., without a WDT reset
.It sram
Volatile RAM memory; like io it cannot be accessed by external programming
.El
.Pp
ATxmega devices have the following memories in addition to eeprom, flash, signature and lock:
.Bl -tag -width "calibration" -compact
.It application
Application flash area
.It apptable
Application table flash area
.It boot
Boot flash area
.It calibration
An area of 4 (ATxmega-A series) or 5 bytes (ATxmega-B/C/D/E) with
oscillator calibration values; this is a sub-memory of prodsig
.It fuses
A logical memory of 7 bytes containing all fuseX of a part, which can be
used to program all fuses at the same time; note that some fuse bytes will
be reserved, though
.It fuse0
A.k.a. jtaguid: JTAG user ID for some devices
.It fuse1
Watchdog configuration
.It fuse6
Fault detection action configuration TC4/5 for ATxmega E series parts
.It fuse Ns Em N
Other fuse bytes of ATxmega devices, where
.Em N
is 2, 4 or 5, for system configuration
.It prodsig
The production signature row is a read-only memory section for factory
programmed data such as the calibration values for oscillators or analogue
modules; it also contains a serial number that consists of the production
lot number, wafer number and wafer coordinates for the part
.It sernum
Serial number with a unique ID for the part consisting of 10 bytes; these
are part of the prodsig memory above
.It sigrow
Memory alias for prodsig
.It tempsense
A two-byte memory, which is located within prodsig; it contains a 12-bit
temperature sensor calibration value
.It usersig
Additional flash memory page that can be used for firmware settings; this
memory is not erased during a chip erase
.It io
Volatile register memory;
.Nm
can read this memory but not write to it using external programming
.It sram
Volatile RAM memory; cannot be usefully accessed by external programming
.El
.Pp
Modern 8-bit AVR devices have the following memories in addition to eeprom, flash, signature and lock:
.Bl -tag -width "calibration" -compact
.It fuse0
A.k.a. wdtcfg: watchdog configuration
.It fuse1
A.k.a. bodcfg: brownout detection configuration
.It fuse2
A.k.a. osccfg: oscillator configuration
.It fuse4
A.k.a. tcd0cfg (not all devices): timer counter type D configuration
.It fuse5
A.k.a. syscfg0: system configuration 0
.It fuse6
A.k.a. syscfg1: system configuration 1
.It fuse7
A.k.a. append or codesize: either the end of the application code section or the code size in blocks of 256/512 bytes
.It fuse8
A.k.a. bootend or bootsize: end of the boot section or the boot size in blocks of 256/512 bytes
.It fusea
A.k.a. pdicfg: configures/locks updi access; it is the only fuse that consists of two bytes
.It fuses
A logical memory of up to 16 bytes containing all fuseX of a part, which can be
used to program all fuses at the same time
.It osc16err
Two bytes typically describing the 16 MHz oscillator frequency error at 3 V and 5 V, respectively
.It osc20err
Two bytes typically describing the 20 MHz oscillator frequency error at 3 V and 5 V, respectively
.It osccal16
Two oscillator calibration bytes for 16 MHz
.It osccal20
Two oscillator calibration bytes for 20 MHz
.It prodsig
Read-only memory section for factory programmed data such as the
signature, calibration values and serial number
.It sigrow
Memory alias for prodsig
.It sernum
Serial number with a unique ID for the part (10 or 16 bytes)
.It tempsense
Temperature sensor calibration values
.It bootrow
Extra page of memory that is only accessible by the MCU in bootloader
code; UDPI can read and write this memory only when the device is
unlocked
.It userrow
Extra page of EEPROM memory that can be used for firmware settings; this
memory is not erased during a chip erase; UPDI cannot read this memory
when the device is locked
.It sib
Special system information block memory with information about AVR family, chip revision etc.
.It io
Volatile register memory;
.Nm
can program this memory but this is of limited utility because anything
written to the io memory will be undefined or lost after reset; writing to
individual registers in the terminal can still be used, e.g., to test I/O
ports
.It sram
Volatile RAM memory; can be read and written but contents will be lost after reset
.El
For a list of all known memories, please refer to the full documentation, eg,
.Li https://github.com/avrdudes/avrdude/blob/main/avrdude.pdf
.Pp
The
.Ar op