Mirrors/avrdude
1
0
Fork 0
mirror of https://github.com/avrdudes/avrdude.git synced 2026-06-02 09:46:34 +03:00
Code Issues Packages Projects Releases Wiki Activity

Extend documentation of classic-part usersig memory

Browse Source
This commit is contained in:
Stefan Rueger
2023-07-14 14:38:13 +01:00
parent 532bd01f66
commit edac02ff6a
2 changed files with 20 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
src/avrdude.1
View File

@@ -759,10 +759,17 @@ Low fuse byte
.It lock
Lock byte
.It usersig
Three extra flash pages for firmware settings in some parts; this memory
is not erased during a chip erase. -U programming can only write 0s not
1s, so 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
Three extra flash pages for firmware settings; this memory is not erased
during a chip erase. Only some classic parts, ATmega128RFA1 and
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
.El
.Pp
ATxmega devices have the following memory types in addition to eeprom, flash, signature and lock:

13
src/doc/avrdude.texi
View File

@@ -804,10 +804,15 @@ High fuse byte
@item lfuse
Low fuse byte
@item usersig
Three extra flash pages for firmware settings in some parts; this memory
is not erased during a chip erase. @code{-U} programming can only write
@code{0}s not @code{1}s, so usersig needs to be erased before a file can
be uploaded to this memory region, e.g., using @code{-T "erase usersig" -U
Three extra flash pages for firmware settings; this memory is not erased
during a chip erase. Only some classic parts, ATmega128RFA1 and
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. AVRDUDE offers JTAG
programming of classic-part usersig memories. As with all flash-type
memories the @code{-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 @code{-T "erase usersig" -U
usersig:w:parameters.hex:i}
@end table