[U-Boot] change autoboot
Newbie with question: uboot is currently configured to autoboot with "run boot_nor". In the configuration I found a variable called BOOTCOMMAND which is set to "run boot_nor". Which I now want to set it to "run prog_all_usb; run boot_nor" I then recompile everything transfer u-boot to my device and on initial startup it works but if I turn my device off and back on it and interrupt autoboot and type "printenv". The bootcmd is set back to just "run boot_nor" - what am i missing??????????????
Thanks
bundy wrote:
Newbie with question: uboot is currently configured to autoboot with "run boot_nor". In the configuration I found a variable called BOOTCOMMAND which is set to "run boot_nor". Which I now want to set it to "run prog_all_usb; run boot_nor" I then recompile everything transfer u-boot to my device and on initial startup it works but if I turn my device off and back on it and interrupt autoboot and type "printenv". The bootcmd is set back to just "run boot_nor"
- what am i missing??????????????
Thanks
Try erasing your U_Boot environment before rebooting. U-Boot wil then boot using the default environment you set up. now change the things you want changed and run saveenv
Dear bundy,
In message 22195894.post@talk.nabble.com you wrote:
uboot is currently configured to autoboot with "run boot_nor". In the configuration I found a variable called BOOTCOMMAND which is set to "run boot_nor". Which I now want to set it to "run prog_all_usb; run boot_nor" I then recompile everything transfer u-boot to my device and on initial startup it works but if I turn my device off and back on it and interrupt autoboot and type "printenv". The bootcmd is set back to just "run boot_nor"
- what am i missing??????????????
If you had bothered to read the manual you should have known that rebuilding U-Boot is not necessary for such a simple change - a simple "setenv" followed by a "saveenv" would have been all you needed.
Best regards,
Wolfgang Denk
Dear Wolfgang Denk
Sorry I was unclear in my question, its not that saveenv doesn't work as it does, it was that I was hoping to do it through the build system/configuration file.
Bundy
wd wrote:
Dear bundy,
In message 22195894.post@talk.nabble.com you wrote:
uboot is currently configured to autoboot with "run boot_nor". In the configuration I found a variable called BOOTCOMMAND which is set to "run boot_nor". Which I now want to set it to "run prog_all_usb; run boot_nor" I then recompile everything transfer u-boot to my device and on initial startup it works but if I turn my device off and back on it and interrupt autoboot and type "printenv". The bootcmd is set back to just "run boot_nor"
- what am i missing??????????????
If you had bothered to read the manual you should have known that rebuilding U-Boot is not necessary for such a simple change - a simple "setenv" followed by a "saveenv" would have been all you needed.
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "It is easier to port a shell than a shell script." - Larry Wall _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Dear bundy,
In message 22209226.post@talk.nabble.com you wrote:
Sorry I was unclear in my question, its not that saveenv doesn't work as it does, it was that I was hoping to do it through the build system/configuration file.
You can do that, too, of course. But allyou affect this way is (usually [*]) the default environment, which gets used if the normal environment gets corrupted - as long as there is a valid copy this one will be used, and the default environment will never be used.
As recommended before, you can erase or otherwise invalidate (for example, just overwrite the checksum entries) the environment to force using the default environment.
[*] An exceptions is the (not frequently used) configuration ith an "embedded" environment where the environment is part of the U-Boot image itself and will get overwritten when you install a new image.
Best regards,
Wolfgang Denk
participants (3)
-
bundy -
Pieter -
Wolfgang Denk