public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Chuck McManis <cmcmanis@mcmanis.com>
To: ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] N00blet question on networking
Date: Fri, 23 Feb 2007 02:49:00 -0000	[thread overview]
Message-ID: <7.0.1.0.0.20070222183752.01b2b130@mcmanis.com> (raw)
In-Reply-To: <45DD86C9.5050503@mlbassoc.com>

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

  parent reply	other threads:[~2007-02-23  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  3:20 Chuck McManis
2007-02-22 12:04 ` Gary Thomas
2007-02-23  2:43   ` Chuck McManis
2007-02-23  2:49   ` Chuck McManis [this message]
2007-02-22  3:47 Laurie.Gellatly

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=7.0.1.0.0.20070222183752.01b2b130@mcmanis.com \
    --to=cmcmanis@mcmanis.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).