Difference: SctDSPTutorial (7 vs. 8)

Revision 82009-10-01 - unknown

Line: 1 to 1
 
META TOPICPARENT name="AtlasSiliconRodGroup"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 12 to 12
 

Sct DSP Tutorial

<!--optional-->
Changed:
<
<
This Tutorial describes how to set up Code Composer Studio, check out the SCT DSP code, and compile a new version of the binary.
>
>
This Tutorial describes how to check out the SCT DSP code, set up Code Composer Studio and compile a new version of the binary under Windows, and how to setup and build the binaries under Linux.

Checking Out From CVS

At the moment the SCT CVS code is on lxplus, it would be nice to move it over to central ATLAS CVS, but this will be a bit of a faff!
  • The CVS for the old (and currently in use) SCT code is located on lxplus:
  • CVSROOT=:ext:username@lxplus.cern.ch:/afs/cern.ch/user/s/sctpixel/private/cvsroot
  • Module RodDaq
  • Branch: SCT_DSP_DEV_1 for the head of the SCT DSP code
  • Or each version should also be tagged (eg SCT_1_4_1)
  • Please tag code if you make a binary for use in the pit!! It makes it MUCH easier to track changes.
If you intend to build under Windows, it is suggested that you check the code out into the directory:
  • C:\Rod-Sct-development
  • This will be in sync with the project file in CVS, or you can change the path yourself manually.
  • Note that, for Linux builds, you can check out to any directory you like.
 

Code Composer Studio

The Digital Signal Processors (DSPs) are used on the ATLAS Silicon Read Out Drivers (ROD) to control the ROD and histogram calibration
Line: 74 to 88
  A dirty way to get round this problem is to replace the new compiler with the old version, which has been put here: cgtools_31.zip. You need to unzip this directory and place it in the C:\CCStudio_v3.3\C6000 directory. Ensure you make a back up of the old directory first!
Deleted:
<
<

Checking Out From CVS

At the moment the SCT CVS code is on lxplus, it would be nice to move it over to central ATLAS CVS, but this will be a bit of a faff!
  • The CVS for the old (and currently in use) SCT code is located on lxplus:
  • CVSROOT=:ext:username@lxplus.cern.ch:/afs/cern.ch/user/s/sctpixel/private/cvsroot
  • Module RodDaq
  • Branch: SCT_DSP_DEV_1 for the head of the SCT DSP code
  • Or each version should also be tagged (eg SCT_1_4_1)
  • Please tag code if you make a binary for use in the pit!! It makes it MUCH easier to track changes.
It is suggested that you check the code out into the directory:
  • C:\Rod-Sct-development
  • This will be in sync with the project file in CVS, or you can change the path yourself manually.
 
Changed:
<
<

The DSP Project

>
>

The DSP Project

 You should now have everything ready to run Code Composer Studio, and first you need to configure it to tell it which devices to use:
Changed:
<
<

Configuring Code Composer Studio

>
>

Configuring Code Composer Studio

 This describes how to set up CCS to compile the DSP code.
  • First, start the CCS setup.
  • Either click the desktop icon, or via the start menu:
Line: 103 to 105
  setupCCS.JPG
  • Save and quit, when prompted, start CCS on exit.
Changed:
<
<

Starting Code Composer Studio

>
>

Starting Code Composer Studio

 
  • If you want to start CCS later, click the desktop icon:
    ccsIcon.JPG
  • Or start it via the start menu.
Line: 112 to 114
 
  • Go to the directory C:\your\install\dir\RodDaq\Dsp\
  • Open rodRun_sct.pjt for the master, sdsp6713_sct.pjt for slaves.
Changed:
<
<

Compiling the Code

>
>

Compiling the Code

 To compile the DSP code, click on one of the compilation buttons:
  • The Compile buttons in CCS:
    compile.JPG
Line: 121 to 123
 
  • nb - If you don't get the window popping up, you probably need Lab Windows (see Additional Libraries above)
  • This will create binaries and copy them to c:\rodts\data\dspProgram\rodRun
Added:
>
>

Building under Linux

The TI compiler is currently installed on SR1 machines at /work/pcphsctr03/TI_tools/TI_CGT_C6000_5.1.13/. A README in the TI_tools directory also describes how to install alternate compiler versions and how to rebuild the support libraries, but, in general, the 5.1.13 installation is ready-to-use (no additional setup, no magic libraries, no zipfiles containing hard-coded directory structures). To compile the code:
  • Check out the source. No restrictions on the directory structure (except that you need to be able see the compiler)
  • cd into the RodDaq/Dsp directory
  • The Makefile should take care of everything for you. Just type make . Or just make master or make slave if that's all you need.
 

Flashing the Binaries

Now you have the binaries, they need to be flashed to the ROD crates.

Master DSP

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback