[U-Boot-Users] storing hush scripts
Hello,
Is there an alternative to store hush scripts, other than in an environment variable? Could you please give details on how it works?
regards,
Carlos Mitidieri
Is there an alternative to store hush scripts, other than in an environment variable? Could you please give details on how it
works?
Infact, use (abuse) of environment variables to store the scripts is strongly discouraged. Yes, you can download the script at run time using UART/TFTP. The script needs a valid header to work, for details see the 'mkimage' utility present in the 'tools' directory. You will have to add header to the script using this utility and then download it. Also, refer to the details of 'autoscr' command.
-- Ajay
In message 040401c707e4$90921860$561fa8c0@pcajain you wrote:
Infact, use (abuse) of environment variables to store the scripts is strongly discouraged.
Who says so? I strongly disagree.
Best regards,
Wolfgang Denk
Infact, use (abuse) of environment variables to store the scripts is strongly discouraged.
Who says so? I strongly disagree.
Refering to the text below:
CONFIG_EXTRA_ENV_SETTINGS: Define this to contain any number of null terminated strings (variable = value pairs) that will be part of the default environment compiled into the boot image. Warning: This method is based on knowledge about the internal format how the environment is stored by the U-Boot code. This is NOT an official, exported interface! Although it is unlikely that this format will change soon, there is no guarantee either. You better know what you are doing here. Note: overly (ab)use of the default environment is discouraged. Make sure to check other ways to preset the environment like the autoscript function or the boot command first.
Therfore, can we not interptet that use (abuse) is discouraged?
-- Ajay
On Wed, 15 Nov 2006 12:07:27 +0530 "Ajay Jain" ajay050@gmail.com wrote:
Infact, use (abuse) of environment variables to store the scripts is strongly discouraged.
Who says so? I strongly disagree.
Refering to the text below:
here. Note: overly (ab)use of the default environment is discouraged. Make sure to check other ways to preset the environment
The key word here is ....... ^default^. The comment is for the specific C macro to setup the default env in the compiled image. I used it to create some standard scripts for a standard devel setup on many boards at once.
To create and run "saveenv" to store any scripts you want on a specific board is just fine.
In message 04fe01c70880$88987f40$561fa8c0@pcajain you wrote:
Refering to the text below:
CONFIG_EXTRA_ENV_SETTINGS: Define this to contain any number of null
...
guarantee either. You better know what you are doing here. Note: overly (ab)use of the default environment is discouraged. Make sure to
^^^^^^^
check other ways to preset the environment like the autoscript function or the boot command first.
Therfore, can we not interptet that use (abuse) is discouraged?
The text only warns not to overload trhe DEFAULT environment.
Best regards,
Wolfgang Denk
Hello!
cam@sysgo.com schrieb:
Is there an alternative to store hush scripts, other than in an environment variable? Could you please give details on how it works?
mkimage (on development host) and autoscr (on U-Boot target) are your friendd.
With best regards Andreas Schweigstill
In message 1163503648.4559a820a36b6@www.sysgo.com you wrote:
Is there an alternative to store hush scripts, other than in an environment variable? Could you please give details on how it works?
Use a script image. Please RTFM.
Best regards,
Wolfgang Denk
participants (6)
-
Ajay Jain -
Andreas Schweigstill -
Andrew -
cam＠sysgo.com -
Tolunay Orkun -
Wolfgang Denk