From: Gary Thomas <gary@mlbassoc.com>
To: Antoine Zen-Ruffinen <antoine.zen@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Problem with TCP/IP stack
Date: Thu, 10 Jan 2008 13:55:00 -0000 [thread overview]
Message-ID: <478623CE.9030406@mlbassoc.com> (raw)
In-Reply-To: <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com>
Please keep your replies on the eCos list!
**EVERYONE** please get this straight. Replies made by me on the
eCos discussion list must be followed up on the eCos discussion list
unless I invite private replies. This way everyone benefits, not
just the interested party. Private email support consultation and
support is available, but only with a contract.
Antoine Zen-Ruffinen wrote:
> The target platform is an embed PC with NS dp83816 NIC. I've port the
> eCos driver my self for the PC platform.
>
> I configure eCos with the configtool, just using the template I made
> and the "net" package.
>
> No, I didn't run a standard eCos network test program. But I build an
> redboot with this configuration. If I type ping -n 1000 -r 1 -h
> 192.168.165.18 (is my host PC) everything went fine !
This is only partly relevant - RedBoot uses a completely different
network stack than normal eCos applications. Also, RedBoot does
not use interrupts, which the eCos stacks rely on.
>
> I know that nothing was send : 1 becose network activity led doesn't
> blink, 2 I monitor network with Wireshark (Ethereal). the monitoring
> trace show the TFTP exchange and the DHCP init but nothing more. It
> look like this :
> No. Time Source Destination Protocol Info
> 69504 25.515675 192.168.165.18 192.168.165.253 TFTP
> Data Packet, Block: 452
> 69505 25.516279 192.168.165.253 192.168.165.18 TFTP
> Acknowledgement, Block: 452
> 69506 25.516289 192.168.165.18 192.168.165.253 TFTP
> Data Packet, Block: 453
> 69507 25.516662 192.168.165.253 192.168.165.18 TFTP
> Error Code, Code: Not defined, Message: redboot
> tftp_stream_terminate
> 69508 25.826093 0.0.0.0 255.255.255.255 DHCP
> DHCP Discover - Transaction ID 0x6c1dfce9
> 69511 26.074789 0.0.0.0 255.255.255.255 DHCP
> DHCP Discover - Transaction ID 0x6c1dfce9
> 69512 26.304739 0.0.0.0 255.255.255.255 DHCP
> DHCP Discover - Transaction ID 0x6c1dfce9
> 69514 26.451407 0.0.0.0 255.255.255.255 DHCP
> DHCP Request - Transaction ID 0x6c1dfde9
> 69516 26.839890 Olicom_c8:1d:6c Broadcast ARP
> Who has 192.168.165.254? Gratuitous ARP
>
Did your eCos application print anything about the DHCP transaction?
I'm betting that it did not (which would imply you are having trouble
with receive interrupts from your driver)
>
> 2008/1/10, Gary Thomas <gary@mlbassoc.com>:
>> Antoine Zen-Ruffinen wrote:
>>> Hi List folks,
>>>
>>> I've a problem with the TCP/IP stack:
>>> - I use TFTP to load my program in redboot. That work fine.
>>> - My application start, call init_all_network_interfaces(), it do the
>>> DHCP stuff. That work fine.
>>> - Then I open a socket and try to send / receive data. No packet is even send.
>>>
>>> Does someone has already seen such problem ?
>>> Any idea ?
>> We'll need more data than this in order to help.
>> * What's the target platform?
>> * How did you configure eCos for your failing application?
>> * Have you run any of the standard eCos network test programs?
>> * How do you know nothing was sent? What sort of debugging
>> have you tried so far?
--
------------------------------------------------------------
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
next prev parent reply other threads:[~2008-01-10 13:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 13:09 Antoine Zen-Ruffinen
2008-01-10 13:18 ` Gary Thomas
[not found] ` <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com>
2008-01-10 13:55 ` Gary Thomas [this message]
2008-01-10 14:15 ` Antoine Zen-Ruffinen
2008-01-10 15:32 ` Antoine Zen-Ruffinen
2008-01-11 8:48 ` Antoine Zen-Ruffinen
2008-01-11 12:38 ` Antoine Zen-Ruffinen
2008-01-11 12:47 ` Gary Thomas
2008-01-11 12:52 ` Andrew Lunn
2008-01-11 15:43 ` Antoine Zen-Ruffinen
2008-01-11 15:59 ` Gary Thomas
2008-01-11 16:08 ` Antoine Zen-Ruffinen
2008-01-11 16:29 ` Gary Thomas
2008-01-11 16:38 ` Antoine Zen-Ruffinen
2008-01-11 16:39 ` Antoine Zen-Ruffinen
2008-01-11 16:46 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 22:44 [ECOS] Problem with TCP/IP Stack Your Name
2001-01-26 10:47 [ECOS] problem with TCP/IP stack Gary Guangyu Pei
2001-01-26 13:46 ` Gary Thomas
2001-01-26 16:39 ` Gary Guangyu Pei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=478623CE.9030406@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=antoine.zen@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).