This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: network support
- To: Fano Ramparany <Fano dot Ramparany at rd dot francetelecom dot fr>
- Subject: Re: [ECOS] network support
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Mon, 22 Jan 2001 08:12:52 -0700 (MST)
- Cc: eCos Disuss <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat, Inc.
On 22-Jan-2001 Fano Ramparany wrote:
> Gary Thomas wrote:
>
>> Here's the very simplest way to test this (using ecosconfig).
>>
>> [gthomas@hermes test2]$ ecosconfig new edb7212 net
>> [gthomas@hermes test2]$ ecosconfig tree
>> [gthomas@hermes test2]$ make;make -C net/tcpip/current/ tests TESTS=tests/ping_test
>>
>> Similar results can be obtained by just using the "net" template and
>> then enabling/building tests.
>>
>> Does this sequence [scenario] not work for you?
>
> I guess this is the linux scenario. We are using the Windows Development tools.
> Thus here is our scenario:
> We have registered the Networking package using the Package Administration tool, then
> using the eCos Configuration tool we have added the Networking package by ticking on
> INET support option.
> Initialization options for eth0 and eth1 are greyed out, then we can't modify them.
> There
> status are: Use BOOTP/DHCP and Show BOOTP/DHCP for both eth0 and eth1.
> Other options have been set with their default value.
> Then we've build the library and the tests.
> When running the ping test here is the gdb debugger trace, which makes no mention of the
> ping
> session I think:
>
The way I did this using the Windows Config Tool was
Build->Templates
Hardware = Cirrus Logic development board
Packages = net
This selection is equivalent to the 'ecosconfig' steps above. All of the appropriate
options are automatically enabled and it should "just work".