[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] uClinux boots on MicroBlaze but......
At 24 Jun 2004 15:25:44 -0000,
anand_12 wrote:
[...]
> We are trying to get uClinux(latest dist) running on the insight
> memec spartan 2e 600 LC development board.After some initial
> hiccups,somehow got the kernel booting(starting address :
> 0x80000000)..but it hung after printing "calibrating delay loop..."
> on the hyperterm...i mean there was no activity beyond that..even
> after a wait of abt 10 minutes...
that usually means that interrupt is not working.
> so next time we commented out the Bogomips computation loop(in
> linux/init/main.c,..and as expected we got the kernel booting
> further(why is that delay there and is using such a workaround
> advisable?)...the kernel boot log(as seen on hyperterm) is as shown
> below :
>
> -----------------------START-------------------------------
>
> Linux version 2.4.24-uc0 (root@soc3) (gcc version 2.95.3-4 Xilinx EDK 6.1 Build
> EDK_G.11) #54 Thu Jun 24 14:26:12 IST 2004
> On node 0 totalpages: 8192
> zone(0): 8192 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> CPU: MICROBLAZE
> Console: xmbserial on UARTLite
> Kernel command line:
> Calibrating delay loop...
> Memory: 31472K/32768K available (594K kernel code, 210K data)
> Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
> Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 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 0xffff2000 (irq = 1) is a Microblaze UARTlite
> ttyS1 at 0xffff4000 (irq = 2) is a Microblaze UARTlite
> Starting kswapd
> pty: 256 Unix98 ptys configured
> xgpio #0 at 0xFFFF5000 mapped to 0xFFFF5000
> Xilinx GPIO registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> VFS: Cannot open root device "" or 00:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 00:00
>
> --------------------------END------------------------------
>
> but as is clear from the above bootlog....root filesystem could not
> be mounted....
well, what's your root fs? if you are tring to boot your kernel as
default, mtd should be enabled by default. what you really need is
"Generic uClinux RAM/ROM filesystem support" in MTD Mapping section.
> we are trying to figure out how and why this kernel panic'd here and
> what to do to proceed further.... can any one help us out as to
> whats going on here?...at the end of the uClinux build process...6
> files are created in the uClinux-dist/images directory..one of them
> being romfs.img....why is this generated and what is it used
> for?...is this file related to the kernel panic message in the
> kernel bootlog shown above?..
>
> besides 2 serial ports seem to have been detected(there is only one
> on the board!! )..or does that mean something else(ttyS0 and ttyS1?
> ..please guide us here....
disable debug serial port in linux-2.4.x/arch/microblaze/config.in as
SUZAKU does.
> i just checked the hardware address mapping oxffff2000 maps to UART
> but 0xffff4000 maps to OPB timer...
now, that might be the reason why calibrating delay loop failed. you
need to have a good working timer to calculate bogomips.
> one more thing that we noticed is that somehow the value 9 is being
> driven to the 7 segment display on the board during the booting
> process(address mapping of GPIO leds : 0xffff3000-...) why is this
> happening?..is it an indication of something important?...
I have no idea about this.
--
yashi
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/