public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo Tyson <hmt@redhat.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE: RedBoot
Date: Thu, 26 Apr 2001 04:15:00 -0000	[thread overview]
Message-ID: <wwtitjrap63.fsf@masala.cambridge.redhat.com> (raw)
In-Reply-To: <NBBBJIKCMKBJFEAHMGMAGENNDHAA.amassa@san.rr.com>


"Anthony Massa" <amassa@san.rr.com> writes:
> >Uh, you have called "init_all_network_interfaces()" in you app?  The
> >network doesn't initialize automatically - precisely to allow for the
> >flexibility we've been discussing.  I mean, the dhcp thread will manage
> >your leases *after the interfaces are brung up* but it won't initiate the
> >bringup.
> 
> I have the call to init_all_network_interfaces in my application properly -
> as stated in the networking documentation.  I have the call in a thread that
> gets created from my cyg_user_start routine.  Is there any additional
> consideration I need to take into account for the call?

No, that all sounds like you're doing exactly the right thing.

For comparison, you could enable CYGPKG_NET_BUILD_TESTS to let the system
build the network tests, then try ping_test for example.  That brings up
all interfaces using whatever means is configured, then pings the "server"
- in your configuration this should mean uses DHCP then pings the DHCP
server or the boot server that DHCP suggested.

If that fails, try configuring static IP addresses (distinct from the one
you have to RedBoot) for the build and try the same test; this tells us
whether it's the whole network being bad or just the DHCP processing.

> I have configured RedBoot to use a static IP address.
> 
> I am still running into the same problem as I mentioned before where the
> network usage gets printed out on the GDB console window, then the hour
> glass sits there for a while, and then the debugger shows program stopped at
> the bottom.

Has the program really stopped?  Does the debugger tell you where?

I can only suggest you breakpoint and step through
init_all_network_interfaces() and see where it's hanging up, sorry.  And of
course compare with the behaviour of the network testcases.

	- Huge

  reply	other threads:[~2001-04-26  4:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25 21:59 Anthony Massa
2001-04-26  4:15 ` Hugo Tyson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-30 10:04 [ECOS] RedBoot Anthony Massa
2001-04-27 15:06 Anthony Massa
2001-04-27 15:25 ` Jonathan Larmour
2001-04-26 21:44 Anthony Massa
2001-04-27 11:32 ` Jonathan Larmour
2001-04-23 12:35 Anthony Massa
2001-04-23 12:47 ` Jonathan Larmour
2001-04-23 12:09 [ECOS] RedBoot Jonathan Larmour
2001-04-24  8:02 ` [ECOS] Anthony Massa
2001-04-24  8:11   ` [ECOS] Re: RedBoot Jonathan Larmour
2001-04-24  8:13     ` [ECOS] RedBoot Anthony Massa
2001-04-24  8:30       ` Hugo 'NOx' Tyson

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=wwtitjrap63.fsf@masala.cambridge.redhat.com \
    --to=hmt@redhat.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).