This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configtool issue


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]