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

RE: [microblaze-uclinux] login issue when booting



I notice you’re running at 50 MHz; have you checked your implementation timing report for errors?

 

Also, you have the UART option of MDM enabled; which UART do you have mapped to console I/O? (I was never able to get the MDM UART working for this purpose and had to use the UARTlite peripheral.)

 

David Banas
Field Applications Engineer
Nu Horizons Electronics Corp.
2070 Ringwood Avenue
San Jose, CA 95131
(408)434-0800 - office
(415)846-5837 - cell
http://www.nuhorizons.com


From: owner-microblaze-uclinux@itee.uq.edu.au [mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of John McGrath
Sent: Friday, April 22, 2005 7:57 AM
To: microblaze-uclinux@itee.uq.edu.au
Subject: Re: [microblaze-uclinux] login issue when booting

 

Hi Brett,
Thanks for the offer to help!
My MHS and MSS are pretty simple (attached) and I also attached the auto-config.in.
The version of the kernel was downloaded completly new wednesday of this week. the only previous kernel I tried was late feb/start of march, and I had the same problem as I'm having now...


I have a pretty simple system - no caches enabled, etc. I assume that somehow auto-confing.in knows what parameters to pass to gcc to enable/disable certain processor features?
One thing about the mdm - the version of it I am using is the version that John Williams had in his ml401 reference platform, i.e. 2.01.a

Maybe If I could get a look at your MHS/MSS I could try put your settings into my baord? (I guess it's just a ucf change needed, all else should be ok!) What version of the EDK are you using?

Cheers,
John





mcnernbm@notes.udayton.edu wrote:


John ,y board also has led sand stuff but I took the dirver out for now to have a minimul kernel so that once Igot that working I could go back and addstuff back in slowly.  This way I had lss to debug and less things that could cause an issue.   Can you post .mss and .mhs file?   Hipefully we can figure otu why yours wont boot all the way cause I feel your pain cause it we frustrating me for a while and now I am so close and just want to see mine fully working.  

Also on the xmd issue I saw that a couple times with mine also.  And when I would go back reset my board and redown load the hardware and then the kernel to it it would go away.  But I to see that once n a while.  Have you tried using an older kernel yet?  Prior to the changes since friday and the other night?

Brett


John McGrath <john.mcgrath@xilinx.com>
Sent by: owner-microblaze-uclinux@itee.uq.edu.au

04/22/2005 06:20 AM

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

To

microblaze-uclinux@itee.uq.edu.au

cc

 

Subject

Re: [microblaze-uclinux] login issue when booting

 

 

 




Hi,
I am using a very basic V2p7 AFX 456 board, from Xilinx. It doesnt't have an ethernet port or flash, so I usually remove those too. I leave the gpio in, as there are 8 on-board LED's. And 8mb of SDRAM, where i download the image.bin. It looks like I do everything the same as you!

One thing which is curiouis is sometimes the XMD console will report EDK Error -  when the kernel is trying to boot. This leads me to beleive the MB is trying to write something to the XMD console...by any chance is it possible the system starting up is trying to use the XMD uart as the console after boot?

Regarding hyperterminal - if you scroll up more than one page, it always mangles the "history" of what it displayed. I don't know why!
Also, I dont think xon/xof should be used, as I beleive the uartlite does not support hardware flow-control...

Cheers,
John

mcnernbm@notes.udayton.edu wrote:

John,

Suprisingly I did not do a whole lot.  I run an update on my kernel and dist directories.  I then made sure my auto-make file was up to date in the kernel architecture microblaze directory.  Once I had this  I built the kernel with as little as possible.  I took out the ethernet, flash, and gpio drivers.  I also changed the mdm from the flash driver to the generic uclinx rom driver.  then I ran the make dep and make and then booted thejimage.bin file through xmd.  My commands I used where dow -data images/image 0x80000000 and then con 0x80000000.  Simple as that.  But I am still having the issue that is will nto let me login now.  So if it keeps doing this I may still go back and try an older kernel download.  Also what board are you using?

Brett


John McGrath <john.mcgrath@xilinx.com>
Sent by:
owner-microblaze-uclinux@itee.uq.edu.au

04/21/2005 04:31 PM

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

 

To

microblaze-uclinux@itee.uq.edu.au

cc

 

Subject

Re: [microblaze-uclinux] login issue when booting

 

 

 





Hi
It seems like you got past the previous problem you were having, detailed in the "booting uclinux" thread. How did you do this? I am still "hanging" at the line


uclinux[mtd]: root filesystem index=0

VFS: Mounted root (romfs filesystem) readonly.

Freeing init memory: 32K



Can you help?

Cheers
John

mcnernbm@notes.udayton.edu wrote:

When booting the uclinux on a memec v2p board I get the results below.  But once it hits the login part I can not login.  I have tried root as the username and pass and jsut root as used and no pass and I can nto get it to login.  Also there is the one fail listed and not sure if that is causing me a problem or not.  Also the only thing I changed when I built the kerneal is I disable the ethernet and networking stuff and the gpio driver and I also changed the MDM to the generic rom selection.  All other option I left alone.


zone(0): 8192 pages.ash device at locati

zone(1): 0 pages.rch for id:(00 00

zone(2): 0 pages.pe(2)rning: dev (

CPU: MICROBLAZErch for id:(00
Kernel command line:e

MBVanil

CFI: Found

Console: xmbserial on UARTLitero00 00) interleave(2) type(1)

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

Starting kswapd

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

uclinux[mtd]: RAM probe address=0x800c58fc size=0xb2000

uclinux[mtd]: root filesystem index=0

VFS: Mounted root (romfs filesystem) readonly.

Freeing init memory: 32K

Mounting proc:

Mounting var:

Populating /var:

Running local start scripts.

Mounting /etc/config:

Populating /etc/config:

flatfsd: Nonexistent or bad flatfs (-43), creating new one...

flatfsd: Failed to write flatfs (-43): No such device

flatfsd: Created 3 configuration files (142 bytes)

Setting hostname:


uclinux-auto login:


THanks for the help

Brett


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________