Hello, I see some values when I do printenv These are the files on my dos partition MLO u-boot.img uEnv.txt zImage zImage-omap3-beagle-xm.dtb
This is what I have in the uEnv.txt file bootcmd="" bootfile="zImage" ethact="" loadaddr="" nandboot="" nandroot="" nandrootfstype="" nandargs="" loaduimage="" loaduimagefat="" nandboot="" mpurate="auto" bootcmd="mmc rescan ; fatload mmc 0:1 0x80300000 zImage; bootz 0x80300000" dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" optargs="consoleblank=0" console="ttyO2 console=tty0,115200n8" vram=16M saveenv printenv It appears that some of variable get written with other data ie vram I am setting to 16M but sometimes I see it set to 12M see at the end I have tried setting the variables manually and executing saveenv All the ones I don't want set setenv name and then saveenv still see the same values when I was using uImage and no this is what I used for my uEnv.txt mpurate=auto bootcmd="mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000" dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" vram=16M optargs="consoleblank=0" console="ttyO2 console=tty0,115200n8" These were the file on the dos partition MLO u-boot.img uEnv.txt uImage This was on a build on 09/21/13 Any and all help will be appreciated. Thanks U-Boot SPL 2013.07 (Oct 19 2013 - 09:14:36) OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2013.07 (Oct 19 2013 - 09:14:36) OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #158000029ff800000160a7450b02602d musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 1.800 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 480ab000 using PIO, IRQ 0 Net: usb_ether Hit any key to stop autoboot: 3 2 1 0 OMAP3 beagleboard.org # l printenv baudrate=115200 beaglerev=xMC bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run userbutton; then setenv bo otenv uEnv.txt;else setenv bootenv user.txt;fi;echo SD/MMC found on device ${mmc dev};if run loadbootenv; then echo Loaded environment from ${bootenv};run import bootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run loaduimage; then run mmcboot;fi;fi;run nandboot; bootdelay=3 bootenv=uEnv.txt bootfile=uImage.beagle buddy=none camera=none console=ttyO2,115200n8 defaultdisplay=dvi dieid#=158000029ff800000160a7450b02602d dvimode=640x480MR-16@60 ethact=usb_ether importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $ filesize loadaddr=0x80200000 loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv} loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz loaduimage=ext2load mmc ${mmcdev}:2 ${loadaddr} /boot/uImage loaduimagefat=fatload mmc ${mmcdev} ${loadaddr} uImage mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=$ {buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_dis p=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} mmcdev=0 mmcroot=/dev/mmcblk0p2 rw mmcrootfstype=ext3 rootwait mpurate=auto nandargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy= ${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_di sp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype} nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr} nandroot=ubi0:rootfs ubi.mtd=4 nandrootfstype=ubifs ramargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=$ {buddy} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdispla y} root=${ramroot} rootfstype=${ramrootfstype} ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr} ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=0x81000000,64M ramrootfstype=ext2 rdaddr=0x81000000 stderr=serial stdin=serial stdout=serial usbtty=cdc_acm userbutton=if gpio input 173; then run userbutton_xm; else run userbutton_nonxm; fi; userbutton_nonxm=gpio input 7; userbutton_xm=gpio input 4; vram=12M Environment size: 2359/131068 bytes OMAP3 beagleboard.org # * - * Qodem 0.1.2 Capture Generated Sun, 20 Oct 2013 10:59:54 -0600 END * - * On Sat, Oct 19, 2013 at 1:09 PM, Rudolf Streif <rstr...@linuxfoundation.org>wrote: > Edward, > > Your zImage is booting fine. The kernel starts and then tries to mount the > root file system. But it cannot find it. It's looking for a UBIFS but > cannot find it: > > > . >> VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error >> -19 >> Please append a correct "root=" boot option; here are the available >> partitions: >> VFS: Unable to mount root fs on unknown-block(0,0) >> User configuration error - no valid root filesystem found >> Kernel panic - not syncing: Invalid configuration from end user prevents >> continu >> ing >> > > You may have had additional error messages before the ones above that you > copied into your e-mail such as: > > UBIFS error (pid 1): ubifs_check_node: bad CRC: calculated 0xdfca80ed, > read 0x7b7c0f6b > UBIFS error (pid 1): ubifs_check_node: bad node at LEB 0:0 > UBIFS error (pid 1): ubifs_read_node: expected node type 6 > > That would be an indicator that the UBIFS root file system was not created > correctly on your flash device. How did you create it? > > Rudi >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto