Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  02 Aug 2023, Caleb Marshall, Forum, Issues with Universe II Driver  
    Reply  02 Aug 2023, Konstantin Olchanski, Forum, Issues with Universe II Driver  
       Reply  03 Aug 2023, Caleb Marshall, Forum, Issues with Universe II Driver  
          Reply  03 Aug 2023, Konstantin Olchanski, Forum, Issues with Universe II Driver  
             Reply  03 Aug 2023, Caleb Marshall, Forum, Issues with Universe II Driver  
                Reply  04 Aug 2023, Caleb Marshall, Forum, Issues with Universe II Driver  
                   Reply  04 Aug 2023, Konstantin Olchanski, Forum, Issues with Universe II Driver  
Message ID: 2571     Entry time: 03 Aug 2023     In reply to: 2570     Reply to this: 2572
Author: Konstantin Olchanski 
Topic: Forum 
Subject: Issues with Universe II Driver  
> Here is the output:
> 
> vmic_mmap: Mapped VME AM 0x0d addr 0x00000000 size 0x00ffffff at address 0x80a01000
> mvme_open:
> Bus handle              = 0x3
> DMA handle              = 0x158f5d0
> DMA area size           = 1048576 bytes
> DMA    physical address = 0x7f91db553000
> vmic_mmap: Mapped VME AM 0x2d addr 0x00000000 size 0x0000ffff at address 0x86ff0000
> vme addr: 00000000 
> addr: db543000 

I see the problem. A24 is mapped at 0x80xxxxxx, A16 is mapped at 0x86ffxxxx, but 
mvme_read computed address 0xdb543000, out of range of either mapped vme address. ouch.

One more thing to check, AFAIK, this universe-II codes were never used on 64-bit CPU 
before, we only have 32-bit Pentium-3 and Pentium-4 machines with these chips. The 
tsi148 codes used to work both 32-bit and 64-bit, we used to have both flavours of 
CPUs, but now only have 64-bit.

What is your output for "uname -a"? does it report 32-bit or 64-bit kernel?

If you feel adventurous, you can build 32-bit midas (cd .../midas; make linux32), 
compile vmescan.o with "-m32" and link vmescan.exe against .../midas/linux-m32/lib, and 
see if that works. Meanwhile, I can check if vmicvme.c is 64-bit clean. Checking if 
kernel module is 64-bit clean would be more difficult...

K.O.
ELOG V3.1.4-2e1708b5