RE: 82559 driver & no packets in/out

Possibly similar problem encountered when we were porting driver code to
PPC405 for PPCBoot. Our setup did not have a serial eeprom to configure
part, this was done through sw (including mac addr). Driver reset part and
tried to send packets relying on many default register settings. Found that
one bit in a configuration register defaults to 0, but needs to be 1 for
'559. It is bit 0 of byte 8 (believe this is the same data for configuration
eeprom) which is called 503#/MII.

Symptoms were part would process tx packets without a complaint but nothing
was ever seen on the interface (link was ok). Finally dumped statistic
registers, and had indication that there was failed tx due to loss of
carrier sense (?). Finally had to just verify all registers were being
configured properly which was where I found this bit needing to be
configured.

-------------------------------------------------------
From: "Agarwal, Lomesh" <[email protected]>
To: "'[email protected]'" <[email protected]>,
   "ecos-discuss (E-Mail)" <[email protected]>
Date: Thu, 30 May 2002 13:53:15 -0700
Subject: [eepro100] Problem with 82559 driver

Hi,
I took 82559 driver for IQ80310 RedBoot and ported it to my platform.
I82559_init passes successfully and I can find the device and its BARs are
initialized properly. But the problem is that I don't see any data packet
coming out on wire (I hooked the NIC to IXIA which is a packet analyzer)
when I try to ping a host. I am using static IP address. Another thing is
that my board has 82559ER in place of 82559.
When I do a ping TxMachine function is called and it starts a tx operation.
Then I see TxMachine being called again. This time it goes to tx_in_progress
block and there I find SCB status as 0x10 and it assumes that CU is idle.
But I don't see any packet coming out.
Can someone give me some hint as to what may be possibly wrong?
Also can someone point me to the document which has all the "command unit
command" and "receive unit command". I downloaded 82559er datasheet from
Intel website but that doesn't
have this info.

Thanks,
Lomesh