Peregrine McGehee wrote:
I have an IP module driver that sets the slot memory base
to 0x7200000 on an MVME-162 (Petra). We are upgrading from
vxWorks 5.1.1 to vxWorks 5.5 (T2.2) and attempts to access
this address now result in an access violation.
I've checked the target/mv162/config.h files - the treatment
of memory seems the same. Suggestions?
Have a look at your old target/mv162/sysLib.c file, in particular the
sysPhysMemDesc[] array, which defines the areas of virtual memory that
get mapped to physical memory - if an address is not covered here, the
MMU will reject it immediately. You probably have an entry in the old
table for the IP memory base address which you need to copy into the new
version.
- Andrew
--
Podiabombastic: The tendency to shoot oneself in the foot.
- References:
- Changes to mv162 BSP in Tornado? Peregrine McGehee
- Navigate by Date:
- Prev:
Changes to mv162 BSP in Tornado? Peregrine McGehee
- Next:
help for error:can't locate program entry point_callocMustSucceed@12 to dynamic link library Com.dll Liu Shu
- 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:
Changes to mv162 BSP in Tornado? Peregrine McGehee
- Next:
help for error:can't locate program entry point_callocMustSucceed@12 to dynamic link library Com.dll Liu Shu
- 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
|