This operation, by using the specified address space, reads in 8, 16, 32, or 64 bits of data from the specified offset. This operation does not require or to be called prior to its viMapAddress() viMapAddressEx() invocation. The following table lists the valid entries for specifying address space. Value Description VI_A16_SPACE Address the A16 address space of VXI/MXI bus. VI_A24_SPACE Address the A24 address space of VXI/MXI bus. VI_A32_SPACE Address the A32 address space of VXI/MXI bus. VI_A64_SPACE Address the A64 address space of VXI/MXI bus. Address the PCI configuration space. Address the specified PCI memory or I/O space. – Access physical locally allocated memory. Related Items and See the INSTR and MEMACC resource descriptions. Also see viOut8(), viOut16(), viOut32(), viOut64(). Implementation Requirements RULE 6.3.1 The operations SHALL NOT fail due to the configured state of the hardware used by the viInXX() and memory access operations viMapAddressXX(), viPeekXX(), viPokeXX(). OBSERVATION 6.3.1 The high-level operations operate successfully independently from the low-level operations viInXX() and (viMapAddressXX(), The high-level and low-level operations should viPeekXX(), viPokeXX()). operate independently regardless of the configured state of the hardware that is used to perform memory accesses. RULE 6.3.2 The operations SHALL detect and return on VXI transfers that are viInXX() VI_ERROR_BERR acknowledged by the VXI BERR* (bus error) signal. RULE 6.3.3 All VXI accesses performed by the operation SHALL be D08 reads. viIn8() RULE 6.3.4 All VXI accesses performed by the operation SHALL be D16 reads. viIn16() RULE 6.3.5 All VXI accesses performed by the operation SHALL be D32 reads. viIn32() RULE 6.3.6 All VXI accesses performed by the operation SHALL be D64 reads. viIn64()
This operation, by using the specified address space, reads in 8, 16, 32, or 64 bits of data from the specified offset. This operation does not require viMapAddress() or viMapAddressEx() to be called prior to its invocation. The following table lists the valid entries for specifying address space. Value Description VI_A16_SPACE Address the A16 address space of VXI/MXI bus. VI_A24_SPACE Address the A24 address space of VXI/MXI bus. VI_A32_SPACE Address the A32 address space of VXI/MXI bus. VI_A64_SPACE Address the A64 address space of VXI/MXI bus. Address the PCI configuration space. – Address the specified PCI memory or I/O space. Access physical locally allocated memory. Related Items See the INSTR and MEMACC resource descriptions. Also see viOut8(), viOut16(), viOut32(), and viOut64(). Implementation Requirements RULE 6.3.1 The viInXX() operations SHALL NOT fail due to the configured state of the hardware used by the memory access operations viMapAddressXX(), viPeekXX(), and viPokeXX(). OBSERVATION 6.3.1 The high-level operations viInXX() operate successfully independently from the low-level operations (viMapAddressXX(), viPeekXX(), and viPokeXX()). The high-level and low-level operations should operate independently regardless of the configured state of the hardware that is used to perform memory accesses. RULE 6.3.2 The viInXX() operations SHALL detect and return VI_ERROR_BERR on VXI transfers that are acknowledged by the VXI BERR* (bus error) signal. RULE 6.3.3 All VXI accesses performed by the viIn8() operation SHALL be D08 reads. RULE 6.3.4 All VXI accesses performed by the viIn16() operation SHALL be D16 reads. RULE 6.3.5 All VXI accesses performed by the viIn32() operation SHALL be D32 reads. RULE 6.3.6 All VXI accesses performed by the viIn64() operation SHALL be D64 reads.
vpp43_2015-06-19.docx