Hi Andrew,
> [...]
> The SPECIAL CONSIDERATIONS section of the vxWorks BSP
> man page 'mv167' explains how to set the clock rate in the non-volatile
> RAM, which you do once for each CPU card. Just type the following at the
> vxWorks shell prompt:
> -> m 0xfffc00fe
> fffc00fe: 0000-21ee
> fffc0100: 0000-.
We only use mv162's, the clock rate is not mentioned on the "mv162" man
page, the memory location you suggested seems to be unused on the
mv162.
What I do to detect the CPU speed is check four bytes within the
"Configuration Area" of the NVRAM at address 0xfffc1f28 which read
0x32353030 (ASCII "2500") for 25MHz and 0x33323030 (ASCII "3200") for 32MHz
boards - I checked this on the MV162-042 (25MHz) and the MV162-532 (32MHz).
I do use different values for SYS_CPU_FREQ in the VxWorks configuration
config/mv162/config.h depending on the board version, so maybe this is
written into the NVRAM at boot time.
Does VxWorks keep its own copy of the CPU speed value? Does my method work
on mv167's, too? What does 0x21ee stand for? Should I use sysNvRamGet() to
stay board independent?
Confused,
Ralph
- Replies:
- Re: CPU speed on mv162/167 Andrew Johnson
- References:
- Re: Boot files for MVME167 Andrew Johnson
- Navigate by Date:
- Prev:
SGL encoder in EPICS Noboru Yamamoto
- Next:
Re: Bad CALC record kills IOC Tim Mooney
- 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:
Re: Boot files for MVME167 Andrew Johnson
- Next:
Re: CPU speed on mv162/167 Andrew Johnson
- 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
|