This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Problems receiving packets on i82559


Hi Andrew,

Thanx for ur help. to answer some of ur questions.....

We have checked the MAC address. It is the same as the MAC address we get
when using Redboot. It is printing the MAC address correctly.

We r able to send packets out without calling init_all_network_interfaces.
But the problem is with receiving. The other thing is we dont want the
application to make a call to init_all_network_interfaces or any other
similar function. Is it possible to have the interface up continously so tht
we dont need to call any function as part of the application?

We called eth_drv_start at the end of our initialization procedure. As a
result of this we received some interrupts but this again stopped after
sometime.

Our hardware platform is an i386 pc with an i82559 card.

Nikhil

-----Original Message-----
From: Andrew Lunn [mailto:andrew dot lunn at ascom dot ch]
Sent: Tuesday, March 11, 2003 3:56 PM
To: Nikhil R.
Cc: Andrew Lunn; ecos-discuss at sources dot redhat dot com
Subject: Re: [ECOS] Problems receiving packets on i82559


On Tue, Mar 11, 2003 at 03:38:38PM +0530, Nikhil R. wrote:
> Hi Andrew,
> 
> As per ur earlier mail we noticed that we were receiving interrupts only
> during the send process. So we called eth_drv_start at the beginning of our
> initialization procedure and this made us receive some interrupts but
stopped
> again after sometime.
> 
> If we look at the BSD code, all the applications call the function
> init_all_network_interfaces. Without calling this function  it seems like
> even the BSD code does not receive any interrupts.


If you don't call init_all_network_interfaces, the interface will be
down. You cannot send/receive IP packets with the interface down
etc. This is explained in the documentation about the network stacks.

Debug the system using one of the standard test programs, eg
ping_test.c. That way you know at least the test code works correctly.

Gary suggested that the MAC address could be wrong. Have you
investigated this? Have you enabled the debug code in the i82559
driver so it prints out the MAC address etc. Is it valid? 

I suggested you check the IRQ number being registered. Have you done
this? Is it correct for your hardware?

What is you hardware platform anyway?

     Andrew


DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]