am3352核心板更新文件系统问题
米尔提供的：根文件系统操作命令：
nand ease 780000 f000000
mmc rescan;
fatload mmc 0 82000000 ubi.img;nandecc sw;nand write.i 82000000 780000 ${filesize};
问题：为什么米尔科技自己提供的文件系统，竟然是启动不了。求解。
OneNAND driver initializing
UBI: attaching mtd7 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI error: process_eb: bad image sequence number 67759283 in PEB 1920, expected 43703682
slab error in kmem_cache_destroy(): cache `ubi_scan_leb_slab': Can't free all objects
Backtrace:
[<c0018f68>] (dump_backtrace+0x0/0x110) from [<c0542518>] (dump_stack+0x18/0x1c)
r6:cf1f2000 r5:cf1eca40 r4:cf1c5940 r3:60000013
[<c0542500>] (dump_stack+0x0/0x1c) from [<c00b252c>] (kmem_cache_destroy+0xd4/0x10c)
[<c00b2458>] (kmem_cache_destroy+0x0/0x10c) from [<c0307e38>] (ubi_scan+0x334/0xa08)
r4:00000780 r3:cf1e9000
[<c0307b04>] (ubi_scan+0x0/0xa08) from [<c02feb2c>] (ubi_attach_mtd_dev+0x500/0xa90)
[<c02fe62c>] (ubi_attach_mtd_dev+0x0/0xa90) from [<c070a700>] (ubi_init+0x20c/0x308)
[<c070a4f4>] (ubi_init+0x0/0x308) from [<c0008690>] (do_one_initcall+0x3c/0x18c)
[<c0008654>] (do_one_initcall+0x0/0x18c) from [<c06e82a0>] (kernel_init+0x9c/0x128)
r9:00000000 r8:00000000 r7:00000013 r6:c0045c58 r5:c0727ba0
r4:c0727998
[<c06e8204>] (kernel_init+0x0/0x128) from [<c0045c58>] (do_exit+0x0/0x698)
r5:c06e8204 r4:00000000
UBI error: ubi_init: cannot attach mtd7
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can.1: device registered (irq=55, irq_obj=56)
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask ffffffaf
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy: device 0:04, driver unknown
davinci_mdio davinci_mdio.0: phy: device 0:06, driver unknown
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
cdc_ncm: 04-Aug-2011
usbcore: registered new interface driver cdc_ncm
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
gadget: using random self ethernet address
gadget: using random host ethernet address
usb0: MAC 7e:fe:cc:97:98:a5
usb0: HOST MAC 3a:f0:7b:c8:2b:ab
gadget: Ethernet Gadget, version: Memorial Day 2008
gadget: g_ether ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 3.2.0 musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: already running
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
watchdog gpio: 104
myir-watchdog driver initialized successfully!
_regulator_get: deviceless supply vdd_mpu not found, using dummy regulator
cpuidle: using governor ladder
cpuidle: using governor menu
omap4_aes_mod_init: loading AM33X AES driver
omap4-aes omap4-aes: AM33X AES hw accel rev: 3.02
omap4_aes_probe: probe() done
omap4_sham_mod_init: loading AM33X SHA/MD5 driver
omap4-sham omap4-sham: AM33X SHA/MD5 hw accel rev: 4.03
omap4_sham_probe: probe() done
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
sgtl5000 2-000a: Device with ID register ffff is not a sgtl5000
sgtl5000 2-000a: asoc: failed to probe CODEC sgtl5000.2-000a: -19
asoc: failed to instantiate card AM335X EVM: -19
ALSA device list:
No soundcards found.
oprofile: hardware counters not available
oprofile: using timer interrupt.
nf_conntrack version 0.5.0 (3936 buckets, 15744 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
mux: Failed to setup hwmod io irq -22
Power Management for AM33XX family
Trying to load am335x-pm-firmware.bin (60 secs timeout)
Copied the M3 firmware to UMEM
Compensating OPP0 for 0mV Orig nvalue:0x99c9b4 New nvalue:0x99c9b4
Compensating OPP1 for 0mV Orig nvalue:0x999080 New nvalue:0x999080
_regulator_get: deviceless supply vdd_core not found, using dummy regulator
smartreflex smartreflex: am33xx_sr_probe: cannot determine opp
smartreflex: probe of smartreflex failed with error -22
sr_init: platform driver register failed
clock: disabling unused clocks to save power
Detected MACID=1c:ba:8c:b3:d4:55
cpsw: Detected MACID = 1c:ba:8c:b3:d4:57
input: gpio-keys as /devices/platform/gpio-keys/input/input0
omap_rtc omap_rtc: setting system clock to 2000-01-01 04:36:16 UTC (946701376)
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 128 mtdblock0(driver?)
1f01 128 mtdblock1(driver?)
1f02 128 mtdblock2(driver?)
1f03 128 mtdblock3(driver?)
1f04 1920 mtdblock4(driver?)
1f05 128 mtdblock5(driver?)
1f06 5120 mtdblock6(driver?)
1f07 254464 mtdblock7(driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Backtrace:
[<c0018f68>] (dump_backtrace+0x0/0x110) from [<c0542518>] (dump_stack+0x18/0x1c)
r6:cf028000 r5:c0793508 r4:c0793508 r3:60000013
[<c0542500>] (dump_stack+0x0/0x1c) from [<c0542590>] (panic+0x74/0x198)
[<c054251c>] (panic+0x0/0x198) from [<c06e8dc0>] (mount_block_root+0x194/0x23c)
r3:00000001 r2:00000000 r1:cf01df78 r0:c06365c0
r7:00008000
[<c06e8c2c>] (mount_block_root+0x0/0x23c) from [<c06e8fec>] (prepare_namespace+0xac/0x1e0)
[<c06e8f40>] (prepare_namespace+0x0/0x1e0) from [<c06e8320>] (kernel_init+0x11c/0x128)
r5:c0727ba0 r4:c0727ba0
[<c06e8204>] (kernel_init+0x0/0x128) from [<c0045c58>] (do_exit+0x0/0x698)
r5:c06e8204 r4:00000000
问题：为什么米尔科技自己提供的文件系统，竟然是启动不了。求解。
页:
[1]