From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Venkatesh <venkatc@in.ceeyes.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Facing problem with i82559 driver...
Date: Tue, 06 Aug 2002 04:52:00 -0000 [thread overview]
Message-ID: <20020806115159.GP3999@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <200208061007.g76A7se15693@in.ceeyes.com>
On Tue, Aug 06, 2002 at 03:07:54AM -0700, Venkatesh wrote:
> Dear All,
>
> My configuration is as follows:
>
> eCos: Latest Cvs source
> Configtool : ecos 2.03
> Operating system: Windows2000
> Platform : i386 PC
> Image download through GDB.
>
> I am trying to execute the "ping_test" example given by eCOS sources.
> The control is not coming out of the init_all_network_interfaces() and
> getting struck up after eth_set_mac_address() in if_i82559.c. The
> target is reset upon execuing the line,
> OUTL( (VIRT_TO_BUS(p_selftest)) | I82559_SELFTEST, ioaddr + SCBPort);
Im confused about what you say here.
It gets stack after eth_set_mac_address().
The target is reset upon executing the self test on the ethernet target.
These are two different things and also different from the output
trace.
Which of the three is correct?
> I request you to please help me to solve the above problem as I am
> struggling with it for the past two weeks.
If you want some help, you need to give us consistent and useful
information we can actually work with.
Where exactly does it get stuck? What happens when its stuck? Does the
target crash out with a memory error? Does gdb still respond?
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-08-06 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 4:37 Venkatesh
2002-08-06 4:52 ` Andrew Lunn [this message]
2002-08-06 5:16 ` Gary Thomas
2002-08-06 5:21 Venkatesh
2002-08-06 5:50 ` Andrew Lunn
2002-08-06 5:39 Venkatesh
2002-08-07 4:19 Venkatesh
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=20020806115159.GP3999@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=venkatc@in.ceeyes.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).