Why FEC and SCC1 can not work at the same time?

Why FEC and SCC1 can not work at the same time?

[zhongqx]

Hello,every one
    Hello Wolf gang thank you for help!my ramdisk problem has passed!I use linux-2.4.4-2002-02-14 kernel and all is ok!but I dont understand why linux-2.4.18 is not ok.


Now I meet a new problem! it is very strange!
I want to use FEC(100M) and SCC1(10M) interface,but they can not work together.
     When I use ppcboot with CONFIG_SCC1_ENET defined , boot linux ,then SCC1 is ok,when I ping FEC (I config it ip address is 192.168.2.221) it displayed messaged "time out".
     When I use ppcboot with CONFIG_FEC_ENET  defined,  boot linux ,then FEC is ok, when I
ping SCC( I config it ip address is 192.168.1.198) it displayed messaged also "time out".

Can you someone give help?thank you in advanced! the following is the linux output:

>bootm 400000 500000
## Booting image at 00400000 ...
   Image Name:   kernel
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    484192 Bytes = 472 kB = 0 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00500000 ...
   Image Name:   ramdisk
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    933860 Bytes = 911 kB = 0 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 00677000, end 0075afe4 ... OK
Linux version 2.4.4-rthal5 (root@localhost.localdomain) (gcc version 2.95.2 1999
1024 (release)) #1 Tue Sep 17 09:45:41 CST 2002
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram rw
Decrementer Frequency: 3000000
Calibrating delay loop... 47.71 BogoMIPS
Memory: 5784k available (900k kernel code, 388k data, 40k init, 0k highmem)
Dentry-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 512 (order: 0, 4096 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
CPM UART driver version 0.03
ttyS0 on SMC1 at 0x0280, BRG1
ttyS1 on SCC2 at 0x0100, BRG2
block: queued sectors max/low 3725kB/1241kB, 64 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
eth0: CPM ENET Version 0.2 on SCC1, 00:d0:93:00:12:34
eth1: FEC ENET Version 0.2, FEC irq 3, MII irq 4, addr 00:d0:93:80:12:34
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 911k freed
devfs: v0.102 (20000622) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x2
loop: loaded (max 8 devices)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 512)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 40k init
init started:  BusyBox v0.60.2 (2002.07.18-17:16+0000) multi-call SIOCADDRT: Net
work is unreachable

    ******(What reason ? when this message output?)


BusyBox v0.60.2 (2002.07.18-17:16+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:D0:93:00:12:34
          inet addr:192.168.2.221  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:64 (64.0 b)  TX bytes:0 (0.0 b)
          Base address:0x3c00

eth1      Link encap:Ethernet  HWaddr 00:D0:93:80:12:34
          inet addr:192.168.1.198  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0xe00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

#

Current config is PPCboot with SCC1 ,the result is eth0 can work but eth1 is bad!

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Why FEC and SCC1 can not work at the same time?

[Ricardo Scop]

Zhongqx,

Probably there some is initialization missing/misconfigured both in FEC
and SCC enet drivers for your board. Main candidates are I/O pins
configuration and/or clock selection.

HTH,

Ricardo Scop                            mailto:scop@digitel.com.br

------------------------------------------------------------------
It might look like I'm doing nothing, but at the cellular level I'm
really quite busy.

Tuesday, September 17, 2002, 4:49:44 AM, you wrote:


z> Hello,every one
z>     Hello Wolf gang thank you for help!my ramdisk problem has passed!I use linux-2.4.4-2002-02-14 kernel and all is ok!but I dont understand why linux-2.4.18 is not ok.


z> Now I meet a new problem! it is very strange!
z> I want to use FEC(100M) and SCC1(10M) interface,but they can not work together.
z>      When I use ppcboot with CONFIG_SCC1_ENET defined , boot linux ,then SCC1 is ok,when I ping FEC (I config it ip address is 192.168.2.221) it displayed messaged "time out".
z>      When I use ppcboot with CONFIG_FEC_ENET  defined,  boot linux ,then FEC is ok, when I
z> ping SCC( I config it ip address is 192.168.1.198) it displayed messaged also "time out".

z> Can you someone give help?thank you in advanced! the following is the linux output:

<snip>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Why FEC and SCC1 can not work at the same time?

[Wolfgang Denk]

In message <001001c25e1e$c9c33ac0$7301a8c0@zhongqx> you wrote:
>
> I want to use FEC(100M) and SCC1(10M) interface,but they can not work together.

They can.

> eth0: CPM ENET Version 0.2 on SCC1, 00:d0:93:00:12:34
> eth1: FEC ENET Version 0.2, FEC irq 3, MII irq 4, addr 00:d0:93:80:12:34

Please be aware that both interfaces use the same MAC  address.  This
is ok as long as you don;t try to connect bioth to the same subnet.

> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 40k init
> init started:  BusyBox v0.60.2 (2002.07.18-17:16+0000) multi-call SIOCADDRT: Net
> work is unreachable
>
>     ******(What reason ? when this message output?)

Well, it  makes  little  sense  to  guess  how  you  ifconfig'ed  the
interfaces, please provide more information.

My bet is that you tired to run  both  ethernet  ports  in  the  same
network,  and  that  you're  experiencing  a  conflict  caused by two
identical MAC addresses.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"I find this a nice feature but it is not according to  the  documen-
tation. Or is it a BUG?"   "Let's call it an accidental feature. :-)"
                       - Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Why FEC and SCC1 can not work at the same time?

[zhongqx]

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "zhongqx" <zhongqx@guoguang.com.cn>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, September 18, 2002 4:10 AM
Subject: Re: Why FEC and SCC1 can not work at the same time?
Sir ,
Thank you for your help,but I disagree with your in some point.

First, I did not use the same MAC address, eth0 is 00:d0:93:00:12:34 and eth1 is 00:d0:93:80:12:34  ,one is 00:12::34 and one is 80:12:34,are they in the same?

Second , I did not use both ethernet port to connect the same network ,one is 192.168.1.X and other is 192.168.2.X ,netmask is 255.255.255.0.

The third, I  ifconfiged my interface in /etc/inid.d/rcS file,my rcS file is:


#!/bin/sh

mount -t proc proc /proc
ifconfig lo 127.0.0.1 netmask 255.0.0.0
ifconfig eth0 192.168.2.221 netmask 255.255.255.0
ifconfig eth1 192.168.1.198 netmask 255.255.255.0

route add default gw 192.168.2.1 eth1


while [ 1 ]
do
        /bin/sh
done

My inittab file is:

# /etc/inittab: init configuration.

# The default runlevel.
#hw id:3:initdefault:

# Boot-time system configuration/initialization script.
#si::sysinit:/etc/init.d/rcS
::sysinit:/etc/init.d/rcS



Route information is here:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     *               255.255.255.0   U     0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:D0:93:00:12:34
          inet addr:192.168.2.221  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:41 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3677 (3.5 kb)  TX bytes:0 (0.0 b)
          Base address:0x3c00

eth1      Link encap:Ethernet  HWaddr 00:D0:93:80:12:34
          inet addr:192.168.1.198  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0xe00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

#

Thank you very much again,hope to hear from you soon!

> In message <001001c25e1e$c9c33ac0$7301a8c0@zhongqx> you wrote:
> >
> > I want to use FEC(100M) and SCC1(10M) interface,but they can not work together.
>
> They can.
>
> > eth0: CPM ENET Version 0.2 on SCC1, 00:d0:93:00:12:34
> > eth1: FEC ENET Version 0.2, FEC irq 3, MII irq 4, addr 00:d0:93:80:12:34
>
> Please be aware that both interfaces use the same MAC  address.  This
> is ok as long as you don;t try to connect bioth to the same subnet.
>
> > VFS: Mounted root (ext2 filesystem).
> > Freeing unused kernel memory: 40k init
> > init started:  BusyBox v0.60.2 (2002.07.18-17:16+0000) multi-call SIOCADDRT: Net
> > work is unreachable
> >
> >     ******(What reason ? when this message output?)
>
> Well, it  makes  little  sense  to  guess  how  you  ifconfig'ed  the
> interfaces, please provide more information.
>
> My bet is that you tired to run  both  ethernet  ports  in  the  same
> network,  and  that  you're  experiencing  a  conflict  caused by two
> identical MAC addresses.
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> "I find this a nice feature but it is not according to  the  documen-
> tation. Or is it a BUG?"   "Let's call it an accidental feature. :-)"
>                        - Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Why FEC and SCC1 can not work at the same time?

[Rick Hunnicutt]

This looks like it may be a simple network issue. You have eth0 on the
192.168.1.X subnet. The subnet mask is set to 255.255.255.0 meaning it can
see all other 192.168.1.X IP's. eth1 is set to 192.168.2.X subnet with the
same subnet  mask so he only sees other IP's on the 192.168.2.X subnet. Your
gateway is 192.168.2.1 for eth1. Is this gateway able to reach both
networks? Have you tried making these on the same network (192.168.1.X) and
trying to ping them?

Rick Hunnicutt


> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf
> Of zhongqx
> Sent: Tuesday, September 17, 2002 5:32 PM
> To: Wolfgang Denk
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: Why FEC and SCC1 can not work at the same time?
>
>
>
> ----- Original Message -----
> From: "Wolfgang Denk" <wd@denx.de>
> To: "zhongqx" <zhongqx@guoguang.com.cn>
> Cc: <linuxppc-embedded@lists.linuxppc.org>
> Sent: Wednesday, September 18, 2002 4:10 AM
> Subject: Re: Why FEC and SCC1 can not work at the same time?
> Sir ,
> Thank you for your help,but I disagree with your in some point.
>
> First, I did not use the same MAC address, eth0 is
> 00:d0:93:00:12:34 and eth1 is 00:d0:93:80:12:34  ,one is
> 00:12::34 and one is 80:12:34,are they in the same?
>
> Second , I did not use both ethernet port to connect the same
> network ,one is 192.168.1.X and other is 192.168.2.X ,netmask
> is 255.255.255.0.
>
> The third, I  ifconfiged my interface in /etc/inid.d/rcS
> file,my rcS file is:
>
>
> #!/bin/sh
>
> mount -t proc proc /proc
> ifconfig lo 127.0.0.1 netmask 255.0.0.0
> ifconfig eth0 192.168.2.221 netmask 255.255.255.0
> ifconfig eth1 192.168.1.198 netmask 255.255.255.0
>
> route add default gw 192.168.2.1 eth1
>
>
> while [ 1 ]
> do
>         /bin/sh
> done
>
> My inittab file is:
>
> # /etc/inittab: init configuration.
>
> # The default runlevel.
> #hw id:3:initdefault:
>
> # Boot-time system configuration/initialization script.
> #si::sysinit:/etc/init.d/rcS
> ::sysinit:/etc/init.d/rcS
>
>
>
> Route information is here:
>
> # route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric
> Ref    Use Iface
> 192.168.2.0     *               255.255.255.0   U     0
> 0        0 eth0
> 192.168.1.0     *               255.255.255.0   U     0
> 0        0 eth1
> # ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:D0:93:00:12:34
>           inet addr:192.168.2.221  Bcast:192.168.2.255
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:41 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:3677 (3.5 kb)  TX bytes:0 (0.0 b)
>           Base address:0x3c00
>
> eth1      Link encap:Ethernet  HWaddr 00:D0:93:80:12:34
>           inet addr:192.168.1.198  Bcast:192.168.1.255
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Base address:0xe00
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> #
>
> Thank you very much again,hope to hear from you soon!


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Why FEC and SCC1 can not work at the same time?

[Dave Ellis]

On Tuesday, September 17, 2002 zhongqx wrote:
> Now I meet a new problem! it is very strange!
> I want to use FEC(100M) and SCC1(10M) interface,but they can
> not work together.
>      When I use ppcboot with CONFIG_SCC1_ENET defined , boot
> linux ,then SCC1 is ok,when I ping FEC (I config it ip
> address is 192.168.2.221) it displayed messaged "time out".
>      When I use ppcboot with CONFIG_FEC_ENET  defined,  boot
> linux ,then FEC is ok, when I
> ping SCC( I config it ip address is 192.168.1.198) it
> displayed messaged also "time out".

For FADS PPCBoot sets up both BCSR1 and BCSR4 in cpu/mpc8xx/scc.c.
In Linux 2.4.18 only BCSR1 is configured in arch/ppc/8xx_io/enet.c
Maybe configuring BCSR4 in enet.c would help.

Dave

Dave Ellis
~~~~~~~~~~~~~~~~~~~~~~~~~~
SIXNET - "Leading the Industrial Ethernet Revolution"
331 Ushers Road,   P.O. Box 767, Clifton Park, NY 12065 USA
Tel +1 (518) 877-5173   Fax +1 (518) 877-8346
Email me at: dge@sixnetio.com
Detailed product info: www.sixnetio.com
~~~~~~~~~~~~~~~~~~~~~~~~~~

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Why FEC and SCC1 can not work at the same time?

[zhongqx]

Sir,
   thank you very much,
   what you said is very right,fix ppcboot just like you said,and the proplem disappear!
   thank you again!
----- Original Message -----
From: "Dave Ellis" <DGE@sixnetio.com>
To: "'zhongqx'" <zhongqx@guoguang.com.cn>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, September 18, 2002 4:20 AM
Subject: RE: Why FEC and SCC1 can not work at the same time?

> On Tuesday, September 17, 2002 zhongqx wrote:
> > Now I meet a new problem! it is very strange!
> > I want to use FEC(100M) and SCC1(10M) interface,but they can
> > not work together.
> >      When I use ppcboot with CONFIG_SCC1_ENET defined , boot
> > linux ,then SCC1 is ok,when I ping FEC (I config it ip
> > address is 192.168.2.221) it displayed messaged "time out".
> >      When I use ppcboot with CONFIG_FEC_ENET  defined,  boot
> > linux ,then FEC is ok, when I
> > ping SCC( I config it ip address is 192.168.1.198) it
> > displayed messaged also "time out".
>
> For FADS PPCBoot sets up both BCSR1 and BCSR4 in cpu/mpc8xx/scc.c.
> In Linux 2.4.18 only BCSR1 is configured in arch/ppc/8xx_io/enet.c
> Maybe configuring BCSR4 in enet.c would help.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Why FEC and SCC1 can not work at the same time?

[Wolfgang Denk]

In message <001801c25ed6$1c389e00$7301a8c0@zhongqx> you wrote:
>
>    thank you very much,
>    what you said is very right,fix ppcboot just like you said,and the proplem disappear!

Oops??? Dave did not mention any changes to PPCBoot, it seems.

PPCBoot is not to blame for your trouble.

> ----- Original Message -----
> From: "Dave Ellis" <DGE@sixnetio.com>
> To: "'zhongqx'" <zhongqx@guoguang.com.cn>
> Cc: <linuxppc-embedded@lists.linuxppc.org>
> Sent: Wednesday, September 18, 2002 4:20 AM
> Subject: RE: Why FEC and SCC1 can not work at the same time?
>
...
> > For FADS PPCBoot sets up both BCSR1 and BCSR4 in cpu/mpc8xx/scc.c.
> > In Linux 2.4.18 only BCSR1 is configured in arch/ppc/8xx_io/enet.c
> > Maybe configuring BCSR4 in enet.c would help.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
It all seemed, he thought, to be rather a lot of  trouble  to  go  to
just sharpen a razor blade.  - Terry Pratchett, _The Light Fantastic_

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/