From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30736 invoked by alias); 10 Jan 2008 13:55:56 -0000 Received: (qmail 30721 invoked by uid 22791); 10 Jan 2008 13:55:55 -0000 X-Spam-Check-By: sourceware.org Received: from 204-133-123-27.dia.static.slbbi.com (HELO mail.chez-thomas.org) (204.133.123.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Jan 2008 13:55:34 +0000 Received: by mail.chez-thomas.org (Postfix, from userid 999) id C5BF01950218; Thu, 10 Jan 2008 06:55:30 -0700 (MST) Received: from hermes.chez-thomas.org (hermes_local [192.168.1.101]) by mail.chez-thomas.org (Postfix) with ESMTP id 82D5819500E6; Thu, 10 Jan 2008 06:55:27 -0700 (MST) Message-ID: <478623CE.9030406@mlbassoc.com> Date: Thu, 10 Jan 2008 13:55:00 -0000 From: Gary Thomas User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Antoine Zen-Ruffinen CC: eCos Discussion References: <2cbbd8de0801100509x43959b34ka8e8e6f35dd081e5@mail.gmail.com> <47861B06.30303@mlbassoc.com> <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com> In-Reply-To: <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Problem with TCP/IP stack X-SW-Source: 2008-01/txt/msg00044.txt.bz2 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 : >> 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