I'm trying to get a '162 running vxw_5.3 to work with a VPIC-616.
Because
of the characteristics of the IP card in question, I'd prefer to use the
extended addressing mode on the vme bus. Note that this is the default
setup
of the '616 as it is received from the manufacturer. The jumpers appear
to
be properly configured.
I can talk to the part of the carrier that resides in the short I/O
space with
no problem. I cannot talk to the carriers memory space, which is mapped
into
the extended address space at 0xd000000.
Since my vme analizer never sees an attempt at a bus cycle, I think that
the
problem is probably with the '162 and/or its BSP. I've dug out the
hardware
manual and it looks like the three registers needed to map the vme bus
extended
address space to the card have reasonable values in them:
Local Bus Slave (VME Master) Ending Addr Reg 1 (0xfff40014) 0xefff
Local Bus Slave (VME Master) Starting Addr Reg 1 0x0080
Map VME addresses from 0x00800000 to 0xefff0000 to
local bus
Local Bus Slave (VME Master) Attribute Reg 1 (0xfff40028) 0x0000
0x0009
Bits 0-5 = address modifier for vme, EXT-USER_DATA
Bit 6 = WP (off), and bit 7 = D16 (off)
Local Bus to VME Bus Enable Control Reg (0xfff4002c) 0xc201
0xad00
Bit 16 = 1, enable map #1
Has anyone tried this? Did it work? If so, what am I overlooking?
Any and all suggestions appreciated.
--
-bill
- Navigate by Date:
- Prev:
RE: network problem w/ ioc Jeff Hill
- Next:
Re: logging onto an ioc (rlogin,telnet) Noboru Yamamoto
- 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: network problem w/ ioc Jeff Hill
- Next:
SENS from WRS and PowerPC; working Janousch Markus
- 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
|