From: Ilija Stanislevik <ilijas@siva.com.mk>
To: eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Ethernet over SPI driver for ENC424J600
Date: Wed, 03 Feb 2010 09:37:00 -0000 [thread overview]
Message-ID: <4B6943D5.9010903@siva.com.mk> (raw)
Hi,
I tested the driver at Ethernet level: sending and receiving Ethernet
packets, setting and getting ESA, etc. The tests have been done on
STM3210E evaluation board (ST cortex M3 processor). Now I am trying to
perform tests with lwip stack.
First I did some initial testing with ecos3.0. Using configtool I chose
ecos3.0 repository, ST STM3210E EVAL board template and lwip_eth package
instead of default. I added my driver source and CDL files to my local
ecos3.0 repository. Everything builds fine.
Then I decided to try the lwip from the CVS. Using configtool I chose
current ecos repository (taken from CVS on February 2. 2010), ST
STM3210E EVAL board template and lwip_eth package. I added my driver
source and CDL files to my local repository. Building library does not
yield:
.
.
home/iko/current_ecos/ecos/packages/net/lwip_tcpip/current/src/ecos/simple.c:72:27:
error: netif/ppp/ppp.h: No such file or directory
/home/iko/current_ecos/ecos/packages/net/lwip_tcpip/current/src/ecos/simple.c:73:28:
error: netif/ppp/chat.h: No such file or directory
/home/iko/current_ecos/ecos/packages/net/lwip_tcpip/current/src/ecos/simple.c:190:8:
warning: multi-line comment
make[1]: Leaving directory
`/home/iko/Agenda/Energ/Ramnenje/Dizajn/STM32/EVALB/ecos/test_current_ecos_build/net/lwip_tcpip/current'
make[1]: *** [src/ecos/simple.o.d] Error 1
make: Leaving directory
`/home/iko/Agenda/Energ/Ramnenje/Dizajn/STM32/EVALB/ecos/test_current_ecos_build'
make: *** [build] Error 2
Any suggestions how to get on track?
Ilija Stanislevik
next reply other threads:[~2010-02-03 9:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 9:37 Ilija Stanislevik [this message]
2010-02-03 13:13 ` Simon Kallweit
2010-02-04 9:17 ` John Dallaway
2010-02-05 7:59 ` Ilija Stanislevik
2010-02-05 8:16 ` Ilija Kocho
2010-02-05 10:26 ` Ross Younger
-- strict thread matches above, loose matches on Subject: below --
2010-02-16 8:20 Ilija Stanislevik
2010-02-16 19:03 ` John Dallaway
2010-02-28 13:40 ` Ilija Stanislevik
2010-06-22 9:56 ` Ilija Stanislevik
[not found] <894030.6104.qm@web8316.mail.in.yahoo.com>
2009-10-26 8:21 ` Ilija Stanislevik
2009-10-26 6:51 Ilija Stanislevik
2009-10-26 9:05 ` John Dallaway
2009-10-26 11:18 ` Ilija Stanislevik
2009-10-26 12:04 ` John Dallaway
2009-10-29 17:40 ` Ilija Stanislevik
2009-10-31 10:00 ` John Dallaway
2009-10-26 11:46 ` Alex Schuilenburg
2009-10-26 21:28 ` Sergei Gavrikov
2009-10-26 22:17 ` John Dallaway
2009-10-27 7:57 ` Ilija Kocho
2009-10-27 10:08 ` Sergei Gavrikov
2009-10-06 13:51 NAND technical review Ross Younger
2009-10-07 9:40 ` Jürgen Lambrecht
2009-10-13 2:44 ` Jonathan Larmour
2009-10-13 12:59 ` Rutger Hofman
2009-10-15 4:41 ` Jonathan Larmour
2009-10-19 10:53 ` Ross Younger
2009-10-20 1:40 ` Jonathan Larmour
2009-10-20 10:17 ` Ross Younger
2009-10-21 2:06 ` Jonathan Larmour
2009-10-22 10:05 ` Ross Younger
2009-11-10 5:15 ` Jonathan Larmour
2009-11-10 10:38 ` Ross Younger
2009-11-10 11:28 ` Ethernet over SPI driver for ENC424J600 Ilija Stanislevik
2009-11-10 12:16 ` Chris Holgate
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=4B6943D5.9010903@siva.com.mk \
--to=ilijas@siva.com.mk \
--cc=ecos-devel@ecos.sourceware.org \
/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).