Quantcast
Channel: Embedded Community : All Content - All Communities
Viewing all articles
Browse latest Browse all 3032

i210 Driver for VxWorks 5.5.1

$
0
0

Hi,

 

I am trying to get the i210 to work with the existing driver for the 82574 on VxWorks 5.5.1 which is built on the original 82643 driver.  Everything looks good (to me) but no data is actually transmitted.  The device appears to be able to receive ok as there is evidence in the counters and these match reasonably well with the counters in the Cisco switch for the port it is connected to. We have a link at both ends and auto-negotiation is successful.

 

The VxWorks driver uses queue 0 only and it creates the context on each send.

 

Below are the main registers of interest - VxWorks only modifies registers 0, 4 and 9 in the PHY.

 

10:02:38 gei82543EndStart:Link is up

10:02:38 phy  reg 0: 00001000

10:02:38 phy  reg 1: 0000796d

10:02:38 phy  reg 2: 00000141

10:02:38 phy  reg 3: 00000c00

10:02:38 phy  reg 4: 00000de1

10:02:38 phy  reg 5: 000043e1

10:02:38 phy  reg 6: 00000005

10:02:38 phy  reg 7: 00002001

10:02:38 phy  reg 8: 00000000

10:02:38 phy  reg 9: 00000300

10:02:38 phy  reg 10: 00004000

10:02:38 phy  reg 15: 00003000

10:02:38 phy  reg 17: 00007c08

10:02:38 gei82543EndStart: TCTL is: a40400fa

10:02:38 gei82543EndStart: STATUS is: 00280743

10:02:38 gei82543EndStart: CTRL_EXT is: 101c0000

10:02:38 gei82543EndStart: CTRL is: 00001941

10:02:38 gei82543EndStart: IPCNFG is: 0000000f

10:02:38 gei82543EndStart: PHPM is: 0000019d

10:02:38 gei82543EndStart: TXDCTL is: 02010000

 

I would appreciate any ideas as to what may cause this behaviour.

 

Thank you.


Viewing all articles
Browse latest Browse all 3032

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>