From: James <ang...@gm...> - 2011-09-05 08:31:04
|
Hi Brett, On Mon, Sep 5, 2011 at 4:34 AM, Brett Hemes <hem...@gm...> wrote: > Hello, > > I am trying to update my overo fire to the newest image and am having some > issues. Here are the steps i have taken: > [snip] > > 2) flash new image to nand (using the same u-boot, uImage, and filesys that > I used for the card > - used the script from here: > http://gumstix.org/how-to/70-writing-images-to-flash.html > [snip] > omap2-nand driver initializing > ONFI flash detected > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V > 16-bit) > cmdlinepart partition parsing not available > Creating 5 MTD partitions on "omap2-nand.0": > 0x000000000000-0x000000080000 : "xloader" > 0x000000080000-0x000000240000 : "uboot" > 0x000000240000-0x000000280000 : "uboot environment" > 0x000000280000-0x000000680000 : "linux" > 0x000000680000-0x000020000000 : "rootfs" > UBI: attaching mtd4 to ubi0 > UBI: physical eraseblock size: 131072 bytes (128 KiB) > UBI: logical eraseblock size: 129024 bytes > UBI: smallest flash I/O unit: 2048 > UBI: sub-page size: 512 > UBI: VID header offset: 512 (aligned 512) > UBI: data offset: 2048 > UBI: max. sequence number: 0 > UBI error: ubi_read_volume_table: the layout volume was not found > UBI error: ubi_init: cannot attach mtd4 > [snip] > VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0) > Please append a correct "root=" boot option; here are the available > partitions: > 1f00 512 mtdblock0 (driver?) > 1f01 1792 mtdblock1 (driver?) > 1f02 256 mtdblock2 (driver?) > 1f03 4096 mtdblock3 (driver?) > 1f04 517632 mtdblock4 (driver?) > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > > Thanks, > Brett > > Are you using the correct file? cos the output seems to be looking for UBI rootfs and not the JFFS2 rootfs. Pop by to Steve's site to take a look at updating the UBI rootfs. http://www.sakoman.com. Hope that helps. -- Regards, James |