Experimental Physics and Industrial Control System
You don't say what your vxWorks host processor is, so I'll take a stab in
the dark here.
The way WRS handles the issue of making processor memory visable from the
vme bus is a bit strange, at least to our way of thinking. You may recall
that John W. patched the kernel to provide a fix for the memory mapping,
which is necessary because the NI-1014 board does DMA to the cpu memory.
If the memory<->vme bus mapping is not correct you will get errors similar
to what you are describing. I don't know if there are other examples of
device/driver support that also use DMA.
AFAIK this may only apply to mv162 processors, but it seems reasonable that
there are others that may suffer from the same problem. I know at one point
I had to kludge other Motorola cards because of similar problems.
You might compare Johns' modified kernel against the old and new "stock
kernels; perhaps the results may point to a solution.
Disclaimer: Any opinions are my own and have | -bill
nothing to do with the official policy or the | [email protected]
management of L.B.N.L, who probably couldn't | Berkeley, CA
care less about employees who play with trains. | aka [email protected]
- Navigate by Date:
- Prev:
GPIB+VxWorks3.5.1 problem Josep A. Perlas
- Next:
can't boot VxWorks on MVME177 Paul Sichta
- 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:
GPIB+VxWorks3.5.1 problem Josep A. Perlas
- Next:
can't boot VxWorks on MVME177 Paul Sichta
- 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