From: Chuck McManis <ecos@mcmanis.com>
To: ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: [ECOS] N00blet question on networking
Date: Thu, 22 Feb 2007 03:20:00 -0000 [thread overview]
Message-ID: <6.1.2.0.2.20070221191033.044064b0@192.168.110.40> (raw)
Ok, so I have redboot working. Further I can build a libtarget.a with a
basic set of options, I tried the simple program to get data from the
console and echo it back, and I can boot redboot, 'load -h <my server>
simple' and 'go' to run it. All's cool.
So I used ecosconfig to add in CYGPKG_NET and FREEBSD_STACK and ETH_DRIVERS
(actually there was a point where I had no conflicts but a couple of
ethernet driver files were missing, its a CDL bug but I've not assured
myself that I know enough about what I'm doing to call it a bug outright
yet ;-)
Now I can build the httpd1.c test and when I run it this is what I get:
----------------------------------------------------
Ethernet eth0: MAC address 00:0a:00:c0:ff:ee
IP: 192.168.110.124/255.255.255.0, Gateway: 192.168.110.254
Default server: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [GRUB]
Non-certified release, version UNKNOWN - built 21:38:48, Feb 19 2007
Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited
RAM: 0x00100000-0x040f0000, [0x0018da10-0x01000000] available
RedBoot> load -h 192.168.110.30 httpd1
Using default protocol (TFTP)
Entry point: 0x00208000, address range: 0x00208000-0x00244720
RedBoot> go
[cyg_net_init] Init: mbinit(0x00000000)
[cyg_net_init] Init: cyg_net_init_devs(0x00000000)
Init device 'vt8235_eth0'
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x00243f80)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x002436c0)
New domain route at 0x00000000
[cyg_net_init] Init: call_route_init(0x00000000)
[cyg_net_init] Done
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
----------------------------------------
Ok, but when I do this, there doesn't seem to be any way to talk to my
target board. Eventually it prints :
BOOTP/DHCP failed on eth0
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
Which seems unusual given that DHCP worked fine for Redboot.
So here are some questions:
What should this test print when it works? Should I be able to ping my
target after using init_all_network_interfaces() ? What is different
between Redboot's use of my driver and ECOS's use of the driver?
--Chuck
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-02-22 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 3:20 Chuck McManis [this message]
2007-02-22 12:04 ` Gary Thomas
2007-02-23 2:43 ` Chuck McManis
2007-02-23 2:49 ` Chuck McManis
2007-02-22 3:47 Laurie.Gellatly
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=6.1.2.0.2.20070221191033.044064b0@192.168.110.40 \
--to=ecos@mcmanis.com \
--cc=ecos-discuss@sources.redhat.com \
/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).