View Single Post
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#107
Originally Posted by Fabry View Post
I have found a bug in bootmenu generation.

I have used this profile:
Code:
ITEM_NAME="Nemo from boot.scr"
ITEM_ID="Nemo2"
ITEM_DEVICE="${INT_CARD}p1"
ITEM_FSTYPE="fat"
ITEM_USEATAG="1"
ITEM_SCRIPT="boot.scr"
to load from MyDocs my old (and working) bootscript for Nemo.

It not works and if i examine the generated menu entry, I find :
Code:
setenv bootmenu_3 'Nemo from boot.scr=
setenv mmcnum 1;
setenv mmcpart 1;
setenv mmctype fat;
setenv bootargs;
setenv atagaddr;
setenv mmckernfile;
setenv mmcinitrdfile;
setenv mmcscriptfile boot.scr;
run trymmcscriptboot;'
Error: Atag not set
This is not error I think. You are not booting kernel, but starting other u-boot script. So if you need to reuse atags from nolo, your script should set all needed variables for booting.

I checked update script and ITEM_USEATAG is relevant only for booting kernel.


... But what other people think? Should external u-boot script set all needed variables for booting? Or should only some and some should set update-bootmenu?
I think that - if user/developer/... decide to use own u-boot script for booting (not prepaired u-boot variables for kernel/initrd) it should also handle passing atags to bootm command.
 

The Following User Says Thank You to pali For This Useful Post: