From: Robert Brusa <bob.brusa@gmail.com>
To: "Andrew Lunn" <andrew@lunn.ch>, "Gary Thomas" <gary@mlbassoc.com>
Cc: "MailingList:ecos-discuss ;" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Fwd: AT91SAM7X-EK with TC/IP - unresolved conflicts
Date: Mon, 01 Sep 2008 09:27:00 -0000 [thread overview]
Message-ID: <op.ugspx7q0keg3uf@localhost> (raw)
In-Reply-To: <20080829162608.GV31987@lunn.ch>
On Fri, 29 Aug 2008 18:26:08 +0200, Andrew Lunn <andrew@lunn.ch> wrote:
...some old stuff removed...
> However, this is a pointless exercise. The AT91SAM7X only has 64K
> RAM. Getting the FreeBSD stack to work in that is probably impossible.
>
> Try the lwip_eth template. Then you will need to tune the lwip
> configuration.
>
> Andrew
Not beeing able to use ethernet would be a serious blow to my planing. I
intend to call a few routines on my target using RPC. This would allow me
to implement a nice GUI on a PC and have the embedded software free of
lengthy user I/F-code. Is RPC supported by ecos?
Back to the above exercise: When using ecosconfig, it seems to work, but
when I call ecosconfig check, I get the following:
================ calling ecosconfig --verbose check
ecos.db, package CYGPKG_HAL_FR30_MB91360: warning
This package is not present in the component repository.
There is no directory `/opt/ecos/ecos-2.x/packages/hal/fr30/mb91360'.
ecos.db, package CYGPKG_HAL_FR30_MB91360_PHYTEC91F364G: warning
This package is not present in the component repository.
There is no directory
`/opt/ecos/ecos-2.x/packages/hal/fr30/phytec91f364g'.
ecos.db, target phytec91f364g: warning
This target refers to an unknown package `CYGPKG_HAL_FR30_MB91360'.
ecos.db, target phytec91f364g: warning
This target refers to an unknown package
`CYGPKG_HAL_FR30_MB91360_PHYTEC91F364G'.
ecos.db, target pc_usb_d12: warning
This target refers to a package `CYGPKG_IO_FILEIO' that is not
hardware-specific.
Target: at91sam7xek
Template: net
No conflicts
=============
Then I call make. It goes through with much output and no errors, but I
can find nowhere a result (library). ????
Finally: Prior to switching to lwip_eth, I would like to learn a bit more
about this package (RPC ?). But a search with lwip in the ecos reference
did not produce a hit.
--
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 prev parent reply other threads:[~2008-09-01 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 15:04 [ECOS] " Robert Brusa
2008-08-29 15:20 ` [ECOS] Fwd: " Robert Brusa
2008-08-29 15:54 ` Gary Thomas
2008-08-29 16:06 ` Robert Brusa
2008-08-29 16:26 ` Gary Thomas
2008-08-30 0:10 ` Andrew Lunn
2008-09-01 9:27 ` Robert Brusa [this message]
2008-09-01 9:38 ` Andrew Lunn
2008-09-02 8:10 ` Robert Brusa
2008-09-02 8:42 ` Andrew Lunn
2008-09-03 13:22 ` Robert Brusa
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=op.ugspx7q0keg3uf@localhost \
--to=bob.brusa@gmail.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.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).