From: Dennis S <Incubus84@web.de>
Subject: [ECOS] How to activate ethernet driver
Date: Tue, 07 Apr 2015 21:10:00 -0000 [thread overview]
Message-ID: <552447CE.email@example.com> (raw)
I have a question concerning the programming of the ethernet in eCos.
The current state is, that I can use some existent functions for the
MAC of my Embedded System located in /devs/eth. They provide the
possibility to access the hardware via HAL_WRITE(). The init function
is used in the NETDEV_TAB macro.
Additionally I wrote some drivers for the seperated PHY with the
obligatory "phy_stat" function. When I started debugging I was very
suprised, that either the init function of the mac nor some function
of the PHY driver was used (I set a brakpoint there and nothing
So my question is: do I have to activate some other things to get
the ethernet work? What possibilities are there to check the result?
By the way: the plan is to use a third party TCP-stack later.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2015-04-07 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 21:10 Dennis S [this message]
2015-04-09 12:15 ` Jerzy Dyrda
[not found] ` <trinity-4777fcb7-729d-4f01-bb84-58b445200f13-1428584884951@3capp-webde-bs37>
2015-04-09 13:43 ` Jerzy Dyrda
[not found] ` <trinity-88db4679-45f1-4bed-85a9-70b78399a50a-1428657096995@3capp-webde-bs01>
2015-04-10 11:26 ` Jerzy Dyrda
2015-04-10 14:30 ` [ECOS] " Grant Edwards
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).