This is the mail archive of the ecos-discuss@sourceware.org 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: Cortex-M1/3 SysTick/RTC

From: Andrew Lunn <andrew at lunn dot ch>
To: "simon dot kallweit at intefo dot ch" <simon dot kallweit at intefo dot ch>
Cc: ecos-discuss at ecos dot sourceware dot org
Date: Thu, 11 Sep 2008 17:51:22 +0200
Subject: Re: [ECOS] Cortex-M1/3 SysTick/RTC
References: <48C936B3.2020505@intefo.ch> <20080911153542.GD25830@lunn.ch> <48C93CB3.8060703@intefo.ch>

> Yes, I will use the SysTick for the real time clock source, moving this  
> to the architecture. So there will be no need to define this in new  
> variants and platforms. We probably should provide macros for overriding  
> though?!?

That is easy to do. The porting guide says the official interface is:

HAL_CLOCK_INITIALIZE( period )
HAL_CLOCK_RESET( vector, period )
HAL_CLOCK_READ( pvalue )

So you can include var_io.h or plf_io.h first and then do:

ifndef HAL_CLOCK_INITIALIZE( period )
#define HAL_CLOCK_INITIALIZE cyg_cortex_clock_init( (period))
#endif

etc...

        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

Follow-Ups:
- Re: Cortex-M1/3 SysTick/RTC
  - From: simon dot kallweit at intefo dot ch

References:
- Cortex-M1/3 SysTick/RTC
  - From: simon dot kallweit at intefo dot ch
- Re: Cortex-M1/3 SysTick/RTC
  - From: Andrew Lunn
- Re: Cortex-M1/3 SysTick/RTC
  - From: simon dot kallweit at intefo dot ch

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