From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24288 invoked by alias); 20 Jun 2005 07:06:34 -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 24227 invoked by uid 22791); 20 Jun 2005 07:06:27 -0000 Received: from dns.cra.se (HELO cra.se) (212.181.13.155) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 20 Jun 2005 07:06:26 +0000 From: Jokke Ramberg Reply-To: joakim.ramberg@ktc.se To: ecos-discuss@ecos.sourceware.org In-Reply-To: <20050617113004.GB4982@lunn.ch> References: <42AD6CA8.40504@rms.ro> <20050613121642.GE30632@lunn.ch> <42AD9362.3070700@rms.ro> <42B1BB21.1080108@rms.ro> <1118998149.3319.15.camel@localhost.localdomain> <20050617113004.GB4982@lunn.ch> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 20 Jun 2005 07:06:00 -0000 Message-Id: <1119251120.3314.5.camel@localhost.localdomain> Mime-Version: 1.0 Subject: Re: [ECOS] porting ecos to at91sam7 X-SW-Source: 2005-06/txt/msg00163.txt.bz2 fre 2005-06-17 klockan 13:30 +0200 skrev Andrew Lunn: > On Fri, Jun 17, 2005 at 10:49:08AM +0200, Jokke Ramberg wrote: > > I am trying to port ecos to Atmels AT91sam7s64. I start out from > > AT91EB55 (from CVS 050504). > > > > Following the instructions in "embedded software development with ecos" > > and some debugging, have got to a stage where the I can build an example > > application from the two-threads example in ecos. I can load it and > > start. > > > > The two threads are started, I get the start messages from them, with > > the correct baudrate, on the serial port, the threads calls > > "cyg_thread_delay(20);", but this function never returns! > > > > I get the timer interrupts, the function "void Cyg_Counter::tick > > ( cyg_uint32 ticks )" is called regularly (I did not measure how often). > > > > What is more required for delay to return? Any defines or cdl stuff?? > > I suggest you run the standard tests and see what passes > fails. clocktruth can be used to make sure the clock is ticking at the > right rate etc. > > Andrew > I can try, but I have very little memory on my device, so the tests can be hard to build. The clock speed is one thing, but even it is not correct, the delay should return ( I set it to only 20, and I can see the tick rate is at least > 1 Hz). Jokke -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss