From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23802 invoked by alias); 23 Feb 2007 02:49:59 -0000 Received: (qmail 23794 invoked by uid 22791); 23 Feb 2007 02:49:58 -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; Fri, 23 Feb 2007 02:49:50 +0000 Received: (qmail 36987 invoked from network); 23 Feb 2007 02:49:49 -0000 Received: from unknown (HELO Vaio370.mcmanis.com) (65.166.100.27) by www.mcmanis.com with SMTP; 23 Feb 2007 02:49:49 -0000 X-Orig-IP: 65.166.100.27 Message-Id: <7.0.1.0.0.20070222183752.01b2b130@mcmanis.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Fri, 23 Feb 2007 02:49:00 -0000 To: ECOS Discussion Group From: Chuck McManis In-Reply-To: <45DD86C9.5050503@mlbassoc.com> References: <6.1.2.0.2.20070221191033.044064b0@192.168.110.40> <45DD86C9.5050503@mlbassoc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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] N00blet question on networking X-SW-Source: 2007-02/txt/msg00220.txt.bz2 At 04:04 AM 2/22/2007, Gary Thomas wrote: The most likely cause is not getting interrupts from your >ethernet card. RedBoot doesn't use them but eCos requires >that they work. Ok so many diag_printfs later ... One of the things I discovered is that my CR0 register which has control bits for enabling transmission and reception. Rx Enable is bit 3 and Tx enable is bit 4, NIC "Start" is bit 1 so a "proper" CR0 should be 0x1a, but at somepoint it gets 0x12 in it and that disables the receiver. Since my transmits were working fine slam 0x1a in to periodically and I at least got through the handshake to the DHCP server (it assigned my address Etc.) that tells me that interrupts are hooked correctly if the CR0 register is correct. Looking at it further, I was wondering if the Half duplex / full duplex state of the PHY might have anything to do with it (its hooked to a switch and so should be full duplex). Has anyone had an experience where if the MAC thought the Phy was half duplex it would disable the receiver when it was transmitting? In such a system would I be adding code to my TxDone function to turn the receiver enable bit back on? Clearly on a Hub it would be half duplex and some other lame networking equipment so I want to do the right thing. --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