Rtl8139 problem on mds8377E, vxworks6.6 - VxWorks

Hi All,

I have a question in Configuring Network Interface.



My target board is M8377, and I intend to add a PCI Ethernet Card, RTL-8139, on it, and make it running (it’s not for the booting!).



In the “Kernel Configuration”, I include the components “INCLUDE_RTL8139_VXB_END” and “INCLUDE_RTL8201PHY” firstly, and then as it says in chapter 3.3.1 in “Wind River Network Stack for VxWorks 6 Programmer’s Guide, 6.6 vol.3”, I include “INCLUDE_IPNET_IFCONFIG_2”, and at the same time set the vale of “IFCONFIG_2” as "ifname","devname rtl0","inet 10.16.120.11", "gateway driver" strictly under the direction of guide pdf.



When I start the target board, vxworks is working well. And, when I use the command “vxBusShow”, it print out information like this:



-------------------------------------------------

Registered Bus Types:

MII_Bus @ 0x001d57c0

PCI_Bus @ 0x001d38d4

Local_Bus @ 0x001d3994



Registered Device Drivers:

ppcIntCtlr at 0x001d4bdc on bus Local_Bus, funcs @ 0x001d4bd0

VxBus version 2

quiccIntCtlr at 0x001d5430 on bus Local_Bus, funcs @ 0x001d53fc

motetsec at 0x001d5258 on bus Local_Bus, funcs @ 0x001d52d0

ns16550 at 0x001d5a8c on bus Local_Bus, funcs @ 0x001d5a1c

ns16550 at 0x001d5a44 on bus PCI_Bus, funcs @ 0x001d5a1c

rtl at 0x001d50e0 on bus PCI_Bus, funcs @ 0x001d5160

rtl8201Phy at 0x001d5964 on bus MII_Bus, funcs @ 0x001d59a4

mv88E1x11Phy at 0x001d5868 on bus MII_Bus, funcs @ 0x001d58a8

bcm54xxPhy at 0x001d57f8 on bus MII_Bus, funcs @ 0x001d5838

genericPhy at 0x001d58f8 on bus MII_Bus, funcs @ 0x001d5938

miiBus at 0x001d5778 on bus PCI_Bus, funcs @ 0x001d57dc

miiBus at 0x001d5738 on bus Local_Bus, funcs @ 0x001d57dc

m83xxPciEx at 0x001d37ec on bus Local_Bus, funcs @ 0x001d37e0

VxBus version 2

m83xxPci at 0x001d509c on bus Local_Bus, funcs @ 0x001d5090

VxBus version 2

plbCtlr at 0x001d39b0 on bus Local_Bus, funcs @ 0x001e0cb4



Busses and Devices Present:

Local_Bus @ 0x001ecba0 with bridge @ 0x001d39f0

Device Instances:

quiccIntCtlr unit 0 on Local_Bus @ 0x001edb60 with busInfo 0x00000000

ppcIntCtlr unit 0 on Local_Bus @ 0x001edc60 with busInfo 0x00000000

ns16550 unit 0 on Local_Bus @ 0x001edd60 with busInfo 0x00000000

ns16550 unit 1 on Local_Bus @ 0x001edf60 with busInfo 0x00000000

m83xxPci unit 0 on Local_Bus @ 0x001ee160 with busInfo 0x001ed260

m83xxPciEx unit 0 on Local_Bus @ 0x001ee460 with busInfo 0x00000000

m83xxPciEx unit 1 on Local_Bus @ 0x001ee760 with busInfo 0x00000000

motetsec unit 0 on Local_Bus @ 0x001eea60 with busInfo 0x00000000

motetsec unit 1 on Local_Bus @ 0x001f1b60 with busInfo 0x00000000

miiBus unit 1 on Local_Bus @ 0x001f2660 with busInfo 0x001ed560

miiBus unit 2 on Local_Bus @ 0x001f2a60 with busInfo 0x001ed5a0

Orphan Devices:

PCI_Bus @ 0x001ed260 with bridge @ 0x001ee160

Device Instances:

rtl unit 0 on PCI_Bus @ 0x001f1d60 with busInfo 0x00000000

miiBus unit 0 on PCI_Bus @ 0x001f2060 with busInfo 0x001ed520

Orphan Devices:

(null) unit 0 on PCI_Bus @ 0x001f1c60 with busInfo 0x00000000

MII_Bus @ 0x001ed520 with bridge @ 0x001f2060

Device Instances:

rtl8201Phy unit 0 on MII_Bus @ 0x001f2260 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x001ed560 with bridge @ 0x001f2660

Device Instances:

genericPhy unit 0 on MII_Bus @ 0x001f2860 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x001ed5a0 with bridge @ 0x001f2a60

Device Instances:

Orphan Devices:

-------------------------------------------------



So, I see rtl is working well, both the device and the driver are in the right way. And then, I use command “ifconfig” to check the status of Network Interfaces, I got the information like this:



-------------------------------------------------

lo0 Link type:Local loopback Queue:none

inet 127.0.0.1 mask 255.255.255.255

inet 224.0.0.1 mask 240.0.0.0

UP RUNNING LOOPBACK MULTICAST

MTU:1500 metric:1 VR:0 ifindex:1

RX packets:0 mcast:0 errors:0 dropped:0

TX packets:0 mcast:0 errors:0

collisions:0 unsupported proto:0

RX bytes:0 TX bytes:0



motetsec0 Link type:Ethernet HWaddr 00:04:9f:a0:aa:00 Queue:none

capabilities: TXCSUM TX6CSUM VLAN_MTU

inet 10.16.120.12 mask 255.0.0.0 broadcast 10.255.255.255

inet 224.0.0.1 mask 240.0.0.0

UP RUNNING SIMPLEX BROADCAST MULTICAST

MTU:1500 metric:1 VR:0 ifindex:2

RX packets:359 mcast:2 errors:0 dropped:9

TX packets:166 mcast:0 errors:0

collisions:0 unsupported proto:0

RX bytes:416k TX bytes:9030



rtl0 Link type:Ethernet HWaddr 00:40:f4:27:b1:9c Queue:none

capabilities: VLAN_MTU

inet 224.0.0.1 mask 240.0.0.0

UP SIMPLEX BROADCAST MULTICAST

MTU:1500 metric:1 VR:0 ifindex:3

RX packets:0 mcast:0 errors:0 dropped:0

TX packets:0 mcast:0 errors:0

collisions:0 unsupported proto:0

RX bytes:0 TX bytes:0

-------------------------------------------------



It’s not normal any longer. It’s right that, there should be 3 END on the board, Loopback, Motetsec (on-board), and our Rtl-8139,

But as I configured before, rtl0 should be like this as I expected:



-------------------------------------------------

rtl0 Link type:Ethernet HWaddr 00:40:f4:27:b1:9c Queue:none

capabilities: VLAN_MTU

inet 10.16.120.11 mask 255.0.0.0 broadcast 10.255.255.255

inet 224.0.0.1 mask 240.0.0.0

UP RUNNING SIMPLEX BROADCAST MULTICAST

… …

-------------------------------------------------



I wonder if I have made any faults on configuring for the network interface, as in vxworks 6.6, the driver of rtl8139 is no longer a Legacy Device Driver, it will be added onto vxbPci automatically if we include it in “Kernel Configuration”. We don’t need to modify our BSP files, right?

In a word, i wanna to know that, why rtl8139 is "UP" but not "RUNNING"? i sweat i've connect it with ethernet cable... - -!

I will appreciate for any answer about this problem!

Thank you very much!