
Kramer Electronics Ltd.
KDS-EN6, KDS-DEC6 - Astparam Configuration API
3
Astparam Configuration API
Overview
KDS-6 firmware includes many configurable features. Most of the configuration are done using
the “Configuration API” called astparam. astparam is the console command to access these
system configurations.
astparam can be saved in flash ROM, so that system configuration is not lost when the system
loses power. Typical applications of astparam are:
•Enable/disable firmware features like serial over IP or video wall.
•Configure factory default firmware features on a production line.
•Prepare an SPI flash image for production, including default astparam settings.
•Enable/Disable firmware features on end customer side.
The format of astparam is a key=value string pair. For example, a astparam:
“en_video_wall=y” means astparam key “en_video_wall”’s value is “y”. Both “key” and “value”
are ANSI string and case sensitive. The firmware decides how to use it.
Note: The firmware does not validate the astparam. So, any type error could cause
unexpected results. The advantage is that a user can add any astparam key/value pair, even if
KDS-6’s reference firmware doesn’t need it. Both RO and RW astparams can be modified or
even removed.
The firmware reserves two flash partitions for system configuration. One is read only (RO) the
other is read-write (RW).
Note: BOTH ‘RO’ and ‘RW’ partitions are actually read/writable. Their usage is just defined
differently.
The firmware treats the setting in the RO partition as the system’s factory default settings. It is
recommended to save non-factory default changes in the RW partition (including the random
ethaddr). When firmware boots up, it takes astparam in the following priority order: RW > RO >
firmware default. Firmware uses the value in RW if the astparam exists. If the astparam is not
available in RW partition, then the value in RO partition is used. Firmware hard coded value is
used only when the astparam doesn’t exist in both RO and RW partition.
When the firmware starts up, both RO and RW configurations are read from flash and saved in
RAM.
Note: All configuration modifications are saved in RAM until the "astparam save [ro]"
command is called.