2008-07-28 08:21:36 No filesystem could mount root, tried:
everest zhang (CHINA)
Message: 59492
Hi,
I use the 2008R1-RC8 version kernel, hardware: adsp-bf561.
The following error message :
U-Boot 1.1.6 (ADI-2008R1) (Jul 27 2008 - 12:46:33)
CPU: ADSP bf561-0.3 (Detected Rev: 0.3)
Board: Potevio-NST BF561 Easyview board
Support: http://blackfin.uclinux.org/
Clock: VCO: 550 MHz, Core: 550 MHz, System: 137 MHz
RAM: 128 MB
Flash: 16 MB
In: serial
Out: serial
Err: serial
NAND: 1024 MiB
Net: MAC: 00:89:34:DD:DD:DD
Hit any key to stop autoboot: 0
u-boot>
u-boot> tftp 0x1000000 vmImage
Found DM9000 or dm9010 ID:90000a46 at address 24800000 !
DM9000 work in 16 bus width
PHY is autonegotiating now, pls waiting ...
operating at 100M full duplex mode
[eth_init]MAC 00 89 34 dd dd dd
TFTP from server 192.168.88.51; our IP address is 192.168.88.233
Filename 'vmImage'.
Load address: 0x1000000
Loading: T #################################################################
#################################################################
##########################
done
Bytes transferred = 798718 (c2ffe hex)
u-boot> bootm 0x1000000
## Booting image at 01000000 ...
Image Name: Linux-2.6.22.18-ADI-2008R1-svn
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 798654 Bytes = 779.9 kB
Load Address: 00001000
Entry Point: 0014a000
Verifying Checksum ... OK
Uncompressing Kernel Image ... ************************************************OK
Starting Kernel at = 14a000
ÿLinux version 2.6.22.18-ADI-2008R1-svn (root@Fedora6_blackfin) (gcc version 4.1.2 (ADI svn)) #25 Mon Jul 28 20:04:48 CST 2008
Hardware Trace Active and Enabled
Warning: limiting memory to 56MB due to hardware anomaly 05000263
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF561 Rev 0.3
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 550 MHz core clock and 137 MHz System Clock
Board Memory: 128MB
Kernel Managed Memory: 128MB
Memory map:
text = 0x00001000-0x000f3d10
rodata = 0x000f4000-0x00139380
data = 0x0013a000-0x0014a000
stack = 0x0013a000-0x0013c000
init = 0x0014a000-0x00163000
bss = 0x00163000-0x00172750
available = 0x00172750-0x037ff000
DMA Zone = 0x07f00000-0x08000000
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 14224
Kernel command line: root=/dev/mtdblock0 rw console=ttyBF0,115200
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 55280k/131072k RAM, (100k init code, 971k kernel code, 406k data, 1024k dma, 73292k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (15 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 16 KB (10 KB free)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
ezkit_init(): registering device resources
Generic PHY: Registered new driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
BF561 Core B driver v0.1 initialized.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 35) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@16
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
After download the release kernel, I only changed hardware flatform from BF527 to BF561-ezkti. I want to know why.
thank you much!
QuoteReplyEditDelete
2008-07-28 11:32:07 Re: No filesystem could mount root, tried:
Mike Frysinger (UNITED STATES)
Message: 59498
do not leave that "Support" line in u-boot for your board. that URL is for boards maintained by ADI and 3rd parties that get integrated. your board does not qualify.
you need to set your root filesystem appropriately. you set "root=/dev/mtdblock0" on your kernel command line, but you didnt enable any MTD drivers which would provide that.
QuoteReplyEditDelete
2008-07-29 09:39:44 Re: No filesystem could mount root, tried:
everest zhang (CHINA)
Message: 59550
Thank you mike. As we used old 2006R1 for long time, recently we will move to 2008R1. There is big different between the two kernel versions. I think there are many difficult to face. Fortunately, I can get help from you and your team. After researching your doc on line, I understand the lastest output files' meaning. so now my board is on fly.