public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Laurie.Gellatly" <laurie.gellatly@netic.com>
To: Chuck McManis <ecos@mcmanis.com>,
	        ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] and another thing ..
Date: Thu, 22 Feb 2007 04:21:00 -0000	[thread overview]
Message-ID: <bfd112908648326693d9b29ab3200da8@www.netic.com> (raw)

The MAC changes - interesting.
So your NIC supports working with two MACs simultaneously?
You might try by simplifying things and keeping just the one MAC and having
it support two IPs which I know works.
Why do you want both Redboot and your app to be DHCP?
Again, I'd look to nail these to some static addresses to get you started
and then make it fancier later.

...Laurie:{)

--------- Original Message --------
From: Chuck McManis <cmcmanis@mcmanis.com>
To: Laurie.Gellatly <laurie.gellatly@netic.com>, Chuck McManis
<ecos@mcmanis.com>, ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] and another thing ..
Date: 21/02/07 03:05

> At 07:52 PM 2/21/2007, Laurie.Gellatly wrote:
> 
> &gt;Using configtool, if you DON'T config to build Redboot, then libtarget
gets
> &gt;built instead.
> 
> 
> Yes, this I am familiar with. I've got a directory (redboot-epia that 
> builds redboot and a directory epia-ecos that builds libtarget.a. And by 
> setting CFLAGS I can in fact have it build -g. So that is all good.
> 
> Another bit of information is that watching my DHCP logs I see that when 
> the program starts DHCP is getting the request for an IP address and it 
> &quot;offers&quot; 192.168.110.123. (the mac actually changes so its not
confused by 
> this, in my redboot setup I was pre-setting the mac, hmmm I could try that

> here too)
> 
> But what seems to be happening is that it responds with the offer and the 
> target board doesn't see it. This is reminescent of an earlier problem I 
> had with redboot and DHCP/BOOTP but I fixed it there and it seems to be 
> here. Almost like my nic card is not seeing any received packets.
> 
> Hmm, back to the painful printf process it looks like. I can actually 
> attach to the board through the terminal server to the serial port (9600 
> baud max, its an old terminal server) but the server cannot deal with gdb 
> slamming so much data through it, it gets corrupted packets.
> 
> Thanks for the response though! I'll keep plugging away
> 
> --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
> 
> 

________________________________________________
Message sent using UebiMiau 2.7.9



-- 
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-02-22  4:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  4:21 Laurie.Gellatly [this message]
2007-02-22  6:28 ` Chuck McManis
2007-02-22  6:50   ` Laurie Gellatly
  -- strict thread matches above, loose matches on Subject: below --
2007-02-22  3:52 Laurie.Gellatly
2007-02-22  4:05 ` Chuck McManis
2007-02-22  3:46 Chuck McManis

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=bfd112908648326693d9b29ab3200da8@www.netic.com \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=ecos@mcmanis.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).