Table of Contents
Advertisement
It is possible to modify envionment variables and start the pre-defined scripts form the bootloader shell. It
is strongly discouraged to modify the pre-defined script variables. However, definition and execution of
user-defined script variables can be done.
Note...
Meddling with the bootloader environment variables can affect significantly
the startup sequence of the board and may cause the system to be un-bootable.
Modification of bootloader environment variables is done using the 'setenv' and 'saveenv' bootloader CLI
commands. In the following example, the new environment script variable 'bootcmdmyscript' is defined.
After that, the 'bootsource' is set to <myscript> causing the bootloader to execute <bootcmdmyscript> upon
next restart. In addition, bootdelay is increased to 10. Finally, all changes are stored into flash environment
sector.
=> setenv bootcmdmyscript 'bootp; tftpboot ${loadaddr} myimg.multi; bootm ${loadaddr}'
=> setenv bootsource myscript
=> setenv bootdelay 10
=> saveenv
Environment changes are stored in one of the redundant bootloader environment sectors. In case of failure
(e.g. power loss), the settings of the redundant sector are still available. However, the fabric default setting
is running with environment sectors erased. In this case the following startup message is displayed:
ENV: Using default environment
Any changes of the environment can be cleared using the 'clear_env' script (provided that 'clear_env' itself
was not changed):
=> run clear_env
47
Software Description
CP6930 User Guide
www.kontron.com
Advertisement
Table of Contents
