SVTVME status report 30 Jan 2001
from last time (12/12/00) SVTVME 1: before 2001
Green = Done Red = NOT Done
- import local version in Trieste (Pisa ?)
- start to integrate lookup tables: AMS
- generate ucode as a functions
- store ucode version and parameters in the RAM
itself as few spurious states.
- function for AMS data-sink mode
NOT YET
- simple function to ena/disa hold and road-limit
NOT YET
- need functions to retrieve uCode version #
and parameters from Ram
Know how to do it. Need few hours of coding
this kind of code is common to offline.
- Where do we keep it ? ==> SVTVME
- General issue for svt_config area.
==> NO. uSEQ code is svtvme specific
- ad hoc workshop with Bill,Giovanni,Alex ?
==> SENT MAIL
- better make procedure ==> ALL TO DO
- separate Thomas' stuff
- .a in place of .o
- still .o for VxWorks ?
- handle dependancies (avoid make clean) ?
Present issues:
- cold start only works at B0
- AMS's are at Fermilab
- very slow to work there from here
- ==> just be patient
- need to enucleate common functions from Bill's smart cold start
to access checksums.
- --> also usefull (I think) for new cold start by Alex B.
- --> would like to increase priority for getting Bill's smart
cold start into "standard" framework.
- WHY HARDWIRED VME ADDRESSES IN PRESENT CODE ?
Any reasons why I should not remove them ?
Stefano Belforte
Last modified: Tue Jan 30 14:42:50 MET