Alignment happens for groups of different values of the same configuration
property, but only when the value lables differ in length by max of 10
characters. For example:
avrdude> c su=int*
avrdude warning: (config) ambiguous; known sut_cksel int* symbols are:
- sut_cksel=intrcosc_8mhz_6ck_14ck_0ms # 2
- sut_cksel=intrcosc_128khz_6ck_14ck_0ms # 3
- sut_cksel=intrcosc_8mhz_6ck_14ck_4ms1 # 18
- sut_cksel=intrcosc_128khz_6ck_14ck_4ms1 # 19
- sut_cksel=intrcosc_8mhz_6ck_14ck_65ms # 34
- sut_cksel=intrcosc_128khz_6ck_14ck_65ms # 35
Example:
$ avrdude -c dryrun -p AVR32DA32 -t
avrdude: AVR device initialized and ready to accept instructions
avrdude: device signature = 0x1e9533 (probably avr32da32)
avrdude> c
config period=t_off # 0
config window=t_off # 0
config sleep=bod_disabled # 0
config active=bod_disabled # 0
config sampfreq=sf_128hz # 0
config lvl=bod_1v9 # 0
config clksel=oschf # 0
config eesave=eex_erased # 0
config rstpincfg=gpio # 0
config crcsel=crc16 # 0
config crcsrc=nocrc # 0b11 = 3
config sut=sut_0ms # 0
config codesize=0 # 0
config bootsize=0 # 0
config key=nolock # 0x5cc5c55c
avrdude> c active= -vv
config active=bod_disabled # 0 (brownout detection disabled)
avrdude> c sleep=3
avrdude warning: (config) assigning a reserved value (0x03) to sleep, check data sheet
avrdude> c -v sleep=
config sleep=0b11 # reserved = 3
avrdude> c sleep=bod_cont
avrdude> c -?
Syntax: config {<opts> | <property>[=<value>]}
Function: Show or change configuration properties of the part
Options:
-f show value of fuse and lock bit memories as well
-a output an initialisation script with all possible assignments
-v increase verbosity, show explanations alongside output
-h show this help message
Config alone shows all property names and current settings of the part's
hardware configuration in terms of symbolic mnemonics or values. Use
avrdude> config <property>
to show that of <property>. Wildcards or initial strings are permitted (but
not both), in which case all settings of matching properties are displayed.
avrdude> config <property>=
shows all possible values that <property> can take on with the currently
set one being the only that is not commented out. Assignments
avrdude> config <property>=<value>
modify the corresponding fuse or lock bits immediately but will normally only
take effect the next time the part is reset (see the data sheet). Value can
be a valid integer or one of the symbolic mnemonics, if known. Wildcards or
initial strings are permitted for the mnemonic, but an assignment only
happens if both the property and the name can be uniquely resolved.
It is quite possible, as is with direct writing to the underlying fuse and
lock bits, to brick a part, i.e., make it unresponsive to further programming
with the chosen programmer: here be dragons.
In fact not only lists of 0b-binary, octal, decimal and 0x-hex bytes can
be read, but also combinations of them, float numners and strings (just
like in terminal write). The immediate mode :m now can also read
terminal-type data (just be careful with preseving the quotes in the
shell through a double layer of quoting).
avrdude -U "eeprom:w:42.0,0b101010,42,0x2a,052,'*':m"
