[u-boot] Environment garbled after setenv?

Evgeniy Karyakin anthropophagite at gmail.com
Sun Dec 7 19:07:29 CET 2008


Hello!

    While trying to edit u-boot environment I experienced this strange 
behaviour, which, I think, is rare because nobody reported this yet. My 
U-Boot is 1.3.2-moko12 (May 9 2008 - 10:28:48).
    Initially I have menu_1 ("Boot from microSD (FAT+ext2)") as follows:

menu_1=Boot from microSD (FAT+ext2): setenv bootargs ${bootargs_base} 
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit; 
fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000

    Changing it to new one:

setenv menu_1 Boot from microSD (FAT+ext2): setenv bootargs 
glamo_mci.sd_max_clk=10000000 \$\{bootargs_base\} rootfstype=ext2 
root=/dev/mmcblk0p2 console=ttySAC2,115200 console=tty0 loglevel=4 
regular_boot rootdelay=5 \$\{mtdparts\}\; sleep 1\; mmcinit\; sleep 1\; 
fatload mmc 1 0x32000000 \$\{sd_image_name\}\; bootm 0x32000000

    Note that every special character is escaped. I'm trying to make a 
permanent boot menu for microSD invocation.
    Now it is (taken copy-paste from minicom console with the help of 
printenv):

menu_1=Boot from microSD (FAT+ext2): setenv bootargs 
glamo_mci.sd_max_clk=10000000 ${bootargs_base} rootfstype=ext2 
root=/dev/mmcblk0p2 console=ttySAC2,115200 console=tty0 loglevel=4 
regular_boot rootdelay=5 ${mtdparts}; sleep 1; mmcinit; sleep 1; fatload 
mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000

    Seems good. But selecting this menu item "Boot from microSD 
(FAT+etx2)" *on the phone* says something like:

Unknown command 'dout' - try 'help'

    Obviously it's a part of the word "stdout". How?? Other items 
selection and their subsequences:

* "Set console to USB"
   Unknown command '_image=uImage.bin' - try 'help'

* "Set console to serial"
   Unknown command '1973-nand' - try 'help'

* "Reboot" (two error lines exactly as follows!)
   Unknown command '=physman-flash:-(nor)' - try 'help'
   (factory),0x0f6a0000(rootfs)' - try 'help'

* "Power off"
   Unknown command 'actory),0x0f6a0000(rootfs)' - try 'help'

    Only plain "Boot" is working. I can boot from microSD from u-boot 
command line managing it from desktop, and NOR menu works on the phone 
as well if I didn't do any environment changes.
    I see it as environment broken and afraid to say "saveenv" which can 
make this uncertain state permanent. What can it be, have anybody seen this?




More information about the community mailing list