From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2834 invoked by alias); 19 Jun 2008 13:05:23 -0000 Received: (qmail 2817 invoked by uid 22791); 19 Jun 2008 13:05:22 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 19 Jun 2008 13:05:00 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m5JD4wjS019525; Thu, 19 Jun 2008 09:04:58 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5JD4wCf016715; Thu, 19 Jun 2008 09:04:58 -0400 Received: from [10.11.14.36] (vpn-14-36.rdu.redhat.com [10.11.14.36]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5JD4vir019680; Thu, 19 Jun 2008 09:04:58 -0400 From: Mark Salter To: Ravi R Cc: ecos-discuss@ecos.sourceware.org In-Reply-To: <513ab1aa0806181926v6894d715ya04e1030d0b36025@mail.gmail.com> References: <513ab1aa0806181926v6894d715ya04e1030d0b36025@mail.gmail.com> Content-Type: text/plain Date: Thu, 19 Jun 2008 14:48:00 -0000 Message-Id: <1213880697.26797.8.camel@deneb.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit 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] NPE ethernet not working with Redboot v2.04 X-SW-Source: 2008-06/txt/msg00120.txt.bz2 On Wed, 2008-06-18 at 19:26 -0700, Ravi R wrote: > We are developing a product based on a board very similar to the Intel IXDP425. > We have taken the Redboot v2.04 source from the Intel IXP400 software > web site and built the source per instructions (with a few small > modifications to GPIO etc) and have installed Redboot on the board. > Redboot seems to be working fine including Serial, PCI configuration > and Flash services. > However, the Ethernet connection is not working. > A default ESA is set correctly, the NPE successfully detects and sets > up the PHY ("success using NPE-B with PHY 0"), the PHY link is > established (Link LED on PHY), the NPE subsystem seems to get > initialized correctly (no errors reported) and the NPE subsystem seems > to accept packets for transmission. However the NPE/Ethernet subsystem > does not appear to send out more than 1 packet (detected on the MII > TX_EN line to the Phy). All subsequent packets are blocked waiting on > the second packet to get transmitted (npe_can_send() returns 0). The > call sequence is as follows: Its hard to say what could be going wrong. Are you sure the first packet gets sent on the wire? Depending on how you have things configured, the "success using NPE-x with PHY n" message could have different meanings. If you have statically configured NPE-B to use PHY 0, then the message simply means that PHY 0 was found. It does not mean the PHY 0 is actually connected to NPE-B. All NPEs share the same mdc/mdio interface to the PHYs. So first, I would make sure that NPE-B really is connected to PHY 0. --Mark -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss