From: Andrew Lunn <andrew@lunn.ch>
To: Chris Hiszpanski <chiszp@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] configtool issue
Date: Mon, 27 Jun 2005 07:19:00 -0000 [thread overview]
Message-ID: <20050627071918.GA11071@lunn.ch> (raw)
In-Reply-To: <BAY106-F218B26B4F12F99360F8598D4EE0@phx.gbl>
On Mon, Jun 27, 2005 at 01:32:10AM +0000, Chris Hiszpanski wrote:
> Hello,
>
> I am new to eCos. I have installed the eCos tools on Windows XP under
> Cygwin, following the install instructions presented in the documentation
> (II. Installing eCos) exactly. Moving on the part III. Programming with
> eCos, I run into problems, in particular when running configtool.
>
> When I start configtool I see a flurry of messages. Here is a snippet of
> what I see:
> ...
> ecos.db, package CYGPKG_DEVS_FLASH_POWERPC_TS1000: warning
> This package does not have any valid version subdirectories.
> ecos.db, package CYGPKG_DEVS_ETH_POWERPC_TS1000 warning
> Version subdirectory `ts1000' does not have a CDL script
> `ts1000_eth_drivers.cdl'
> ...
> <repeated hundreds of times for various packages>
> ...
> Is this normal?
Sort of. Its a bug which appears with recent cygwin packages. See
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000095
You can get an updated version of configtool from
http://www.ecoscentric.com/devzone/configtool.shtml
> Following section VI, I tried ecosconfig new arm7tdmi. As expected arm7tdmi
> is not a valid target. Where are the valid targets lists?
ecos.db in the packages target. arm7tdmi is a processor not a
target. eCos targets are real boards, not processors, since a target
is much more than just the processor.
> My current goal is to get eCos and its TCP/IP stack running to a pingable
> state on my own hardware (see
> http://www.its.caltech.edu/~hiszpans/ethphone/ethphone.html for minimal
> documentation). I'm somewhat lost as how to do this. Do I need to create a
> custom ecos.ecc file for my hardware? Some pointers would be helpful and
> appreciated.
You need to compare your hardware with the other ARM targets and
decide which is the closet. You then need to use that as a starting
point for your port. There is information about porting eCos in
http://ecos.sourceware.org/docs-latest/ref/hal-porting-guide.html
And the book "Embedded Software Development with eCos"
Andrew
--
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:[~2005-06-27 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 1:32 Chris Hiszpanski
2005-06-27 7:19 ` Andrew Lunn [this message]
2005-06-27 22:35 ` [ECOS] MIPS issue neuwald
2005-06-28 2:48 ` [ECOS] GDB install error neuwald
2005-06-28 13:08 ` [ECOS] GDB error neuwald
2005-06-28 13:30 ` Andrew Lunn
2005-06-29 15:55 ` Bart Veer
2005-06-28 13:49 ` [ECOS] MIPS neuwald
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=20050627071918.GA11071@lunn.ch \
--to=andrew@lunn.ch \
--cc=chiszp@hotmail.com \
--cc=ecos-discuss@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).