Hi again,<br><br>Thank you once again for presenting the VME world to me :)<br><br>>Looks like you're reading something. Address 0x10100000 is larger than<br>>a 24 bit address. Perhaps you should be using A32 transfers instead of
<br>>A24?<br><br>No, no, I need to do A16 access, thats the only way to read the control registers. Form here comes also my confusion - I thought that when I'm reading CS/CSR register I need to do it in CSR address space. So no algorithms for geographical location of boards are needed in my case I guess.
<br>Actually the base address of CSR on the board is 0xA000 (10100000 is the first byte of the address selection in inary, shame on me :( ). But when I try to configure it with outWinCfgADC.zlatedAddrL = 0xA000, when I run the programm I get an errno 29 (Invalid argument) from ioctl(). In fact if I set the xlatedAddrL to some value smaller that 0x10000 I get this error. Here's my most recent configuration:
<br><br> outWinCfgADC.windowNbr = 0;<br> outWinCfgADC.windowEnable = 1;<br> outWinCfgADC.wrPostEnable = 0;<br> outWinCfgADC.userAccessType = VME_SUPER;<br> outWinCfgADC.dataAccessType = VME_DATA;
<br> outWinCfgADC.windowSizeL = 0x10000;<br> outWinCfgADC.xferProtocol = VME_SCT;<br> outWinCfgADC.addrSpace = VME_A16;<br> outWinCfgADC.maxDataWidth = VME_D16;<br> outWinCfgADC.xlatedAddrL
= 0x10000000;<br><br>I think that 0x10000 for window size is big enough to encompass the whole A16 addressable space. With the 0x10000000 xlatedAddr I get no errors and read the desired registers when I increment this address to 0x1000A000. But nevertheless it seems strange to me that the device does not accept xlatedAddr lower that 0x10000. Maybe its due to the configuration of the VME controller?
<br><br>Best regards,<br>Konstantin<br>