Messy output after "booting the kernel."

It sounds like the console settings are not correct in u-boot.  Could you please post your entire u-boot environment variables?  Type "printenv" at the u-boot prompt.

The console settings should be:

console=ttyS0, 115200n8

and this should used as part of the bootargs which is passed to the kernel

Greg

Greg,

I set the console=ttyS2, 115200n8, but I changed it as you said. 

The console gives no information after "booting the kernal".

==============

TFTP from server 192.168.0.1; our IP address is 192.168.0.5
Filename 'uImage'.
Load address: 0xc0700000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############################
done
Bytes transferred = 1804376 (1b8858 hex)
U-Boot > bootm
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-2.6.18_pro500-da830_omapl1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1804312 Bytes =  1.7 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
........................................................... done, booting the ke
rnel.

U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

I2C:   ready
DRAM:  64 MB
In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
More than one PHY detected.
Hit any key to stop autoboot:  0
U-Boot > printenv
bootdelay=3
baudrate=115200
ethaddr=00:0e:99:02:fd:04
autoload=no
nfshost=192.168.0.1
autoboot=no
mem=32M
bootcmd=dhcp;tftp
rootpath=/home/MECHENG/guo.132/workdir/filesys
bootfile=uImage
filesize=1B8858
fileaddr=C0700000
netmask=255.255.255.0
ipaddr=192.168.0.5
serverip=192.168.0.1
dnsip=192.168.0.1
bootarfs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=dev/nfs nfsboot=192.168
.0.1://home/MECHENG/guo.132/workdir/filesysy, nolock mem=32M
bootargs=console=ttyS0, 115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.1
68.0.1:/home/MECHENG/guo.132/workdir/filesys, nolock mem=32M
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

Environment size: 666/16380 bytes
U-Boot > dhcp
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 28
DHCP client bound to address 192.168.0.5
U-Boot > tftp
TFTP from server 192.168.0.1; our IP address is 192.168.0.5
Filename 'uImage'.
Load address: 0xc0700000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############################
done
Bytes transferred = 1804376 (1b8858 hex)
U-Boot > bootm
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-2.6.18_pro500-da830_omapl1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1804312 Bytes =  1.7 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
........................................................... done, booting the ke
rnel.

If you are using a Logic PD board with OMAPL1x, then using ttyS2 in the console parameter is correct.  I apologize for the confusion because I gave you the ttyS0 setting that is correct for the OMAP3 EVM.  So you should change back to ttyS2.

Since you said the symptom is a "messy" output I thought that the problem was the speed part of the console setting which should be 115200n8.

I see a space in bootargs in the definition of console.  There is a space between the comma and the numerical value 115200.  Take out that space and try again with ttyS2.

Greg

Greg,

Thanks for your suggestions.

I changed back to "ttyS2".

The second suggestion worked. There should be no space between "console=ttyS2,115200n8" and the people who has such kind of problem should have a try of such examination.

Cheers!