From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1579 invoked by alias); 11 Apr 2007 09:13:04 -0000 Received: (qmail 1563 invoked by uid 22791); 11 Apr 2007 09:13:03 -0000 X-Spam-Check-By: sourceware.org Received: from anchor-post-36.mail.demon.net (HELO anchor-post-36.mail.demon.net) (194.217.242.86) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Apr 2007 10:12:57 +0100 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-36.mail.demon.net with esmtp (Exim 4.42) id 1HbYso-000Gdx-Kf; Wed, 11 Apr 2007 09:12:54 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id D049F1386AA; Wed, 11 Apr 2007 10:12:53 +0100 (BST) To: Michele Paselli Cc: References: <55208.1176207327833.JavaMail.root@ps5> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Wed, 11 Apr 2007 09:13:00 -0000 In-Reply-To: <55208.1176207327833.JavaMail.root@ps5> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] problems with RTC X-SW-Source: 2007-04/txt/msg00062.txt.bz2 Michele Paselli writes: > Hi all, > > I'm developing a radio driver for an AT91 platform and I need to > change the time granularity in order to make some precise latency > measures. In order to have a frequency multiplied by 10 (1 KHz since > the default is 100Hz) I multiplied by 10 the CYGNUM_HAL_RTC_DENOMINATOR > parameter. I also modified the CYGNUM_KERNEL_TIMESLICE_TICKS parameter > in order to have the same timeslice interval as I would have in the > default conditions. The ticks are now indeed 1 every millisecond, but > the radio driver does not seem to work properly anymore. In particular, > the driver seems to miss come interrupts. The only call to a function > related to timers in the driver is a timeout counter but I multiplied > its value by 10 to have the same conditions as before. Can anyone > suggest me a possible cause? I think that the conditions for the driver > in terms of timing are the same as before, but maybe I'm missing > something. I don't have any suggestions for fixing your driver, in theory everything you have done is correct. I have run many eCos configurations with a 1KHz clock with no problems. Something you should check is that the clock ticks are arriving at the expected rate. Try running the clocktruth kernel test against a stopwatch to check this. -- Nick Garnett eCos Kernel Architect eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss