SVTVME status report 12 Dec 2000

• work program until March 1
• not all the work, will update
• need to keep time for other jobs as well
  • HitBuffer n.1
  • HB documentation (AMS as well ?)
  • upgrade/adapt/develop test code for HB + ...
  • all the stuff that is not in the list
  • scattered help on hw/sw
  • computing for italian analysis
  • security
  • ...

SVTVME 1: before 2001

• import local version in Trieste (Pisa ?)

• start to integrate lookup tables: AMS
  • generate ucode as a functions
  • function for AMS data-sink mode
  • store ucode version and parameters in the RAM itslef
    as few spurious states.
  • simple function to ena/disa hold and road-limit
• this kind of code is common to offline.
  • Where do we keep it ?
  • General issue for svt_config area.
  • ad hoc workshop with Bill,Giovanni,Alex ?

• better make procedure
  • separate Thomas' stuff
  • .a in place of .o
  • still .o for VxWorks ?
  • handle dependancies (avoid make clean) ?

SVTVME 2: january 2001

• documentation
  • usable web page by Jan 15
  • continous project afterwards

• complete access controls
  • error messages, verbosity level
  • protected/locked boards

• XTF
  • add XTF-A. Not trivial. longer then 64-bits words.
  • define send-data-out operation for XTF-A
  • add XTF-C (if any)

• flash RAM's (need function from UKY/BA/SC)
  • add methods if any (will slip as needed)

SVTVME 3: february 2001

• smooth code
  • better handle of some global variables
  • clean-up, simplify HF/TF calls
  • more macros, less lines
  • TF/HF has some different methods for cold start
  • integrate Bill's VME access by many words, blocks etc.
  • better define needed elementary steps, and improve usage of common low level step

• cpu boot
  • boot customisation by crate of initial values
  • need to put startup scripts out of cdf_svt
  • not my task (in principle)
  • nobody's task (in principle) like fixing b0svt07....