Development Environment and FECs / SCUs

Computers for building FESA/DevAcc Software

At GSI the following computers can be used to design, code, compile and link FESA classes and equipment:

• asl740, asl741, asl742, asl743, asl744 ( CentOS (acc7), 64-bit architecture, FESA3 4.0.0 to 7.3.0 )
• asl751 to asl755 (Rocky9 - acc9 / yocto, 64-bit architecture, FESA3 7.5.0 and later)

Computers for testing FESA/DevAcc Software

Note that FESA software build on the acc7 cluster can be tested directly on that cluster, if no timing-network is required.

The following front end computers may be used for testing purposes. Be aware: This list might be outdated! (Last complete update: 25/09/2023).

To make use of one of these front end computers, follow these steps:

• Ask other users registered for that system for access, if there are any
• Make sure no other FESA/Devacc binary is running on the chosen computer (If so, check who is running it)
• register yourself in this list with your full name. If you are an external, as well provide a mail address.
• If the usage is temporary, unregister yourself when you are done

scuxl0061	mit ACU, ohne WR	scuxl	BR3.2.117a
scuxl0104	mit ACU, ohne WR, + FM900 745 (Adapter) + FG900 740 (universal IO)	scuxl	BR3.2.117a
scuxl0121	mit ACU, ohne WR	scuxl	BR3.2.117a
scuxl0134	mit FG900 810 (Inputkarte 8 IN)	scux.el7	BR3.2.117a
scuxl0646	mit FG901 152 (SIO Mil)	yocto	BR3.2.117a
ka2cg04	VME-GuP, PPC, neue SE auf 2 und alte SE auf 3	cpu87	BR3.2.117a
vmla0**	Virtual FECs without timing ... see separate list	-	-	-
dal004	Supermicro with connected picoscopes	scuxl	BR3.2.117a	Alexander Schwinn
scuxl0640	mit FG901 152 (SIO Mil) mit Devicebuskabel zum BEA-Testrack	yocto	BR3.2.117a	Alexander Schwinn / Rok Hari (Cosylab)
Computers for testing DevAcc Software
Computers for testing FESA Software
name	system-info	Ram Disk	location	currently used by
name	system-info	Ram Disk	location	currently used by
scuxl0004		yocto	BR3.2.117a	Dominic Day
scuxl0052	mit FG900.161 mit scuxl0344 im Crate	yocto	BR3.2.117a	Dominic Day
kp1cg33	VME-GuP, PPC	lfos-boot-cpu87-testing.bin	BR3.2.160 - Büro	Grzegorz Kowalski <g.kowalski@gsi.de>
ke3cg07	SDDSC022 Leihgabe von BEA	cpu87	BR3.2.117a	Matthias Wiebel
scuxl0559		scuxl	BR3.2.117a	Peter Kainberger
scuxl0657		scuxl	BR3.2.117a	Peter Kainberger
scuxl0081	mit FG352 410 (DDS-RingHF)	scuxl	BR3.2.117a	Tobias Habermann
scuxl0002	mit scuxl0141 im Crate	scuxl	BR3.2.117a	Tobias Habermann., Matthias Wiebel
scuxl0141	mit scuxl002 im Crate	scuxl	BR3.2.117a	Tobias Habermann., Matthias Wiebel
kp1cg01	VME-GuP, mit SEs	cpu87-20220407	BR3.2.117a	Ulf Reinhardt
scuxl0344	mit scuxl0052 im Crate	scuxl	BR3.2.117a	Ulf Reinhardt / Vitaliy Rapp

Other FECs

• Pro: Productive FECs are currently tracked by Icinga.
• Int: FECs in the integration systems are currently tracked by Icinga.
• A list of the virtual FECs is available here: https://www-acc.gsi.de/wiki/Frontend/VirtualFrontends .

FEC Configuration

All FEC's share the same basic structure of an Initrd Based Linux System and are located in the accelerator network (connect via '.acc.gsi.de' suffix)

• Information about the file system for FEC's: FEC file system.
• For productive FECs, here some info on how to use hostnames / GSI nomenclatures as FEC names: https://www-acc.gsi.de/wiki/FESA/FrontEnds
  • For FEC configuration of a FESA3 deploy-unit this means that the FEC folder still has to be named like the original hostname of the FEC (unexpected!)
  • Logging in to the FEC also requires the original hostname (unexpected!)
  • Retrieving log messages from the booting FEC also requires the original hostname (unexpected!)
  • If nomenclatures for FEC names are used in capital letters, they cannot be distinguished any more from common device names at first sight

RAM Disk Configuration

• Information about boot-configuration: Start on EmbeddedSystems.
• This Wiki page provides information on how to read/set the PXE links for the Linux image and RAM disk of a FEC.