[ECOS] networking support for my eCos application

[ECOS] networking support for my eCos application

[C B]

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.
 
Thank you,
Chris

_________________________________________________________________
Peek-a-boo FREE Tricks & Treats for You!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] networking support for my eCos application

[Gary Thomas]

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

RE: [ECOS] networking support for my eCos application

[C B]

> Do an
>
> ecosconfig export foo.ecm
>
> and post foo.ecm.
>
> Also check that net/common/current/src/inet_ntoa.c is getting
> compiled and it is in the library install/lib/libtarget.a

I'll check the libtarget.a.  Here are the contents of foo.ecm:

------------------------------- begin foo.ecm -----------------------------------------
cdl_savefile_version 1;
cdl_savefile_command cdl_savefile_version {};
cdl_savefile_command cdl_savefile_command {};
cdl_savefile_command cdl_configuration { description hardware template package };
cdl_savefile_command cdl_package { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_component { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_option { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_interface { value_source user_value wizard_value inferred_value };

cdl_configuration eCos {
    description "" ;
    hardware    eb9261 ;
    template    net ;
    package -hardware CYGPKG_HAL_ARM current ;
    package -hardware CYGPKG_HAL_ARM_AT91 current ;
    package -hardware CYGPKG_HAL_ARM_AT91SAM9261 current ;
    package -hardware CYGPKG_IO_SERIAL_ARM_AT91 current ;
    package -hardware CYGPKG_IO_SPI current ;
    package -hardware CYGPKG_DEVS_SPI_ARM_AT91 current ;
    package -hardware CYGPKG_DEVS_SPI_ARM_EB9261 current ;
    package -hardware CYGPKG_DEVS_AT45_DATAFLASH_SPI current ;
    package -hardware CYGPKG_DEVS_ETH_EB9261 current ;
    package -hardware CYGPKG_DEVS_ETH_DAVICOM_DM9000A current ;
    package -template CYGPKG_HAL current ;
    package -template CYGPKG_IO current ;
    package -template CYGPKG_IO_SERIAL current ;
    package -template CYGPKG_INFRA current ;
    package -template CYGPKG_ISOINFRA current ;
    package -template CYGPKG_KERNEL current ;
    package -template CYGPKG_MEMALLOC current ;
    package -template CYGPKG_LIBC current ;
    package -template CYGPKG_LIBC_TIME current ;
    package -template CYGPKG_LIBC_STDLIB current ;
    package -template CYGPKG_LIBC_STRING current ;
    package -template CYGPKG_LIBC_I18N current ;
    package -template CYGPKG_LIBC_SETJMP current ;
    package -template CYGPKG_LIBC_STARTUP current ;
    package -template CYGPKG_LIBC_STDIO current ;
    package -template CYGPKG_LIBM current ;
    package -template CYGPKG_POSIX current ;
    package -template CYGPKG_IO_WATCHDOG current ;
    package -template CYGPKG_IO_WALLCLOCK current ;
    package -template CYGPKG_ERROR current ;
    package -template CYGPKG_IO_FILEIO current ;
    package -template CYGPKG_NET current ;
    package -template CYGPKG_NET_FREEBSD_STACK current ;
    package -template CYGPKG_NS_DNS current ;
    package -template CYGPKG_IO_ETH_DRIVERS current ;
    package -template CYGPKG_NET_SNTP current ;
};

cdl_option CYGHWR_HAL_ARM_AT91_FIQ {
    inferred_value 1
};

cdl_option CYGBLD_ISO_CTYPE_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_ERRNO_CODES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_ERRNO_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_FILETYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_STREAMS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_FILEOPS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_FILEACCESS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_FORMATTED_IO_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_CHAR_IO_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_DIRECT_IO_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_FILEPOS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDIO_ERROR_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDLIB_STRCONV_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDLIB_ABS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STDLIB_DIV_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRERROR_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRTOK_R_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRING_LOCALE_FUNCS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRING_BSD_FUNCS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRING_MEMFUNCS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRING_STRFUNCS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_STRUCTTIMEVAL_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_FNMATCH_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_POSIX_TIMER_TYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_POSIX_CLOCK_TYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_C_TIME_TYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_POSIX_TIMERS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_POSIX_CLOCKS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_C_CLOCK_FUNCS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_SIGNAL_NUMBERS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_SIGNAL_IMPL_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_SETJMP_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_SIGSETJMP_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_DIRENT_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_PTHREADTYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_PMUTEXTYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_BSDTYPES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_UTSNAME_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_SEMAPHORES_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_PTHREAD_IMPL_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_PTHREAD_MUTEX_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_POSIX_LIMITS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_OPEN_MAX_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_NAME_MAX_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_DNS_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_NETDB_PROTO_HEADER {
    inferred_value 1 
};

cdl_option CYGBLD_ISO_NETDB_SERV_HEADER {
    inferred_value 1 
};

cdl_option CYGIMP_KERNEL_SCHED_SORTED_QUEUES {
    inferred_value 1
};

cdl_option CYGSEM_KERNEL_SCHED_TIMESLICE_ENABLE {
    inferred_value 1
};

cdl_component CYGSEM_KERNEL_SCHED_ASR_SUPPORT {
    inferred_value 1
};

cdl_option CYGSEM_KERNEL_SCHED_ASR_GLOBAL {
    inferred_value 1
};

cdl_component CYGPKG_KERNEL_THREADS_DESTRUCTORS {
    inferred_value 1
};

------------------------------------ end foo.ecm -----------------------------------------
_________________________________________________________________
Climb to the top of the charts!  Play Star Shuffle:  the word scramble challenge with star power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_oct

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] networking support for my eCos application

[Andrew Lunn]

On Thu, Nov 08, 2007 at 03:00:59PM -0500, C B wrote:
> 
> 
> > 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
> 
> Thanks for your help (Andrew & Gary).  I think I'm getting closer.
> 
> I got the latest eCos from CVS and the latest configtool &
> ecosconfig from ecoscentric.com.  I copied the relevant hardware
> info from the ecos.db that I have to the one I checked out of CVS.
> I'm able to succesfully perform each of the commands above.
> 
> But, when I try to compile and link my own code I still get these
> undefined references when I try to link with the eCos libs I've
> built:
>  >>> undefined reference to 'init_all_network_interfaces'
>  >>> undefined reference to 'eth0_up'
>  >>> undefined reference to 'eth0_bootp_data'
>  >>> undefined reference to 'inet_ntoa'

It sounds like you don't have the CYGPKG_NET package in your
configuration. However that would be strange, the net template always
includes it.

Do an 

ecosconfig export foo.ecm

and post foo.ecm. 

Also check that net/common/current/src/inet_ntoa.c is getting
compiled and it is in the library install/lib/libtarget.a

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] networking support for my eCos application

[C B]

> 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

Thanks for your help (Andrew & Gary).  I think I'm getting closer.

I got the latest eCos from CVS and the latest configtool & ecosconfig from ecoscentric.com.  I copied the relevant hardware info from the ecos.db that I have to the one I checked out of CVS.  I'm able to succesfully perform each of the commands above.

But, when I try to compile and link my own code I still get these undefined references when I try to link with the eCos libs I've built:

 >>> undefined reference to 'init_all_network_interfaces'
 >>> undefined reference to 'eth0_up'
 >>> undefined reference to 'eth0_bootp_data'
 >>> undefined reference to 'inet_ntoa'

The command that gives those errors:
     arm-elf-ld -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\install\lib" -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\net\common\current" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\arm-elf\lib" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\lib\gcc-lib\arm-elf\3.2.1" -Ttarget.ld  -o"Simple.exe"  ./simple.o

The ping_test calls init_all_network_interfaces() so I'm not sure why it's not found.

Chris



_________________________________________________________________
Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare!
http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] networking support for my eCos application

[Andrew Lunn]

On Mon, Nov 05, 2007 at 10:53:52PM -0500, C B wrote:
> 
> > Date: Mon, 5 Nov 2007 19:42:57 +0100> From: andrew@lunn.ch> To: csb_80@hotmail.com> CC: ecos-discuss@ecos.sourceware.org> Subject: Re: [ECOS] networking support for my eCos application> >
> > > I think I'm missing something here. I checked out the latest from> > CVS without any issues but when I tried 'ecosconfig new eb9261 net'> > I got a bunch of warnings about version subdirectory 'XXX' does not> > have a CDL script and no valid version subdirectories and finally> > and error 'Unknown target eb9261' (out is included below).> > That is probably to do with incompatibilities with the cygwin you have> and the config tool. Grab the latest snapshot from the eCosCentric.com> DevZone.
>  
> Thanks for your response Andrew.  Once I get past these initial configuration issues I'm looking forward to working with eCos.
>  
> Even running this on a linux VM I get the unknown target error.  Am I missing a step in setting up a new target?

eb9261 is not a target in anonymous cvs. You said you inherited this
code from somebody else. My guess is she has added a new target to
ecos.db and some new packages into the tree.

The easiest way forward is to copy these packages into your anonymous
CVS checkout and add the target entry to the ecos.db.

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] networking support for my eCos application

[Andrew Lunn]

On Mon, Nov 05, 2007 at 11:10:59AM -0500, C B wrote:
> 
> 
> Gary,
> 
> I think I'm missing something here.  I checked out the latest from
> CVS without any issues but when I tried 'ecosconfig new eb9261 net'
> I got a bunch of warnings about version subdirectory 'XXX' does not
> have a CDL script and no valid version subdirectories and finally
> and error 'Unknown target eb9261' (out is included below).

That is probably to do with incompatibilities with the cygwin you have
and the config tool. Grab the latest snapshot from the eCosCentric.com
DevZone.
  
> I tried configuring things with configtool and that was even more
> confusing.  I tried building a template based on an ARM eval board
> (PID) but it wouldn't let me add any packages to the template
> (e.g. AT91 ethernet driver) nor was there any obvious way to create
> a new template.  The error I got when trying to add a package was
> 'add and remove hardware packages by selecting a new hardware
> template'.

You are not allowed to add hardware packages to a target. The AT91 eth
driver would not work with the PID, since it is for the on chip
ethernet you find in the AT91SAM7 devices. This is one reason adding
hardware packages are not allowed!
  
> I also notice that trying to create a new platform with configtool
> provides a dialog box with several fields but regardless of what I
> fill in the ok button is never enabled.

I don't use the config tool, but i don't see how that can work. You
need to edit the ecos.db and add a new target. Use the others as an
example.

> I was just hoping to be able to create an eCos configuration for an
> ARM 9 based evaluation board but I seem to be missing something
> fundamental in how these things are setup.  Is there any
> documentation that takes a new user through the process?

Look at the section:

target integrator_arm9

for an ARM9 example.

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] networking support for my eCos application

[C B]

Gary,

I think I'm missing something here.  I checked out the latest from CVS without any issues but when I tried 'ecosconfig new eb9261 net' I got a bunch of warnings about version subdirectory 'XXX' does not have a CDL script and no valid version subdirectories and finally and error 'Unknown target eb9261'  (out is included below).
 
I tried configuring things with configtool and that was even more confusing.  I tried building a template based on an ARM eval board (PID) but it wouldn't let me add any packages to the template (e.g. AT91 ethernet driver) nor was there any obvious way to create a new template.  The error I got when trying to add a package was 'add and remove hardware packages by selecting a new hardware template'.
 
I also notice that trying to create a new platform with configtool provides a dialog box with several fields but regardless of what I fill in the ok button is never enabled.
 
I was just hoping to be able to create an eCos configuration for an ARM 9 based evaluation board but I seem to be missing something fundamental in how these things are setup.  Is there any documentation that takes a new user through the process?
 
Thanks,
Chris
 
----------- part of the output from 'ecosconfig new eb9261 net' ---------------------
 
ecos.db, package CYGPKG_HAL: warning
    Version subdirectory `common' does not have a CDL script `hal.cdl'.
ecos.db, package CYGPKG_HAL: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_INFRA: warning
    Version subdirectory `infra' does not have a CDL script `infra.cdl'.
ecos.db, package CYGPKG_INFRA: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_IO: warning
    Version subdirectory `common' does not have a CDL script `io.cdl'.
ecos.db, package CYGPKG_IO: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_IO_SERIAL: warning
    Version subdirectory `serial' does not have a CDL script `io_serial.cdl'.
ecos.db, package CYGPKG_IO_SERIAL: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_IO_CAN: warning
    Version subdirectory `can' does not have a CDL script `io_can.cdl'.
...
...
(a bunch more in here I've removed for brevity)
...
...
ecos.db, package CYGPKG_FS_FAT: warning
    Version subdirectory `fat' does not have a CDL script `fatfs.cdl'.
ecos.db, package CYGPKG_FS_FAT: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_NET_LWIP: warning
    Version subdirectory `lwip_tcpip' does not have a CDL script `cdl/lwip_net.cdl'.
ecos.db, package CYGPKG_NET_LWIP: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_ATHTTPD: warning
    Version subdirectory `athttpd' does not have a CDL script `httpd.cdl'.
ecos.db, package CYGPKG_ATHTTPD: warning
    This package does not have any valid version subdirectories.
Unknown target eb9261

 
 
----------------------- end output ------------------------------------------



> Date: Fri, 2 Nov 2007 13:07:44 -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:
>> 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
>

_________________________________________________________________
Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare!
http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] networking support for my eCos application

[Gary Thomas]

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

RE: [ECOS] networking support for my eCos application

[C B]

[-- Attachment #1: Type: text/plain, Size: 2648 bytes --]


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...)

My exported config is attached.

Thanks,
Chris



> 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
>

_________________________________________________________________
Windows Live Hotmail and Microsoft Office Outlook – together at last.  Get it now.
http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033

[-- Attachment #2: eCos_config.ecm --]
[-- Type: text/plain, Size: 9226 bytes --]

cdl_savefile_version 1;
cdl_savefile_command cdl_savefile_version {};
cdl_savefile_command cdl_savefile_command {};
cdl_savefile_command cdl_configuration { description hardware template package };
cdl_savefile_command cdl_package { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_component { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_option { value_source user_value wizard_value inferred_value };
cdl_savefile_command cdl_interface { value_source user_value wizard_value inferred_value };

cdl_configuration eCos {
    description "" ;
    hardware    eb9261 ;
    template    eb9261-net ;
    package -hardware CYGPKG_HAL_ARM current ;
    package -hardware CYGPKG_HAL_ARM_AT91 current ;
    package -hardware CYGPKG_HAL_ARM_AT91SAM9261 current ;
    package -hardware CYGPKG_IO_SERIAL_ARM_AT91 current ;
    package -hardware CYGPKG_IO_SPI current ;
    package -hardware CYGPKG_DEVS_SPI_ARM_AT91 current ;
    package -hardware CYGPKG_DEVS_SPI_ARM_EB9261 current ;
    package -hardware CYGPKG_DEVS_AT45_DATAFLASH_SPI current ;
    package -hardware CYGPKG_DEVS_ETH_EB9261 current ;
    package -hardware CYGPKG_DEVS_ETH_DAVICOM_DM9000A current ;
    package -template CYGPKG_HAL current ;
    package -template CYGPKG_IO current ;
    package -template CYGPKG_IO_SERIAL current ;
    package -template CYGPKG_INFRA current ;
    package -template CYGPKG_ISOINFRA current ;
    package -template CYGPKG_KERNEL current ;
    package -template CYGPKG_MEMALLOC current ;
    package -template CYGPKG_LIBC current ;
    package -template CYGPKG_LIBC_TIME current ;
    package -template CYGPKG_LIBC_STDLIB current ;
    package -template CYGPKG_LIBC_STRING current ;
    package -template CYGPKG_LIBC_I18N current ;
    package -template CYGPKG_LIBC_SETJMP current ;
    package -template CYGPKG_LIBC_STARTUP current ;
    package -template CYGPKG_LIBC_STDIO current ;
    package -template CYGPKG_LIBM current ;
    package -template CYGPKG_POSIX current ;
    package -template CYGPKG_IO_WATCHDOG current ;
    package -template CYGPKG_IO_WALLCLOCK current ;
    package -template CYGPKG_ERROR current ;
    package -template CYGPKG_IO_FILEIO current ;
    package -template CYGPKG_NET current ;
    package -template CYGPKG_NET_OPENBSD_STACK current ;
    package -template CYGPKG_IO_ETH_DRIVERS current ;
    package -template CYGPKG_NET_FTPCLIENT current ;
    package -template CYGPKG_CPULOAD current ;
};

cdl_option CYGSEM_HAL_INSTALL_MMU_TABLES {
    user_value 0
};

cdl_component CYGDBG_HAL_DIAG_TO_DEBUG_CHAN {
    user_value 0
    inferred_value 0
};

cdl_component CYGSEM_HAL_ENABLE_DCACHE_ON_STARTUP {
    inferred_value 0
};

cdl_option CYGSEM_HAL_ENABLE_ICACHE_ON_STARTUP {
    inferred_value 0
};

cdl_option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT {
    inferred_value 0
};

cdl_option CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT {
    inferred_value 0
};

cdl_option CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE {
    user_value 1
};

cdl_option CYGSEM_HAL_USE_ROM_MONITOR {
    user_value 1 GDB_stubs
    inferred_value 0 ""
};

cdl_option CYGHWR_HAL_ARM_AT91_FIQ {
    user_value 1
    inferred_value 1
};

cdl_option CYGBLD_HAL_ARM_AT91_TIMER_TC {
    inferred_value 0
};

cdl_option CYGBLD_HAL_ARM_AT91_TIMER_PIT {
    inferred_value 1
};

cdl_option CYGBLD_HAL_ARM_AT91_SERIAL_DBG {
    inferred_value 1
};

cdl_option CYGBLD_HAL_ARM_AT91_SERIAL_UART {
    inferred_value 0
};

cdl_component CYG_HAL_STARTUP {
    user_value RAM
    inferred_value ROMRAM
};

cdl_component CYGPKG_IO_SERIAL_DEVICES {
    inferred_value 1
};

cdl_option CYGBLD_ISO_CTYPE_HEADER {
    inferred_value 1 <cyg/libc/i18n/ctype.inl>
};

cdl_option CYGBLD_ISO_ERRNO_CODES_HEADER {
    inferred_value 1 <cyg/error/codes.h>
};

cdl_option CYGBLD_ISO_ERRNO_HEADER {
    inferred_value 1 <cyg/error/errno.h>
};

cdl_option CYGBLD_ISO_STDIO_FILETYPES_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_STREAMS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEOPS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEACCESS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FORMATTED_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_CHAR_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_DIRECT_IO_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_FILEPOS_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDIO_ERROR_HEADER {
    inferred_value 1 <cyg/libc/stdio/stdio.h>
};

cdl_option CYGBLD_ISO_STDLIB_STRCONV_HEADER {
    inferred_value 1 <cyg/libc/stdlib/atox.inl>
};

cdl_option CYGBLD_ISO_STDLIB_ABS_HEADER {
    inferred_value 1 <cyg/libc/stdlib/abs.inl>
};

cdl_option CYGBLD_ISO_STDLIB_DIV_HEADER {
    inferred_value 1 <cyg/libc/stdlib/div.inl>
};

cdl_option CYGBLD_ISO_STRERROR_HEADER {
    inferred_value 1 <cyg/error/strerror.h>
};

cdl_option CYGBLD_ISO_STRTOK_R_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_LOCALE_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_BSD_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/bsdstring.h>
};

cdl_option CYGBLD_ISO_STRING_MEMFUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRING_STRFUNCS_HEADER {
    inferred_value 1 <cyg/libc/string/string.h>
};

cdl_option CYGBLD_ISO_STRUCTTIMEVAL_HEADER {
    inferred_value 1 <cyg/posix/sys/time.h>
};

cdl_option CYGBLD_ISO_POSIX_TIMER_TYPES_HEADER {
    inferred_value 1 <cyg/posix/time.h>
};

cdl_option CYGBLD_ISO_POSIX_CLOCK_TYPES_HEADER {
    inferred_value 1 <cyg/posix/time.h>
};

cdl_option CYGBLD_ISO_C_TIME_TYPES_HEADER {
    inferred_value 1 <cyg/libc/time/time.h>
};

cdl_option CYGBLD_ISO_POSIX_TIMERS_HEADER {
    inferred_value 1 <cyg/posix/time.h>
};

cdl_option CYGBLD_ISO_POSIX_CLOCKS_HEADER {
    inferred_value 1 <cyg/posix/time.h>
};

cdl_option CYGBLD_ISO_C_CLOCK_FUNCS_HEADER {
    inferred_value 1 <cyg/libc/time/time.h>
};

cdl_option CYGBLD_ISO_SIGNAL_NUMBERS_HEADER {
    inferred_value 1 <cyg/posix/signal.h>
};

cdl_option CYGBLD_ISO_SIGNAL_IMPL_HEADER {
    inferred_value 1 <cyg/posix/signal.h>
};

cdl_option CYGBLD_ISO_SETJMP_HEADER {
    inferred_value 1 <cyg/libc/setjmp/setjmp.h>
};

cdl_option CYGBLD_ISO_SIGSETJMP_HEADER {
    inferred_value 1 <cyg/posix/sigsetjmp.h>
};

cdl_option CYGBLD_ISO_DIRENT_HEADER {
    inferred_value 1 <cyg/fileio/dirent.h>
};

cdl_option CYGBLD_ISO_PTHREADTYPES_HEADER {
    inferred_value 1 <cyg/posix/types.h>
};

cdl_option CYGBLD_ISO_PMUTEXTYPES_HEADER {
    inferred_value 1 <cyg/posix/muttypes.h>
};

cdl_option CYGBLD_ISO_BSDTYPES_HEADER {
    inferred_value 1 <sys/bsdtypes.h>
};

cdl_option CYGBLD_ISO_UTSNAME_HEADER {
    inferred_value 1 <cyg/posix/utsname.h>
};

cdl_option CYGBLD_ISO_SEMAPHORES_HEADER {
    inferred_value 1 <cyg/posix/semaphore.h>
};

cdl_option CYGBLD_ISO_PTHREAD_IMPL_HEADER {
    inferred_value 1 <cyg/posix/pthread.h>
};

cdl_option CYGBLD_ISO_PTHREAD_MUTEX_HEADER {
    inferred_value 1 <cyg/posix/mutex.h>
};

cdl_option CYGBLD_ISO_POSIX_LIMITS_HEADER {
    inferred_value 1 <cyg/posix/limits.h>
};

cdl_option CYGBLD_ISO_OPEN_MAX_HEADER {
    inferred_value 1 <cyg/fileio/limits.h>
};

cdl_option CYGBLD_ISO_NAME_MAX_HEADER {
    inferred_value 1 <cyg/fileio/limits.h>
};

cdl_option CYGBLD_ISO_DNS_HEADER {
    inferred_value 1 <cyg/ns/dns/dns.h>
};

cdl_option CYGBLD_ISO_NETDB_PROTO_HEADER {
    inferred_value 1 <net/netdb.h>
};

cdl_option CYGBLD_ISO_NETDB_SERV_HEADER {
    inferred_value 1 <net/netdb.h>
};

cdl_option CYGIMP_KERNEL_SCHED_SORTED_QUEUES {
    inferred_value 1
};

cdl_option CYGSEM_KERNEL_SCHED_TIMESLICE_ENABLE {
    inferred_value 1
};

cdl_component CYGSEM_KERNEL_SCHED_ASR_SUPPORT {
    inferred_value 1
};

cdl_option CYGSEM_KERNEL_SCHED_ASR_GLOBAL {
    inferred_value 1
};

cdl_component CYGPKG_KERNEL_THREADS_DESTRUCTORS {
    inferred_value 1
};

cdl_option CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT {
    inferred_value 0
};

cdl_component CYGPKG_NET_TFTP {
    user_value 0
};

cdl_component CYGPKG_NET_DHCP {
    user_value 0
};

cdl_component CYGHWR_NET_DRIVER_ETH0_MANUAL {
    user_value 0
};

cdl_component CYGHWR_NET_DRIVER_ETH0_BOOTP {
    user_value 0
};

cdl_component CYGHWR_NET_DRIVER_ETH0_ADDRS {
    user_value 1
};

cdl_option CYGHWR_NET_DRIVER_ETH0_ADDRS_IP {
    user_value 10.1.4.3
};

cdl_option CYGHWR_NET_DRIVER_ETH0_ADDRS_BROADCAST {
    user_value 10.1.4.255
};

cdl_option CYGHWR_NET_DRIVER_ETH0_ADDRS_GATEWAY {
    user_value 10.1.4.1
};

cdl_option CYGHWR_NET_DRIVER_ETH0_ADDRS_SERVER {
    user_value 10.1.4.1
};



[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss