From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23366 invoked by alias); 27 Jun 2005 07:19:28 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 23322 invoked by uid 22791); 27 Jun 2005 07:19:22 -0000 Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 27 Jun 2005 07:19:22 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1Dmntm-0002uF-00; Mon, 27 Jun 2005 09:19:18 +0200 Date: Mon, 27 Jun 2005 07:19:00 -0000 To: Chris Hiszpanski Cc: ecos-discuss@ecos.sourceware.org Message-ID: <20050627071918.GA11071@lunn.ch> Mail-Followup-To: Chris Hiszpanski , ecos-discuss@ecos.sourceware.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Andrew Lunn Subject: Re: [ECOS] configtool issue X-SW-Source: 2005-06/txt/msg00262.txt.bz2 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' > ... > > ... > 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