Comment 5 for bug 1231266

Hello everyone,

Here is the u-boot env variables set on my SD card:

==========================================================
ARNDALE5250 # print
baudrate=115200
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; fi; fi; fi
bootdelay=3
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttySAC2,115200n8
ethact=asx0
ethaddr=02:8e:8f:56:16:33
loadaddr=0x42000000
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} root=${mmcroot}
mmcboot=echo Booting from mmc${mmcdev} ...; run mmcargs; bootm ${loadaddr}
mmcdev=0:2
mmcroot=/dev/mmcblk0p2 rw
preboot=usb start
stderr=serial
stdin=serial
stdout=serial
usbethaddr=02:8e:8f:56:16:33

Environment size: 731/16380 bytes
========================================================

I am attaching my boot.txt here. If everyone's boot.txt is same then the problem is not in linaro-image-tools create utility.

The env variables that Vishal shared has correct "bootcmd" but incorrect "bootargs" and the env variables shared by Botao has correct "bootargs" but incorrect "bootcmd".
But in both case the "bootcmd" does not refer to boot.scr. My "bootcmd" correctly loads and runs boot.scr.

Now, this may be because you might have used the same SD card for some other board or might have changed the env variables and did "saveenv". Flashing SD card for arndale using linaro-image-tool does not over-write the env variable section starting from 1073 to 1105 on SD card.

Solution:
The solution to this problem is to set env variables as per my env variables, particularly, bootcmd, mmcdev, loadbootscript, loaduimage, mmcboot, loadaddr and then save env variables using "saveenv" command.

Alternatively you can erase env section by following command:
# dd if=/dev/zero of=/dev/sdc seek=1073 bs=512 count=32
But even then you will have to set env variables and then saveenv. So I would suggest not to erase env variables.

Once you set env variables according to my settings and do saveenv, your subsequent boots will be successful.

Please let me know if you still face the issue

Regards,
Pranav