Building the Entire System: Difference between revisions

From GammaSphere DAQ
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
According to notes left from Tim Madden, a multi-stage make is required to build the .munch files for the IOCs.  Munch files are raw binary executable for the MVME5500 generated by a cross compiler.  The cross compiler resides on machine con5, a Sun Solaris machine.  If that machine dies, we're probably in deep trouble.
A multi-stage make is required to build the .munch files for the IOCs.  Munch files are raw binary executable for the MVME5500's VxWorks operating system generated by a cross compiler.  The cross compiler resides on machine con6, a Sun Solaris machine.  This machine has no internal hard disk, it connects to the network file server.  This means files ''can'' be copied willy-nilly but that doesn't mean they ''should'' be.  Yes, physicists, I speak to you. '''DO NOT TOUCH /dk/fs2/dgs/global_sanbox EVER. NO, NEVER!!'''


=== Compiling the Code (Updated September 2021 to use con6) ===
=== Compiling the Code ===
# Log into con6 as dgs
# ssh -XY dgs@con6
# cd /global/devel/gretTop/9-22/dgsIoc
# cd /global/devel/dgsDrivers/dgsDriverApp/src
# make -B
# ./Export_SVN_ParameterFiles.sh
# cd ../dgsDrivers
# cd ../..
# make -B
# make clean
# make
## There should be ZERO errors and ZERO warnings.  Anything else is a fatal, full, stop.
# cd ../dgsIoc
# cd ../dgsIoc
# make clean
# make
# make
## There should be ZERO errors and ZERO warnings.  Anything else is a fatal, full, stop.
# Log out of con6
# Log out of con6
# Log into dgs1 as dgs
# Log into dgs1 as dgs
# cd /global/devel/gretTop/9-22/dgsIoc
# cd /global/ioc/bin/vxWorks-ppc604_long
# ./Copy_from_sandbox.sh (This last command copies the munch file from con6 to dgs1, making it available to the MVME5500s.)
# ./CopyNewMunch.sh
 
===Procedure as Found On the DGS Repository===
'''''As of September 2021 this procedure is out of date as con5 is offline.'''''
*SSH to con5 on onenet.
*This is a solaris sytem that has the vxWorks cross compilier.
*First you build various libraries of DGS, such as the Sender, board drivers, VME drivers.
*Then you build the whole system to link all the libraries together into a “munch” file, or vxWorks executable code.
 
On con5 enter the following commands:
<pre>
cd /global/devel/gretTop/9-22
cd dgsDrivers
make
cd ..
cd dgsData
make
cd ..
cd gretVME
make
cd dgsIoc
make
</pre>

Revision as of 00:28, April 1, 2023

A multi-stage make is required to build the .munch files for the IOCs. Munch files are raw binary executable for the MVME5500's VxWorks operating system generated by a cross compiler. The cross compiler resides on machine con6, a Sun Solaris machine. This machine has no internal hard disk, it connects to the network file server. This means files can be copied willy-nilly but that doesn't mean they should be. Yes, physicists, I speak to you. DO NOT TOUCH /dk/fs2/dgs/global_sanbox EVER. NO, NEVER!!

Compiling the Code

  1. ssh -XY dgs@con6
  2. cd /global/devel/dgsDrivers/dgsDriverApp/src
  3. ./Export_SVN_ParameterFiles.sh
  4. cd ../..
  5. make clean
  6. make
    1. There should be ZERO errors and ZERO warnings. Anything else is a fatal, full, stop.
  7. cd ../dgsIoc
  8. make clean
  9. make
    1. There should be ZERO errors and ZERO warnings. Anything else is a fatal, full, stop.
  10. Log out of con6
  11. Log into dgs1 as dgs
  12. cd /global/ioc/bin/vxWorks-ppc604_long
  13. ./CopyNewMunch.sh
Retrieved from "https://wiki.anl.gov/wiki_gsdaq/index.php?title=Building_the_Entire_System&oldid=4231"