[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] not getting shell prompt at the end of uClinuxboot



Hi Anand,

I'll do my best to answer your questions - see below:

anand_12 wrote:

> Blkmem copyright 1998,1999 D. Jeff Dionne 
> Blkmem copyright 1998 Kenneth Albanowski 
> Blkmem 1 disk images: 
> 0: 800E6E2C-80118E2B [VIRTUAL 800E6E2C-80118E2B] (RO) 
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize 
> uclinux[mtd]: RAM probe address=0x800e6e2c size=0x32000 
> uclinux[mtd]: root filesystem index=0 
> Can't allocate major number 31 for Memory Technology Devices. 

Blkmem and MTD are mutually exclusive, you really should use either one 
or the other.  There are ways around this, but not many good reasons. 
I'd recommend MTD only if you can, it's cleaner and works well.

This may or may not be related to the problem you are seeing, but should 
be fixed up anyway.

> VFS: Mounted root (romfs filesystem) readonly. 
> Freeing unused kernel memory: 40K freed 
> 
> Sash command shell (v 
> ---------------BOOTLOG END-------------------------------- 
> 
> 
> After printing "Sash command shell(v" it hangs...I am not able to figure out what is happening...can anyone help me out with this....??...atfirst i thought it could just be 
> some stdout fflush'ing(because of which i am not able to see the display on the hyperterm) issue...but it seems there is something more to it....any help would be welcome 

Does your board really have 32MB of RAM, as reported by the bootlog?  If 
not, you must adjust the values contained in 
linux-2.4.x/include/asm-microblaze/xparameters.h (or is it mbvanilla.h - 
can't remember, have been away for 3 weeks!)- there are #defines for the 
start of ram, and the size.  Make sure that size is correct.

> besides I am running microblaze at 50 Mhz but bogomips computed is just 2.85...does this indicate a timer problem?.... 

That number looks about right when you have no cache, or it is disabled. 
  This is another thing to check, if your microblazesystem has no cache, 
then make sure you indicate that in the kernel config, under processor 
type and features there is an option to specify the existence and size 
of the instruction and data caches.  Make sure they match your hardware 
configuration.

Also, make sure the other options in there (barrel shifter, hard 
multipler etc) also match your actual hardware specification.

Cheers,

John

___________________________
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/