From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18820 invoked by alias); 22 Feb 2007 06:28:37 -0000 Received: (qmail 18810 invoked by uid 22791); 22 Feb 2007 06:28:36 -0000 X-Spam-Check-By: sourceware.org Received: from www.mcmanis.com (HELO www.mcmanis.com) (66.125.189.29) by sourceware.org (qpsmtpd/0.31) with SMTP; Thu, 22 Feb 2007 06:28:32 +0000 Received: (qmail 31537 invoked from network); 22 Feb 2007 06:28:30 -0000 Received: from unknown (HELO manowar.mcmanis.com) (192.168.110.32) by 192.168.110.40 with SMTP; 22 Feb 2007 06:28:30 -0000 X-Orig-IP: 192.168.110.32 Message-Id: <6.1.2.0.2.20070221222531.03c90ec0@192.168.110.40> X-Sender: X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 22 Feb 2007 06:28:00 -0000 To: ECOS Discussion Group From: Chuck McManis Cc: "Laurie.Gellatly" In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] and another thing .. X-SW-Source: 2007-02/txt/msg00209.txt.bz2 At 08:21 PM 2/21/2007, you wrote: >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. Well as I expected hard coding the address didn't really change anything. Basically I'm not seeing any of the response packets. So I went back to my old notes from a year ago where I had a similar issue with Redboot and there were issues with enabling the CRC checking / generation which I've confirmed are not the issue here. Sigh, time to match Ethereal traces with debugging output and try to narrow down where things go wrong. I suppose the good news is that when I use DHCP the DHCP server *is* seeing the transmitted packets so I can contentrate primarily on the receiver. It does complain about not being able to set multicast but I don't think that is a real problem. I'll know after I dig into the traces more thoroughly. Hmm, I suppose I could dig up my old Intel board as well and see if that board had similar issues. Another avenue to try ... --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