Configuration for ioc-b34-cd43

There are many parts that need to be consistent, and many of our failed boots were from inconsistency in kernel version, 32 vs. 64 bit, software in /afs/slac/g/lcls/epics/R3-14-12-4_1-0 vs /afs/slac/g/lcls/epics/ etc.

BPM configuration on 4-8-2015:

ioc-b34-cd43.ipxe

kernel vers 3.2.13-121108

set extra-args ROOTPATH=afsnfs2:/afs/slac:/afs/slac

ioc-b34-cd43/startup.cmd

/afs/slac/g/lcls/epics/iocCommon/All/Dev/linuxRT_nfs.cmd

/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd43/kernel-modules.cmd

echo -n 1 > /sys/module/spurious/parameters/noirqdebug

su laci -c /afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd43/startup-laci-rt.cmd

ioc-b34-cd43/kernel-modules.cmd

KERNEL_DRIVER_HOME=/afs/slac/g/lcls/package/linuxKernel_Modules

SIS8300_DRIVER=$KERNEL_DRIVER_HOME/sis8300drv/Branch_Straumann

PCI_EVR_DRIVER=$KERNEL_DRIVER_HOME/pci_mrfevr_linuxRT/buildroot-uclibc-x86

insmod $PCI_EVR_DRIVER/pci_mrfevr.ko

$PCI_EVR_DRIVER/module_load

modprobe uio

insmod $SIS8300_DRIVER/sis8300drv.ko

chmod ugo+wr /dev/sis*

ln -s /afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd43 /home/root/bpm \[NOTE: should be /root, not /home/root, produced error message\]

ioc-b34-cd43/startup-laci-rt.cmd all viocs commented out

ioc-b34-cd43/startupConsole-laci-rt.cmd

standard ulimit/umask lines

nfs and kernel-module lines, redundant with startup.cmd

cd /afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd43/vioc-in10-bp02

bin/bpmApp iocStartup.cmd

ioc-b34-cd43/vioc-in10-bp02/iocStartup.cmd

Standard pre/post

chdir("/afs/slac/g/lcls/epics/iocTop/Bpm/sonya/Bpm-R9-5-6/iocBoot/vioc-in10-bp02")

../../bin/linuxRT-x86/bpmApp

iocsh("st.cmd")

eltc(0)

Configuration now running for EVR test only

ioc-b34-cd43.ipxe

kernel vers 3.14.12-rt9_x86_64

set extra-args ramdisk_size=524288 ROOTPATH=lcls-dev3:/afs/slac:/afs/slac BOOTFILE=/afs/slac/g/lcls/epics/R3-14-12-4_1-0/iocCommon/ioc-b34-cd43/startup.cmd

ioc-b34-cd43/startup.cmd

Soft link to $IOC/All/Dev/linuxRT_startup_cpu.cmd

Changed path to caRepeater:

su laci -c /afs/slac/g/lcls/epics/R3-14-12-4_1-0/base/base-R3-14-12-4_1-0/bin/linuxRT-x86_64/caRepeater&

Should we move caRepeater to kernel-modules.cmd? Is there a way to use the same script for 32 and 64 bit systems, and systems with different Base versions?

ioc-b34-cd43/kernel-modules.cmd

KERNEL_DRIVER_HOME=/afs/slac/g/lcls/package/linuxKernel_Modules

SIS8300_DRIVER=$KERNEL_DRIVER_HOME/sis8300drv/Branch_Straumann

PCI_EVR_DRIVER=$KERNEL_DRIVER_HOME/pci_mrfevr_linuxRT/buildroot-uclibc-x86_64

^ NOTE: Changed to _64 version ^

insmod $PCI_EVR_DRIVER/pci_mrfevr.ko

$PCI_EVR_DRIVER/module_load

modprobe uio

insmod $SIS8300_DRIVER/sis8300drv.ko

chmod ugo+wr /dev/sis*

ln -s /afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd43 /home/root/bpm \[NOTE: should be /root, not /home/root, produced error message\]

ioc-b34-cd43/startupConsole-laci-evrLab.cmd

standard ulimit/umask lines

cd /afs/slac/g/lcls/epics/iocCommon/vioc-b34-ev43

iocSpecificRelease/bin/linuxRT-x86_64/evrLab iocStartup.cmd

vioc-b34-ev43/iocStatup.cmd

epicsEnvSet("IOC_APP","/afs/slac/g/lcls/epics/R3-14-12-4_1-0/iocTop/evrLab/MAIN_TRUNK")

epicsEnvSet("IOC_BOOT","${IOC_APP}/iocBoot/vioc-b34-ev43")

cd ${IOC_BOOT}

< st.cmd

ev43 screen added to Dev Event IOCs... screen