How To Compile CURI FAmodule in CentOS 7.2 with U1709 64-Bit OS and CURI 1.21

Note that this instruction is tested only with the following system and software versions:

OS: CentOS 7.2
Unison: U1709
Curi: CURI_1.12_2.121.x86_64

1. edit your project.makefile to look like this:

TARGET_MINOR_VERSION = 1

SO_TARGET = fademo_hooks.so

# -- Start of project files --
PROJECT_SOURCES = fademo_attach.cpp \
fademo_hooks.cpp  \

PROJECT_HEADERS   = fademo_hooks.h \

NO_PTHREAD=true
MBITS=64
PROJECT_INCLUDE_PATHS = -DLINUX_TARGET -DLINUX -DUNISON -I. -I/ltx/include 
PROJECT_LIBRARIES=-Wl,-rpath,/ltx/lib$(MBITS) -L/ltx/lib$(MBITS) -levxa

ifeq ("$(BUILD_OS)", "Linux")
CFLAGS:=-DLINUX_TARGET
endif

LDFLAGS:=

prepare:

Note the "MBITS=64" added

2. update all "long" arguments in fademo_hooks.h, fademo_attach.cpp, fademo_hooks.cpp to FA_LONG and "unsigned long" to FA_ULONG if any

3. use this command to compile > gmake CFG=Release MBITS=64 MBITS_CURI=64

4. after compiling as above, the .so files are stored in ~Release/ folder. rename Release to Release64 

5. update CURI config file /opt/ateTools/curi/unison/config/curi_conf.xml to point to this FAmodule:

<CURI_CONF>
    <Config Configuration_ID="DefaultConfiguration">
        <ConfigEnv Equipment_Path="/opt/ateTools/curi/unison/lib" Communications_Path="/opt/ateTools/curi/unison/lib" User_Path="/home/localuser/Desktop/famodule/Release"/>
        <CommunicationsList>
            <GPIB_IF>
                <Settings>
                    <stringSetting token="IbcAUTOPOLL" value="0"/>
                </Settings>
            </GPIB_IF>
            <RS232_IF/>
            <TTL_IF/>
            <TTL_IF DriverID="ASL PCI PORT" AccessName="ASL_XP_TTL" Library="curi_asl_ttl" />
            <TTL_IF DriverID="ASL AT PORT" AccessName="ASL_NT_TTL" Library="curi_asl_ttl" />
            <TCPIP_IF Port="65000"/>
            <USB_IF/>
        </CommunicationsList>
    </Config>

    <UserLibrary AccessName="Demo famodule" Library="fademo_hooks">
        <Settings>
    <stringSetting token="Module Type" value="FAPROC Module"/>
    <stringSetting token="Priority" value="50"/>
        </Settings>
    </UserLibrary>

Where /home/localuser/Desktop/famodule/Release is the path (without the '64' suffix) where your Famodule .so file is located and fademo_hooks is the name of the .so file

6. make sure to relaunch Unison

How to Install and Test CURI

• Download CURI package from Expedite (Software Support)
• Make sure to choose the right version 
• enVision 
• isg_enVision_curi-<version.<arch>.rpm
• e.g. isg_enVision_curi-1.12-1.117.cnt4.6.i386.rpm 
• Unison
• isg_unison_curi-<version>.<arch>.rpm
• e.g. isg_unison_curi-1.12-2.117.cnt4.6.i386.rpm
• Note: The above filename convention is supposed to be for versions older than 112. However, newer versions such as the example above (version 117) are still observed to be following the old naming convention. refer to curi deployment presentation for this issue
• Install CURI package
• login as root
• >rpm -ivh <curi>.rpm
• make sure not to use -uvh as option
• Check for install locations
• Windows: c:\opt\ateTools\curi\CURI_<release>
• Linux: /opt/ateTools/curi/CURI_<version>
• e.g. installing isg_enVision_curi-1.12-1.117.cnt4.6.i386.rpm
• Install location: /opt/ateTools/curi/CURI_CURI_1.12_1.117
• e.g. installing isg_unison_curi-1.12-2.117.cnt4.6.i386.rpm
• Install location: /opt/ateTools/curi/CURI_CURI_1.12_2.117
• Symbolic links: /opt/ateTools/curi/
• Legacy - ITE and enVision
• CURI=> <curi directory>
• Unison
• unison => <curi directory>
• CURI config file locations
• Unison: /opt/ateTools/curi/unison/config/curi_conf.xml
• enVision: /opt/ateTools/curi/CURI/config/curi_conf.xml
• Optional: Change write permissions of curi_conf.xml
• curi_conf.xml can be found here:
• Unison: /opt/ateTools/curi/unison/config/curi_conf.xml
• enVision: /opt/ateTools/curi/CURI/config/curi_conf.xml
• Verify if CURI is installed correctly
• Linux
• /opt/ateTools/curi/CURI_<release>/bin/test_curi 
• /opt/ateTools/curi/CURI_<release>/bin/test_curi -noTestLoop
• option to not enter into loop mode
• Ignore the "FAILED: onEquipment not supported..." in the output log
• Windows
• C;\opt\ateTools\curi\CURI_<release>bin/test_curi.exe
• Above commands will list all equipment this CURI release knows. if no list comes out, something is wrong

How to uninstall CURI from CentOS

• login as root
• to find the installed curi package, execute this command
• >rpm -qa | grep curi 
• rpm -e <curi>

Install locations:

• Windows: c:\opt\ateTools\curi\CURI_<release>
• Linux: /opt/ateTools/curi
• Pre v112
• /opt/ateTools/curi/CURI_<release>
• v112 and higher
• /opt/ateTools/curi/diamond-curi-<release>
• /opt/ateTools/curi/enVision-curi-<release>
• /opt/ateTools/curi/unison-curi-<release>
• note that the diamond is for ITE
• Symbolic links
• Legacy - ITE and enVision
• CURI=> <curi directory>
• Unison
• unison => <curi directory>
• CURI config file locations
• Unison
• /opt/ateTools/curi/unison/config/curi_conf.xml
• enVision
• /opt/ateTools/curi/CURI/config/curi_conf.xml

How to verify if CURI is installed correctly

• Linux
• /opt/ateTools/curi/CURI_<release>/bin/test_curi 
• /opt/ateTools/curi/CURI_<release>/bin/test_curi -noTestLoop
• option to not enter into loop mode
• Windows
• C;\opt\ateTools\curi\CURI_<release>bin/test_curi.exe
• Above commands will list all equipment this CURI release knows. if no list comes out, something is wrong