From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16618 invoked by alias); 17 Oct 2003 09:32:56 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 16599 invoked from network); 17 Oct 2003 09:32:54 -0000 Received: from unknown (HELO anchor-post-31.mail.demon.net) (194.217.242.89) by sources.redhat.com with SMTP; 17 Oct 2003 09:32:54 -0000 Received: from calivar.demon.co.uk ([212.228.213.211] helo=miso.calivar.com) by anchor-post-31.mail.demon.net with esmtp (Exim 3.35 #1) id 1AAQya-000K5M-0V; Fri, 17 Oct 2003 10:32:53 +0100 Received: from miso.calivar.com (miso.calivar.com [127.0.0.2]) by miso.calivar.com (Postfix) with ESMTP id 3FB0528DF46; Fri, 17 Oct 2003 10:04:40 +0100 (BST) To: "Transferencia de Archivos" Cc: ecos-discuss@sources.redhat.com References: <200310160401.h9G41fXk005039@dns.vitacom.net> From: Nick Garnett Date: Fri, 17 Oct 2003 09:32:00 -0000 In-Reply-To: <200310160401.h9G41fXk005039@dns.vitacom.net> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] at91eb40a Timer Counter X-SW-Source: 2003-10/txt/msg00317.txt.bz2 "Transferencia de Archivos" writes: > >eCos currently uses TC0 to implement its main system timer and TC2 to > >implement a microsecond delay timer. You could probably disable the > >latter, but disabling the system timer would only work if you have no > >code that needs timing services of any sort. This is fairly rare, even > > for very simple programs. -- > >Nick Garnett eCos Kernel Architect > >http://www.ecoscentric.com The eCos and RedBoot experts > > Thank you all, who answered my last message, and now I have other > questions In fact I really need to get the maximum free > timer-counters of the board, since I need a pretty fast measurement > rate of signals.(PWM) Anyone knows, wich features are compromised > disabling the microsecond timer? In theory you can transfer the microsecond timer over to using the same timer as the system clock. However, you will have to rewrite the hal_delay_us() function in the HAL. An example of how to write the new routine can be found in the i386 HAL. > So the "clock ticks" I would expect > from ecos in this case would be maximum the MCK/2 that TC0 supports? I'm not sure what you are asking here. It is a bad idea to run the system clock at too high a rate, since you would then swamp the CPU with interrupts. > And a final question, since the Interrupt model that eCos uses as > the documentation says, is based on the ARM model, should I expect > that the interrupt model work would be transparent from ecos > code?(On the AT91EB40a). > eCos has its own interrupt architecture. This invoves decoding all interrupt sources into their own ISR vectors by using the interrupt controller. However, you can also access the underlying hardware interrupt vectors if you really want to. However this is not recommended. -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com The eCos and RedBoot experts -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss