Re: [microblaze-uclinux] Booting uClinux memec v2p7

[mcnernbm@xxxxxxxxxxxxxxxxx]

John,
I mounted the romfs and I was able to
succesfully browse it.    Also after I build the kernel with
a,]ll the make ocmmands I have been coping the images folder from the linux
machine onto a pc and then downloading it the board.  Is this a problem
or ok or do I need to grab the image from where it is made?  Also
made the change after seeing that other post about the genirc uclinux under
MTD but still got the other error.  
Thanks
Brett

John Williams <jwilliams@itee.uq.edu.au>
Sent by: owner-microblaze-uclinux@itee.uq.edu.au

04/19/2005 09:43 PM

Please respond to
microblaze-uclinux@itee.uq.edu.au

To	microblaze-uclinux@itee.uq.edu.au
cc
Subject	Re: [microblaze-uclinux] Booting uClinux memec v2p7

Hi Brett,

mcnernbm@notes.udayton.edu wrote:
> 
> when trying to use the auto-config method with edk 7.1 when booting
I 
> get the following
> Search for id:(00 00) interleave(2) type(1)
> Search for id:(00 00) interleave(2) type(1)
> Search for id:(00 00) interleave(2) type(1)
> Search for id:(00 00) interleave(4) type(2)
> Search for id:(00 00) interleave(4) type(2)
> Search for id:(00 00) interleave(4) type(2)
> Search for id:(00 00) interleave(4) type(1)
> Search for id:(00 00) interleave(4) type(1)
> Search for id:(00 00) interleave(4) type(1)
> JEDEC: Found no Flash device at location zero
> MBVanilla ram probe(0x800c791c,729088,4): b2000 at 800c791c

Since you have no flash in your system, disable the "mbvanilla"
MTD 
mapping, and choose the generic uClinux one instead.  Deatailed 
instructions on this were posted in another reply to somebody else 
within the last week.

menuconfig->kernel->mtd->mappings


> VFS: Mounted root (romfs filesystem) readonly.
> Freeing init memory: 32K
> release_dev: driver.table[60] not tty for (04:40)

never seen this before.  Something's breaking your romfs image.

You can try mounting it locally on your dev machine, with the loop device:

$ mount -t romfs  -o loop images/romfs.img /mnt/tmp

or similar.  If it mounts and you can browse the filesystem OK, then
it 
suggests it's being corrupted once it hits your board.

This might help narrow things down a little.

Regards,

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/