mv2700 memory map

[Kristi Luchini <luchini@SLAC.Stanford.EDU>]

Hi,

I've recently received an mv2700 powerPC. When I accessed registers on
some VME modules with  A24/D16 and A16/D32 the data is incorrect. I'm
able however to access these modules fine with an mv177. So the memory
mapping on the mv2700 seems to require modification.  Andrew Johnson
suggested that the problem may be with D32/D64 access. I've left the
memory mapping in the EXTENDED_VME mode at the moment.
The change that I've made is in mv2700.h as follows
to Map access to A16 VMEbus - 64K       MAP FOR EXTENDED VME vxWork 

#define VAL_LSI3_CTL            ( LSI_CTL_EN     | LSI_CTL_WP  |\
                                  LSI_CTL_D16    | LSI_CTL_A16 |\
                                  LSI_CTL_SUP    | LSI_CTL_USR |\
                                  LSI_CTL_SINGLE | LSI_CTL_PCI_MEM )
instead of 
            #define VAL_LSI3_CTL            ( LSI_CTL_EN     |
LSI_CTL_WP  |\
                                  LSI_CTL_D64    | LSI_CTL_A16 |\
                                  LSI_CTL_DATA   | LSI_CTL_USR |\
                                  LSI_CTL_SINGLE | LSI_CTL_PCI_MEM )

I was then able to access A16/D32 although it is unclear to me if I've
done the right thing. I have still been unsuccessful
in being able to access A24/D16.  Does anyone have some experience with
modifying the mv2700 memory
map that isn't busy at the EPICS conference this week? I'd appreciate
any help that someone can offer.

    - Regards,
         Kristi