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: 2566     Entry time: 02 Aug 2023     Reply to this: 2567
Author: Caleb Marshall 
Topic: Forum 
Subject: Issues with Universe II Driver  

Hello,

At our lab we are currently in the process of migrating more of our systems over to Midas. However, all of our working systems are dependent on SBCs with the Tsi-148 chips of which we only have a handful. In order to have some backups and spares for testing, we have been attempting to get Midas working with some borrowed SBCs (Concurrent Technologies VX 40x/04x) with Universe-II chips. The SBC is running CentOS 7. I have tried to follow the instructions posted here. The universe-II kernel module appears to load correctly, dmesg gives:

[   32.384826] VME: Board is system controller
[   32.384875] VME: Driver compiled for SMP system
[   32.384877] VME: Installed VME Universe module version: 3.6.KO6
 

However, running vmescan.exe fails with a segfault. Running with gdb shows:

vmic_mmap: Mapped VME AM 0x0d addr 0x00000000 size 0x00ffffff at address 0x80a01000
mvme_open:
Bus handle              = 0x7
DMA handle              = 0x6045d0
DMA area size           = 1048576 bytes
DMA    physical address = 0x7ffff7eea000
vmic_mmap: Mapped VME AM 0x2d addr 0x00000000 size 0x0000ffff at address 0x86ff0000

Program received signal SIGSEGV, Segmentation fault.
mvme_read_value (mvme=0x604010, vme_addr=<optimized out>)
    at /home/jam/midas/packages/midas/drivers/vme/vmic/vmicvme.c:352
352        dst  = *((WORD *)addr);
 

With the pointer addr originating from a call to vmic_mapcheck within the  mvme_read_value functions in the vmicvme.c file. Help with where to go from here would be appreciated.

-Caleb 

 

ELOG V3.1.4-2e1708b5