public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: C B <csb_80@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] networking support for my eCos application
Date: Fri, 02 Nov 2007 19:08:00 -0000	[thread overview]
Message-ID: <472B7580.4080409@mlbassoc.com> (raw)
In-Reply-To: <BAY105-W23333C084A205F22C0380FEA8D0@phx.gbl>

C B wrote:
> Wow.  Thanks for the quick response.
> 
> I'm using the 2.0 release of eCos, not the latest from CVS although I can easily switch if you think it may be part of my problem (or future ones...)

Yes, I would definitely suggest that you update to the CVS tree
(release 2.0 is nearing 5 years old!)

Once you've done that, I'd also suggest that you try some simple
things.  This sequence should work and generate a test that you
can try on your hardware:
  % ecosconfig new eb9261 net
  % ecosconfig tree
  % make; make -C net/common/current tests TESTS=tests/ping_test

Note: it's not clear to me why your tree has its own 'eb9261-net'
template as this should not be necessary.  Using .ecm files is
a much better approach.

n.b. of course you can do the steps above using the config tool,
but using ecosconfig is much more concise and easier to explain :-)

>> Date: Fri, 2 Nov 2007 12:41:25 -0600
>> From: gary@mlbassoc.com
>> To: csb_80@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: [ECOS] networking support for my eCos application
>>
>> C B wrote:
>>> I'm new to eCos and am trying to get some simple networking capabilities into an application that I've inherited. The eCos configuration I have appears to have the networking package included and yet when I attempt to link my application against the eCos libs I get several 'undefined reference' type errors. In particular:
>>>
>>> undefined reference to 'init_all_network_interfaces'
>>> undefined reference to 'eth0_up'
>>> undefined reference to 'eth0_bootp_data'
>>> undefined reference to 'inet_ntoa'
>>>
>>> It's some simple ftp client side stuff that is generating these errors but all I'd really like to be able to do is create and read data from a socket.
>>>
>>> I'm using the eCos Configuration Tool Version 2.11 in Windows XP and everything in the configuration builds fine. In the configuration view I have 'Basic networking framework' with 'INET support' checked under it, and 'OpenBSD TCP/IP Stack' and 'FTP client' also there.
>>>
>>> I've tried to provide the summary of what I'm doing but please ask if there is something I've left out that would be valuable. I've searched the archives and google'd a bunch but I'm unable to figure out a simple explanation for why the networking stuff doesn't seem to make it into my config.
>> It doesn't look like the network has been configured.
>>
>> What eCos sources are you using (latest from anon CVS is recommended)
>> Can you send your actual configuration? (use File->Export)
>>
>> Also, you probably should be using the FreeBSD network stack
>> as the OpenBSD stack is very old and no longer maintained.


-- 
------------------------------------------------------------
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:[~2007-11-02 19:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 18:54 C B
2007-11-02 19:08 ` Gary Thomas [this message]
2007-11-05 16:12   ` C B
2007-11-05 18:43     ` Andrew Lunn
     [not found]       ` <BAY105-W2585C1EB05E16C54EA73C5EA890@phx.gbl>
2007-11-06  8:34         ` Andrew Lunn
2007-11-08 20:01   ` C B
2007-11-08 21:05     ` Andrew Lunn
2007-11-09  9:22     ` [ECOS] " John Dallaway
2007-11-09 13:32       ` [ECOS] " C B
2007-11-09 18:48         ` C B
2007-11-09 18:55           ` Andrew Lunn
2007-11-12 11:52             ` C B
2007-11-12 12:27               ` Gary Thomas
2007-11-12 18:11                 ` C B
2007-11-14 13:30                   ` [ECOS] Adding xscale support to my eCos config C B
2007-11-14 14:05                     ` Andrew Lunn
2007-11-14 14:13                       ` Mark Salter
2007-11-14 15:23                       ` C B
2007-11-14 15:24                         ` Gary Thomas
2007-11-14 20:11                           ` C B
2007-11-14 20:42                             ` C B
2007-11-16 18:15                               ` [ECOS] Performance timing C B
2007-11-16 19:47                                 ` Gary Thomas
2007-11-16 19:55                                   ` C B
2007-11-17  7:07                                     ` Mike Arthur
2007-11-19  5:19                                       ` C B
2007-11-19 14:36                                         ` Gary Thomas
2007-11-22 13:39                                           ` [ECOS] eCos compatible with arm-elf-gcc version 4.1.1? C B
2007-11-22 14:28                                             ` Lars Poeschel
2007-11-22 16:42                                               ` C B
2007-11-27 14:38                                               ` C B
2007-11-28 13:24                                                 ` C B
     [not found]             ` <BAY105-W28BEA5A1C91693C8BE5C8FEA870@phx.gbl>
2007-11-12 12:07               ` [ECOS] RE: networking support for my eCos application Andrew Lunn
2007-11-12 18:05                 ` C B
  -- strict thread matches above, loose matches on Subject: below --
2007-11-08 23:33 [ECOS] " C B
2007-11-02 18:31 C B
2007-11-02 18:41 ` Gary Thomas

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=472B7580.4080409@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=csb_80@hotmail.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).