>It _looks_ like perhaps part of the boot-loader is getting over-written by the
>down-loaded kernel.
Hmmm... just a thought:
The memory size info in the Makefile and friends for vxWorks is set up like
crap [That is, it is in all the BSPs I have had to hack on.] If it is not
set right (and recall that it has to be set in more than one place -- just to
make sure you screw it up a few times first) the loader may fail.
It has been a while since I looked into that part of the init code, but I have
been leaving it set to 4MB for the 167 and letting things get a little
fragmented. If it is set too high, or if the multiple copies of that config
are not set identically (I believe there is doc on that cruft in the Makefile)
gawd knows what could happen.
--John Winans
_ ____ ____ _ _ _
/ \ | _ \/ ___| | | | | __ _ ___| | _____ _ __ __ _ _ _ _ _
/ _ \ | |_) \___ \ | |_| |/ _` |/ __| |/ / _ \ '__| / _` | | | | | | |
/ ___ \| __/ ___) | | _ | (_| | (__| < __/ | | (_| | |_| | |_| |
/_/ \_\_| |____/ |_| |_|\__,_|\___|_|\_\___|_| \__, |\__,_|\__, |
|___/ |___/
- Navigate by Date:
- Prev:
building vxWorks for nitro-260 Bill Brown
- Next:
A possible alignment fix side-effect. Peregrine McGehee
- 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:
building vxWorks for nitro-260 Bill Brown
- Next:
Re: building vxWorks for nitro-260 Bill Brown
- 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
|