Virtual machine installation for ISE 14.7/Impact

Impact -as part of the ISE tool chain- is required to program older Xilinx FPGAs (respective their attached FLASH memory chips), like the Spartan-2 family on the SIS3316 VME digitizer.

The document below describes how to install a virtual machine under Windows 10 and 11 for the use of ISE14.7.

Posted in Uncategorized | Tagged , , , , , , , | Leave a comment

Skip SIS3316 FLASH ID Code Check

The obsolete W25Q64FVSSIG FLASH memory of the SIS3316 VME digitizer needed to be replaced with the compatible type W25Q64JVSSIM at some point after the end of iMPACT support.
The ‘ID check’ must be deactivated in order to program this new FLASH type with iMPACT.

To do this, the line ‘export XIL_IMPACT_SKIPIDCODECHECK=1’ must be inserted at the end of the ‘.bashrc’ file:

  1. Start the ISE 14.7 VM
  2. Open a terminal: Applications > System Tools > Terminal
  3. copy and paste the following into the terminal and execute it: echo “export XIL_IMPACT_SKIPIDCODECHECK=1” >> ~/.bashrc
  4. Restart the VM

The FLASH to be selected can be seen below:

Select FLASH

The same holds for higher serial numbers the SIs8300-L2 and SIS8325 digitizer AMCs (please refer to SIS8300/8325/x PROM IDCODE not recognized by Impact | Struck DAQ Blog).

Posted in Uncategorized | Tagged , , , , , | Leave a comment

EPICS module for the SIS3153 USB3.0 to VME Interface

An EPICS module for support of SIS 3150 and 3153 USB to VME interface boards .

The support is a driver derived from asynPortDriver. The driver allows records to perform VME I/O using standard asyn device support.

The driver is based on a library from SIS for the low-level USB to VME transactions. This library is included in this module, so nothing else needs to be downloaded.

https://github.com/epics-modules/SIS3153

Thanks to Mark Rivers for the implementation.

Posted in Uncategorized | Tagged , , , , | Leave a comment

Possible DS8VM1 R13/R13b CLKOUT5 instability in Distribution Clock Mode

An issue with the CLKOUT5 output on some units in Distribution Clock Mode was reported on the more recent R13 and R13b revisions of the DS8VM1.

Installing 100 nF 0402 X7R capacitors on C17R1 (supplying VCC11 CLK4 DAC CLK of the LMK04906 chip) and C17S1 (supplying VCC12 CLK5 FPGA CLK) -similar to earlier revisions- fixes the anomaly.

Posted in Uncategorized | Tagged , , | Leave a comment

SIS315x USB to VME Interface LINUX access right issue

In particular with newer Linux distributions it can happen that a SIS315x cannot be accessed via USB.
The “OpenTest” program will terminate with the following error message in that case:

Hello world!
device 0
path: 002/005
vendor: 1657
product: 3153
Error in ‘Sis3150usb_OpenDriver_And_Download_FX2_Setup’: -1

The error is caused by missing write permissions for the USB device. To request the required authorizations, a new udev rule must be added to /usr/lib/udev/rules.d.
Create the file “99-struck-sis315x.rules” in this directory and add the following content:

# SIS3150 USB
SUBSYSTEM==”usb”, ATTR{idVendor}==”1657″, ATTR{idProduct}==”3150″, MODE=”0666″
# SIS3153 USB
SUBSYSTEM==”usb”, ATTR{idVendor}==”1657″,ATTR{idProduct}==”3153″, MODE=”0666″

Get 99-struck-sis315x.rules file

The SIS315x should be accessible without error after a system restart.

Posted in Uncategorized | Tagged , , , , , , , , | Leave a comment

SIS1100 Linux Driver 2.16 under AlmaLinux 9.4

Issue:
Possible use of change from mainline kernel 6.4.0 in transition from AlmaLinux 9.2 to 9.4 (5.14.0-284 -> 5.14.9-427)

Error:
> Error: too many arguments for function »class_create«
> 573 | sis1100_global.class = class_create(THIS_MODULE,
> "sis1100");

Workaround:
sis1100_autoconf_linux.c ca. line 570:

sis1100_global.class = class_create(THIS_MODULE, "sis1100");
change to:
sis1100_global.class = class_create("sis1100");

Posted in Uncategorized | Tagged , , , | Leave a comment

OpenSource Article on SIS1160/SFMC 2.5 GSPS 14-Bit High Count Rate Data Aquisition

Under the Link below you can access a repository, that contains raw experimental data acquired during a gELBE beam time in October 2023.

In this setup, a bremsstrahlung beam of up to 12.5 MeV energy in 13 MHz pulses irradiates a CeBr3 scintillation detector (by Hilger®) of Ø 1” x 1”, coupled to a Hamamatsu® R13408-100 PMT, custom voltage divider and shaping electronics, and a commercial digitizer (SFMC01+SIS1160) by Struck®, containing an AD9689 chip that supports a data sampling rate of 2.5 Gsps and 14-bits. 

High-count rate photon detection with scintillators coupled to photomultiplier tubes and fast digitizers | RODARE (hzdr.de)

Posted in Digitizer | Tagged , , , , , , , , | Leave a comment

NIM A Article on the Use of 2.5 GSPS 14-Bit SIS1160/SFMC01 PCIe Digitizer for Prompt Gamma-ray Measurements During Proton Therapy Treatments

The use of a SIS1160 PCI Express carrier with a SFMC01 Digitizer FMC for dead-time free data acquisition during proton therapy treatments is described in the NIM A article under the link below:

A dead-time-free data acquisition system for prompt gamma-ray measurements during proton therapy treatments – ScienceDirect

Posted in Uncategorized | Tagged , , , | Leave a comment

SIS1100-e2/eCMC Fujitsu BIOS Freeze (and Change of Size of Mapped Window)

Issue:

PC with SIS1100-e/eCMC freezes/hangs at power up.

Reported by Marcus Fleck from DESY for a Fujitsu d3598-b13 mainboard initially.

Solution:

Change the PCI Class ID from:

07h Simple Communications Device

to:

06h Other Bridge device

Software and instructions for the change (and to change the size of the mapped window) can be found here.

Prerequisite: driver version 8.0.0.11 has to be installed

Posted in Uncategorized | Tagged , , , , , | Leave a comment

SIS1100 Driver With Windows 10 HVCI Signature

Some Windows 10 systems (typically new machines) with the most recent Version 2004 of the operating system have HVCI (Hypervisor-protected Code Integrity) activated. The used German expression is ‚Kernisolation’.
Drivers from 8.0.0.11 onwards are furnished with HVCI compliant driver signage.

Older Drivers are not started by Windows and are typically reported with error Code 39 in the device Manager.

The reason for the major version change from 6.4.2.x to 8.0.0.x is the migration from the underlying PLX to the more recent Broadcom code.

Posted in Driver | Tagged , , , , | Leave a comment