Follow Us
13Z014-71 - VME4WIN/MDIS5 Software Package (MEN) - VMEbus support under Windows for MEN A19, A20 and A22
VME4WIN/MDIS5 Software Package (MEN) - VMEbus support under Windows for MEN A19, A20 and A22
Download 13z01471.zipiUse this package for MEN A22 VMEbus CPU board! -----[ Revision 3.0 ]-----
[ 2014-03-21 15:23:51 by dpfeuffer ]
R:1. 16Z002-02 VMELL driver development
2. 16Z002-02 driver: VMELL_RequestVmeAddrWindow: error handling erroneous
3. 16Z002-02 driver: VMELL_GetRevision: HW revision missing
4. ctrl-C abort of appl. statically linked with vme4win.lib hangs
5. performance test tool required
M:1. minor fixes during code review, debugs modified
2. 16Z002-02 driver: error handling fixed
3. 16Z002-02 driver: using RevisionID from FPGA PCI device config space as HW revision
4. fixed in vme4win lib, executables new built
5. VMEPERF (vmeperf.exe) added
-----[ Revision 1.4 ]-----
[ 2014-02-28 16:26:57 by dpfeuffer ]
R:1. 16Z002-02 VMELL driver development
M:1.a) 16Z002-02 VMELL driver added
b) VMELL drivers start no longer as boot driver (now StartType=0x3)
c) TSI148 VMELL driver modified according required VMEK changes
d) vme4win_clinst: disable hardware swapping options if the VMELL driver
doesn't support it
e) vme4win_lib: used IOCTL codes to VMEK changed (old range was reserved
for Microsoft!)
f) all non-dll executables linked with updated vme4win.lib that uses
changed IOCTL codes for VMELL driver
g) vme_m99_a201.exe: completely revised
h) vmectrl.exe: address spaces now VMELL driver specific
i) documentation completely revised (not yet finished!)
-----[ Revision 1.3 ]-----
[ 2013-02-12 11:13:04 by Apb ]
R: It was not possible to install more than 8 slave boards because the driver
installed each new slave board in a new outbound windows, regardless of the
size of previously mapped windows.
M: Return the real mapped size to the VMEK library to take count of the atomic
mapped size of 0x10000 of the TSI148's outbound window.
-----[ Revision 1.2 ]-----
[ 2012-08-09 11:51:54 by Apb ]
R : Access to 24 bits VME addresses with a granularity < 0x10000 was not possible.
M : Modifying of the local address offset to take care of a higher granularity.
Now a granularity of 0x100 is possible.
-----[ Revision 1.1 ]-----
[ 2010-05-04 13:37:09 by CKauntz ]
Initial Revision
Download 13z01471_rev1_3.zipiUse this package for MEN A19/A20 VMEbus CPU boards!Errata for VME accesses via VME_Read(): When VME_Read is used to access a VME space, the region must previously also be mapped using the VME_Map function. -----[ Revision 1.3 ]-----
[ 2013-02-12 11:13:04 by Apb ]
R: It was not possible to install more than 8 slave boards because the driver
installed each new slave board in a new outbound windows, regardless of the
size of previously mapped windows.
M: Return the real mapped size to the VMEK library to take count of the atomic
mapped size of 0x10000 of the TSI148's outbound window.
-----[ Revision 1.2 ]-----
[ 2012-08-09 11:51:54 by Apb ]
R : Access to 24 bits VME addresses with a granularity < 0x10000 was not possible.
M : Modifying of the local address offset to take care of a higher granularity.
Now a granularity of 0x100 is possible.
-----[ Revision 1.1 ]-----
[ 2010-05-04 13:37:09 by CKauntz ]
Initial Revision
Licensing Information
[ 2014-03-21 15:23:51 by dpfeuffer ]
R:1. 16Z002-02 VMELL driver development
2. 16Z002-02 driver: VMELL_RequestVmeAddrWindow: error handling erroneous
3. 16Z002-02 driver: VMELL_GetRevision: HW revision missing
4. ctrl-C abort of appl. statically linked with vme4win.lib hangs
5. performance test tool required
M:1. minor fixes during code review, debugs modified
2. 16Z002-02 driver: error handling fixed
3. 16Z002-02 driver: using RevisionID from FPGA PCI device config space as HW revision
4. fixed in vme4win lib, executables new built
5. VMEPERF (vmeperf.exe) added
-----[ Revision 1.4 ]-----
[ 2014-02-28 16:26:57 by dpfeuffer ]
R:1. 16Z002-02 VMELL driver development
M:1.a) 16Z002-02 VMELL driver added
b) VMELL drivers start no longer as boot driver (now StartType=0x3)
c) TSI148 VMELL driver modified according required VMEK changes
d) vme4win_clinst: disable hardware swapping options if the VMELL driver
doesn't support it
e) vme4win_lib: used IOCTL codes to VMEK changed (old range was reserved
for Microsoft!)
f) all non-dll executables linked with updated vme4win.lib that uses
changed IOCTL codes for VMELL driver
g) vme_m99_a201.exe: completely revised
h) vmectrl.exe: address spaces now VMELL driver specific
i) documentation completely revised (not yet finished!)
-----[ Revision 1.3 ]-----
[ 2013-02-12 11:13:04 by Apb ]
R: It was not possible to install more than 8 slave boards because the driver
installed each new slave board in a new outbound windows, regardless of the
size of previously mapped windows.
M: Return the real mapped size to the VMEK library to take count of the atomic
mapped size of 0x10000 of the TSI148's outbound window.
-----[ Revision 1.2 ]-----
[ 2012-08-09 11:51:54 by Apb ]
R : Access to 24 bits VME addresses with a granularity < 0x10000 was not possible.
M : Modifying of the local address offset to take care of a higher granularity.
Now a granularity of 0x100 is possible.
-----[ Revision 1.1 ]-----
[ 2010-05-04 13:37:09 by CKauntz ]
Initial Revision
Download 13z01471_rev1_3.zipiUse this package for MEN A19/A20 VMEbus CPU boards!Errata for VME accesses via VME_Read(): When VME_Read is used to access a VME space, the region must previously also be mapped using the VME_Map function. -----[ Revision 1.3 ]-----
[ 2013-02-12 11:13:04 by Apb ]
R: It was not possible to install more than 8 slave boards because the driver
installed each new slave board in a new outbound windows, regardless of the
size of previously mapped windows.
M: Return the real mapped size to the VMEK library to take count of the atomic
mapped size of 0x10000 of the TSI148's outbound window.
-----[ Revision 1.2 ]-----
[ 2012-08-09 11:51:54 by Apb ]
R : Access to 24 bits VME addresses with a granularity < 0x10000 was not possible.
M : Modifying of the local address offset to take care of a higher granularity.
Now a granularity of 0x100 is possible.
-----[ Revision 1.1 ]-----
[ 2010-05-04 13:37:09 by CKauntz ]
Initial Revision
Licensing Information
VME4WIN means VMEbus Support for Windows
It provides access to the VMEbus under Windows XP/Vista/7 (32-bit and 64-bit) to access the VMEbus using common programming languages (e.g. C, C++, VB).
Contents of the VME4WIN/MDIS5 Package
- The VME4WIN software package comprises the following software modules:
- VME4WIN Drivers (Windows kernel mode drivers) for the supported PCI(e)-to-VMEbus bridges
- The VME4WIN Library (provided as static library and DLL), that provides the VME/VMECTRL-API
- Example C programs (including source code), that demonstrate the usage of the VME/VMECTRL-API from application software
- Documentation as 'Compiled HTML Help File'
Supported VME-PC Hardware
- TSI148 driver for the TSI148 PCI-to-VMEbus bridge chip on MEN A19/A20 VMEbus CPU boards
- 16Z002 driver for the MEN 16Z002 V2 PCIe-to-VMEbus FPGA IP core on MEN A22 VMEbus CPU boards
MDIS5 Compatibility
The VME4WIN drivers can be used in conjunction with MDIS5 drivers
Licensing Information
This article is free of charge.
Ordering Information & Downloads
Main Software
13Z014-71
VME4WIN/MDIS5 Software Package (MEN) - VMEbus support under Windows XP/Vista/Windows 7 for MEN A19 and A20