Re: Problems with Serial Port on IceCube

Re: Problems with Serial Port on IceCube

[Linas Petras]

I have tried using another serial cable (as suggested by Wolfgang) but =
it
made no difference, but I did not expect it to as I get all the messages
from the bootroms OK.

I have have confirmed that I have (as suggested by Sylvian) set
CONFIG_CMDLINE=3D "console=3DttyS0" and have also tried =
"console=3DttyS0, 115200"
(as my serial port is set to 115200 on the icecube board) without any
messages after arch:exit.=20

Below is what I see when I try and boot Sylvians 2-6-10-rc2 kernel.

=3D> tftp 200000
Using FEC ETHERNET device
TFTP from server 192.168.1.101; our IP address is 192.168.1.201
Filename 'uImage'.
Load address: 0x200000
Loading: =
#################################################################
 #################################################################
 #################################################################
 #############################################################
done
Bytes transferred =3D 1305842 (13ecf2 hex)
=3D> bootm 200000
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.10-rc2
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1305778 Bytes =3D  1.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
ocp: exit
arch: exit
            =20
At this point all output to the serial port stops but the board boots =
and I
can telnet to the IP address. It's not that important in the greater =
scheme
of things, just very annoying :-(

Below is a "printenv" from the icecube-uboot.

baudrate=3D115200
ethact=3DFEC ETHERNET
preboot=3Decho;echo AutoStarting. Press any key to abort ...;echo
ethaddr=3D00:04:9F:00:12:60
bootdelay=3D5
hostname=3Dicecube
flashboot=3Droot=3D/dev/mtdblock2 rw
rootfs=3Droot=3D/dev/nfs rw =
nfsroot=3D192.168.1.101:/work/ELDK-3.1/ppc_6xx
bootfile=3DuImage
nfsroot=3Droot=3D/dev/nfs rw =
nfsroot=3D192.168.1.101:/work/ELDK-3.1/ppc_6xx
ip=3Dip=3D192.168.1.201:192.168.1.101:192.168.1.101:255.255.255.0:icecube=
::off
bootargs=3Droot=3D/dev/nfs rw =
nfsroot=3D192.168.1.101:/work/ELDK-3.1/ppc_6xx
ip=3D192.16
8.1.201:192.168.1.101:192.168.1.101:255.255.255.0:icecube::off
filesize=3Db7d6e
fileaddr=3D100000
netmask=3D255.255.255.0
ipaddr=3D192.168.1.201
serverip=3D192.168.1.101
bootcmd=3Dbootm ff100000
stdin=3Dserial
stdout=3Dserial
stderr=3Dserial


Any ideas????


Linas Petras
------------
I know not with which weapons World War III will be faught, but World =
War IV
will be faught with sticks and stones. - Albert Einstein.

Problems with Serial Port on IceCube

[Linas Petras]

Hi All

I'm running Sylvain Munaut's version of 2.6.10-rc2 with DENX's 3.1 ELDK =
as
the cross
compile tools with nfs mounted root filesystem and I seem to have a =
probelm
when I'm=20
connected to the "icecube" development boards serial port.

I get the u-boot 1.1.3 bootrom messages from the serial port on the
"icecube" and can=20
boot the kernel using the serial port but I don't get any messages after =
the
early=20
boot message "arch: exit". It appeared to me that the board was booting =
so I
tried to=20
telnet via the network to the board and this worked fine. So the kernel =
is
running, I=20
just don't get the "normal" bootup messages from the kernel.

If I use the standard DENX 2.4.25 kernel I get all the message going to =
the
serial=20
port OK.

Any ideas of whats going on ????? Is their a problem with the console
support in=20
Sylvain's port or something in the "standard" init scripts that come =
with
DENX's ELDK=20
3.1 when used with a 2.6.xx kernel or have I missed something obvious?

Linas Petras
------------
I know not with which weapons World War III will be faught, but World =
War IV
will be faught with sticks and stones. - Albert Einstein.

Re: Problems with Serial Port on IceCube

[Wolfgang Denk]

Dear Linas,

in message <000001c50adc$c814dae0$6401a8c0@supernova> you wrote:
> 
> Any ideas of whats going on ????? Is their a problem with the console support in 
> Sylvain's port or something in the "standard" init scripts that come with DENX's ELDK 
> 3.1 when used with a 2.6.xx kernel or have I missed something obvious?

There is nothing in the init scripts that should matter here.

Just out of curiousity: can you try another console cable? Probably a
minimal one (only 3 wires: GND + RxD + TxD) ?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"There are things that are so serious that you can  only  joke  about
them"                                                    - Heisenberg

Re: Problems with Serial Port on IceCube

[Sylvain Munaut]

Hi

Does your kernel cmdline includes the "console=ttyS0" ?
It's mandatory here while with DENX's kernel it may not be.

The initscript are not even launched at that point ...


Sylvain


Linas Petras wrote:

>Hi All
>
>I'm running Sylvain Munaut's version of 2.6.10-rc2 with DENX's 3.1 ELDK as
>the cross
>compile tools with nfs mounted root filesystem and I seem to have a probelm
>when I'm 
>connected to the "icecube" development boards serial port.
>
>I get the u-boot 1.1.3 bootrom messages from the serial port on the
>"icecube" and can 
>boot the kernel using the serial port but I don't get any messages after the
>early 
>boot message "arch: exit". It appeared to me that the board was booting so I
>tried to 
>telnet via the network to the board and this worked fine. So the kernel is
>running, I 
>just don't get the "normal" bootup messages from the kernel.
>
>If I use the standard DENX 2.4.25 kernel I get all the message going to the
>serial 
>port OK.
>
>Any ideas of whats going on ????? Is their a problem with the console
>support in 
>Sylvain's port or something in the "standard" init scripts that come with
>DENX's ELDK 
>3.1 when used with a 2.6.xx kernel or have I missed something obvious?
>
>Linas Petras
>------------
>I know not with which weapons World War III will be faught, but World War IV
>will be faught with sticks and stones. - Albert Einstein.
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>  
>