[yocto] Freescale T1040RDB Failed to mount UBIFS

[Sandeep G.R]

Hi Leo,

I walked through the QorIQ-SDK-1.7 manual section 3.4.16 for T1040RDB
doesn't say anything on the NAND flash procedure. I can see the NOR Flash
memory map and flash procedure.

I use T4240RDB with NOR flash works great.

Please contact your local Freescale FAE for more support and post the
question is Freescale forum you might get some help.


On Fri, Apr 10, 2015 at 10:53 AM, Leo Tao <Leo.Tao at flextronics.com> wrote:

>  Hi,
>
>
>
> I built UBIFS rootfs for T1040RDB, apparently I got 2 rootfs images:
>
> 1. fsl-image-core-t1040rdb-20150408204106.rootfs.ubi
>
> 2. fsl-image-core-t1040rdb-20150408204106.rootfs.ubifs
>
> So I updated  Nand Flash rootfs Partition with  image
> :fsl-image-core-t1040rdb-20150408204106.rootfs.ubifs
>
>
>
> Uboot bootcmd : bootcmd=setenv bootargs noinitrd ip=off mem=256M
> rootwait=1 rw ubi.mtd=7,4096 rootfstype=ubifs root=ubi0:rootfs
> console=$consoledev,$baudrate $othbootargs;nand read.e $loadaddr
> $kernel_addr $kernel_size;nand read.e $fdtaddr $fdt_addr $fdt_size;bootm
> $loadaddr - $fdtaddr
>
>
>
> My question is
>
> 1.       which image should be flashed to Nand, xxx.ubi or xxx.ubifs?
>
> 2.       what does the error blow mean?
>
>
>
> Built uboot and kernel to support ubifs and reset  T1040RDB, but I got
> error blow:
>
>
>
> Key type dns_resolver registered
>
> UBI: attaching mtd7 to ubi0
>
> UBI error: validate_ec_hdr: bad VID header offset 512, expected 4096
>
> UBI error: validate_ec_hdr: bad EC header
>
> Erase counter header dump:
>
>         magic          0x55424923
>
>         version        1
>
>         ec             0
>
>         vid_hdr_offset 512
>
>         data_offset    1024
>
>         image_seq      2076921562
>
>         hdr_crc        0x951adef
>
> erase counter header hexdump:
>
> CPU: 2 PID: 1 Comm: swapper/0 Not tainted
> 3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b #6
>
> Call Trace:
>
> [c9081cd0] [c0006f50] show_stack+0x40/0x150 (unreliable)
>
> [c9081d10] [c06e9a20] dump_stack+0x78/0xa0
>
> [c9081d20] [c03a56ac] validate_ec_hdr+0xac/0x120
>
> [c9081d30] [c03a6104] ubi_io_read_ec_hdr+0x184/0x240
>
> [c9081d60] [c03aaf00] ubi_attach+0x180/0x14d0
>
> [c9081de0] [c039fdf8] ubi_attach_mtd_dev+0x688/0xc80
>
> [c9081e30] [c08e9348] ubi_init+0x274/0x30c
>
> [c9081e80] [c00021a8] do_one_initcall+0x158/0x1b0
>
> [c9081ef0] [c08cb8d0] kernel_init_freeable+0x134/0x1d0
>
> [c9081f20] [c0002808] kernel_init+0x18/0x170
>
> [c9081f40] [c000fe0c] ret_from_kernel_thread+0x5c/0x64
>
> UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
>
> UBI error: ubi_attach_mtd_dev: failed to attach mtd7, error -22
>
> UBI error: ubi_init: cannot attach mtd7
>
> fsl_dpa_macless: FSL DPAA MACless Ethernet driver ()
>
> fsl_dpa_generic: FSL DPAA Generic Ethernet driver ()
>
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
>
> UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
>
> 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:
>
> 1f00          131072 mtdblock0  (driver?)
>
> 1f01            1536 mtdblock1  (driver?)
>
> 1f02            1024 mtdblock2  (driver?)
>
> 1f03            1024 mtdblock3  (driver?)
>
> 1f04           24576 mtdblock4  (driver?)
>
> 1f05           10240 mtdblock5  (driver?)
>
> 1f06            1024 mtdblock6  (driver?)
>
> 1f07          409600 mtdblock7  (driver?)
>
> 1f08           98304 mtdblock8  (driver?)
>
> 1f09          524288 mtdblock9  (driver?)
>
> 1f0a           65536 mtdblock10  (driver?)
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.7+g66
>  The information contained in this message may be privileged and
> confidential. It is intended to be read only by the individual or entity to
> whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and delete or
> destroy any copy of this message!
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
*Thanks & Regards,*
*Sandeep G R*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150410/09b22236/attachment.html>