public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Lopy <lpz@laposte.net>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Réf. : Re: [ECOS] Problem with TCP/IP stack
Date: Thu, 10 Jan 2008 13:36:00 -0000	[thread overview]
Message-ID: <47861F3B.5090803@mlbassoc.com> (raw)
In-Reply-To: <19742966.42231199971885201.JavaMail.www@wwinf8204>

Note: this reply belongs on the eCos discussion list, not me personally.

Lopy wrote:
> Hi, 
> 
>  
> 
> We have experimented this kind of problem, but only with MultiCast, or 
> with big packets, but I don't think that is the same problem than you 
> ask for.
> 
>  
> 
> A/ If the DHCP server don't give the opt 3 (GATEWAY), it's not possible 
> to send MultiCast packets. But there is no problem for sending unicast 
> packet.

As the original message did not mention multicast, I doubt this is relevant.

> B/ We have another problem (bypassed but not fixed), who is than big 
> packets ( who need to be fragmented ) are not send. But we think that is 
> a driver problem, so if you don't have the same microprocessor perhaps 
> you don't have the same problem.
> 
>  
> 
> We work with MPC8270 on a own designed board.

Can you elaborate on your problems?  Are you using the FCC driver
code which is in the public eCos repository?

> -----ecos-discuss-owner@ecos.sourceware.org a écrit : -----
> 
>     Pour : Antoine Zen-Ruffinen <antoine.zen@gmail.com>
>     De : Gary Thomas <gary@mlbassoc.com>
>     Envoyé par : ecos-discuss-owner@ecos.sourceware.org
>     Date : 10/01/2008 14:17
>     cc : ecos-discuss@ecos.sourceware.org
>     Objet : Re: [ECOS] Problem with TCP/IP stack
> 
>     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

           reply	other threads:[~2008-01-10 13:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <19742966.42231199971885201.JavaMail.www@wwinf8204>]

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=47861F3B.5090803@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=lpz@laposte.net \
    /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).