[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] uclinux boot problem (kernel panic)
Hi,
We tried the options & debug solutions given on the following link:
http://www.ucdot.org/article.pl?sid=03/01/11/1049210&mode=thread.
We obtain the following log on the hyperterminal:
Log File:
Linux version 2.4.32-uc0 (root@localhost) (gcc version 3.4.1 ( Xilinx
EDK 8.1 Bu
ild EDK_I.17 121005 )) #18 Sat Mar 18 12:06:57 IST 2006
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
CPU: MICROBLAZE
Kernel command line: °
Console: xmbserial on UARTLite
Calibrating delay loop... 33.07 BogoMIPS
Memory: 64MB = 64MB total
Memory: 63080KB available (709K code, 1033K data, 40K init)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Microblaze UARTlite serial driver version 1.00
ttyS0 at 0x40600000 (irq = 8) is a Microblaze UARTlite
Starting kswapd
RAMDISK driver initialized: 16 RAM disks of 67108864K size 1024
blocksize
uclinux[mtd]: RAM probe address=0x240e2840 size=0xd2000
uclinux[mtd]: root filesystem index=0
MicroBlaze auto-config flash probe(0x22000000,8388608,4): 800000 at
22000000
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x40000,blocks=32
Using buffer write method
Creating 8 MTD partitions on "Flash":
0x00000000-0x00004000 : "Bootloader"
mtd: partition "Bootloader" doesn't end on an erase block -- force
read-only
0x00004000-0x00008000 : "Bootargs"
mtd: partition "Bootargs" doesn't start on an erase block boundary --
force read
-only
0x00008000-0x0000c000 : "MAC"
mtd: partition "MAC" doesn't start on an erase block boundary -- force
read-only
0x00010000-0x00020000 : "Config"
mtd: partition "Config" doesn't start on an erase block boundary --
force read-o
nly
0x0000c000-0x00010000 : "Spare"
mtd: partition "Spare" doesn't start on an erase block boundary -- force
read-on
ly
0x00100000-0x00400000 : "Image"
0x00400000-0x00800000 : "JFFS2"
0x00000000-0x00800000 : "Flash"
MicroBlaze auto-config ram probe(0x240e2840,860160,4): d2000 at 240e2840
Creating 1 MTD partitions on "RAM":
0x00000000-0x000d2000 : "Romfs"
*******
VFS: test name = </dev/root>
VFS: fs_name = <ext2>
VFS: fs_name = <romfs>
VFS: root name <1f:09>
*******
VFS: tried fs_name = <ext2> err= -6
VFS: Cannot open root device "" or 1f:09
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 1f:09
It is not trying to mount the romfs partition. What could be the
problem? Are there any changes required in any source file? Is there any
step missing for kernel compilation? Please guide us.
Regards
Sanjay Patel
Embedded Engineer - Embedded Division
eInfochips Ltd
Phone: +91-79-55425187, 55457574 -Ext-118
Mobile: 98980-84637
-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of
Brettschneider Falk
Sent: Monday, March 20, 2006 1:03 PM
To: 'microblaze-uclinux@xxxxxxxxxxxxxx'
Subject: RE: [microblaze-uclinux] uclinux boot problem (kernel panic)
Hi,
your root filesystem is at index 0, that means the first MTD partition.
But
there's the bootloader. Your last MTD partition contains the "Romfs", so
the
log entry should actually be uclinux[mtd]: root filesystem index=0. That
may
be reason for the behaviour. This link might help you to find a
solution:
http://www.ucdot.org/article.pl?sid=03/01/11/1049210&mode=thread.
-----Original Message-----
From: Sanjay Patel
>
>
>Hi everybody,
>
>We programmed the linear flash memory with the tool (Programming Flash
Memory) provided within XPS. It allows programming the flash >with .srec
file.
>The image.srec file generated after following kernel compilation steps
provided was used for programming.
>
>The OUTPUT on the hyperterminal was as follows:
>
...8< snip
>
>What could be the problem? Are we wrong anywhere? Are we missing any
step
to follow?
>Please guide us!
>
>The board used by us is ML402 Board! The version is RevB. The size of
flash
memory is 8MB on board.
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
eInfochips Business Disclaimer:
This message may contain confidential, proprietary or legally Privileged
information. In case you are not the original intended Recipient of the
message, you must not, directly or indirectly, use, Disclose,
distribute, print, or copy any part of this message and you are
requested to delete it and inform the sender. Any views expressed in
this message are those of the individual sender unless otherwise stated.
Nothing contained in this message shall be construed as an offer or
acceptance of any offer by eInfochips Limited and/or eInfochips
Inc("eInfochips") unless sent with that express intent and with due
authority of eInfochips. eInfochips has taken enough precautions to
prevent the spread of viruses. However the company accepts no liability
for any damage caused by any virus transmitted by this email.
eInfochips Business Disclaimer:
This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by eInfochips Limited and/or eInfochips Inc("eInfochips") unless sent with that express intent and with due authority of eInfochips. eInfochips has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/