On Mon, 2005-03-07 at 16:41 -0800, Badri Sampathkumar wrote:
Hi:
I have just modified the ping_lo_test.c application to ping an external
address instead of the loopback address. I run only this application.
My board is sending out a gratituous ARP on startup and when the
application
opens a RAW socket and sends an ICMP echo req, the stck sends
an ARP request. It gets back an ARP reply that gets queued up in the
arpintrq and seems to never get processed. it remains in the queue.
I net isr for ARP , is never getting called. I think register_netisr()
itself is not getting called.
The cyg_net_init() call that handles isr's is not getting a chance to
run..
Try running the standard tests, like ping_test.c, unchanged. If your
network is set up reasonably (a DHCP server that can return a valid
'server' IP), it should run and tell you a lot.
You also did not tell us how you configured your kernel and whether
or not you have verified eCos basic operation (have you run any other
multi-threaded tests)?
thanks,
/Badri
----- Original Message -----
From: "Gary Thomas" <gary@mlbassoc.com>
To: "Badri Sampathkumar" <badri@atheros.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Sent: Monday, March 07, 2005 3:54 PM
Subject: Re: [ECOS] ecos net stack query
> On Mon, 2005-03-07 at 15:48 -0800, Badri Sampathkumar wrote:
>> Hi All,
>>
>> I am using the Free BSB networking stack as part of my BSP for my
>> custom
>> board.
>> I am trying to bringup the Ethernet driver for the board.
>>
>> I am able to successfuly tx/rx packets from/to my ethernet hardware
>> driver.
>>
>> When I try to give the received pkts to the upper layers of the tcp/ip
>> stack
>> for e.g ARP, IP modules, the packets get queued up into their
>> respective
>> queues (arpintrq, ipintrq etc) and they are not processed from there
>> on.
>> They seem to be remaining in the queue for a long time. so i am not
>> able
>> to
>> ping another m/c from my board or vice versa.
>>
>> I have confirmed that the pkts are received correctly in the hardware
>> driver
>> by running ethereal on the peer host and then cross checking the hex
>> dump
>> of
>> the
>> pkts between the hw driver and the ethereal dump.
>
> What else do you have running?
> How did you configure your kernel?
> Have you tried the standard network tests? That's the best way
> to make sure the stack is working from the start.
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
>
>
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss