Experimental Physics and Industrial Control System
|
You would have to use the linker flags to define _CPUClockSpeed as
80000000 when linking your application, but other than that I think
that everything would be o.k.
Make sure that any devices you have hooked to the external bus still
meet the TA* setup time -- the 64 MHz version of the MCF5282 requires
Tsetup to be at least 10ns -- so external devices have only 5.625 ns
from CLK till they have to have TA* asserted. This was a real pain to
deal with in my ColdFire/FPGA applications.
On May 5, 2008, at 6:53 PM, K.M Ha wrote:
Hello,
Recently the Arcturus company relesed new uC5282 model.
The difference is coldfire CPU clock 80 MHz(previous model clock is
64 MHz).
Model : uC5282-16E16C80-XR
Somebody use this model for embedded m68k-RTEMS IOC applications ?
If i choson this model, all of BSP is compatible in recent m68k-
RTEMS BSP ?
Thanks.
Kiman Ha,
Pohang Light Source
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- References:
- RTEMS-GeSys_2.1.beta and cexp-1.5 for uC5282 Coldfire Module K.M Ha
- 80 MHz clock for uC5282 Coldfire Module K.M Ha
- Navigate by Date:
- Prev:
80 MHz clock for uC5282 Coldfire Module K.M Ha
- Next:
asyn problem John Sinclair
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
<2008>
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
80 MHz clock for uC5282 Coldfire Module K.M Ha
- Next:
FW: Beginners C++ questions Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
<2008>
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|