FNAL STT Meeting  H.Evans 8/9/99 Communication & Control H.EvansColumbia U. Overview of FRC Functions:  Road Info STCs,TFCs –Device Independent Data.

Slides:



Advertisements
Similar presentations
IO Interfaces and Bus Standards. Interface circuits Consists of the cktry required to connect an i/o device to a computer. On one side we have data bus.
Advertisements

System Integration and Performance
INPUT-OUTPUT ORGANIZATION
11-1 ECE 424 Design of Microprocessor-Based Systems Haibo Wang ECE Department Southern Illinois University Carbondale, IL I/O System Design.
Smart Card Reader. Quick Start Training Agenda Smart Card Introduction ISO 7816 Standard Smart Card Operation CoolRunner-II Smart Card Reader CoolRunner-II.
Arctic IEC-104 Gateway Jari Lahti, CTO.
CS-334: Computer Architecture
Michigan State University 6/28/ L2 I/O Transfer James T. Linnemann Michigan State University Trigger Meeting February 20, 1998.
Chapter 7 Input/Output. Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats.
Group 7 Jhonathan Briceño Reginal Etienne Christian Kruger Felix Martinez Dane Minott Immer S Rivera Ander Sahonero.
Copyright ©: Nahrstedt, Angrave, Abdelzaher
INPUT-OUTPUT ORGANIZATION
INPUT/OUTPUT ARCHITECTURE By Truc Truong. Input Devices Keyboard Keyboard Mouse Mouse Scanner Scanner CD-Rom CD-Rom Game Controller Game Controller.
Computer Architecture Lecture 08 Fasih ur Rehman.
The University of New Hampshire InterOperability Laboratory Serial ATA (SATA) Protocol Chapter 10 – Transport Layer.
Input / Output CS 537 – Introduction to Operating Systems.
The computer system’s I/O architecture is its interface to the outside world. This architecture provides a systematic means of controlling interaction.
Chapter 7 Input/Output Luisa Botero Santiago Del Portillo Ivan Vega.
LSU 10/22/2004Serial I/O1 Programming Unit, Lecture 5.
Chapter 10: Input / Output Devices Dr Mohamed Menacer Taibah University
Input/OUTPUT [I/O Module structure].
XTRP Hardware Mike Kasten University of Illinois 2/24/00.
COMPUTER ORGANIZATIONS CSNB123 NSMS2013 Ver.1Systems and Networking1.
Computer Architecture Lecture10: Input/output devices Piotr Bilski.
CS 342 – Operating Systems Spring 2003 © Ibrahim Korpeoglu Bilkent University1 Input/Output CS 342 – Operating Systems Ibrahim Korpeoglu Bilkent University.
 8251A is a USART (Universal Synchronous Asynchronous Receiver Transmitter) for serial data communication.  Programmable peripheral designed for synchronous.
Input/Output Computer component : Input/Output I/O Modules External Devices I/O Modules Function and Structure I/O Operation Techniques I/O Channels and.
First ideas for the Argontube electronics Shaper, simulations Block Diagram for analog path Delta Code Data Reduction Bus system, Controller Max.
L/O/G/O Input Output Chapter 4 CS.216 Computer Architecture and Organization.
Nevis FVTX Update Dave Winter FVTX Silicon Meeting 13 July 2006.
1 The PHENIX Muon Identifier Front End Electronics Andrew Glenn (University of Tennessee), for the PHENIX collaboration Andrew Glenn 5/1/01 April APS Meeting.
FPGA firmware of DC5 FEE. Outline List of issue Data loss issue Command error issue (DCM to FEM) Command lost issue (PC with USB connection to GANDALF)
The computer system’s I/O architecture is its interface to the outside world. This architecture provides a systematic means of controlling interaction.
L3 DAQ Doug Chapin for the L3DAQ group DAQShifters Meeting 10 Sep 2002 Overview of L3 DAQ uMon l3xqt l3xmon.
System-On-a-Programmable-Chip (SOPC) Implementation of the Silicon Track Card (STC) Thesis Defense By Arvindh-kumar Lalam Department of Electrical and.
PROGRAMMABLE PERIPHERAL INTERFACE -8255
Protocol Layering Chapter 11.
Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower than CPU.
IT3002 Computer Architecture
L2 Silicon Track Trigger D0 Trigger Workshop 22 April 2002 Ulrich Heintz Boston University.
11 th April 2003L1 DCT Upgrade FDR – TSF SessionMarc Kelly University Of Bristol On behalf of the TSF team Firmware and Testing on the TSF Upgrade Marc.
STT In-Crate CPU Bill Lee 28 April STT In-Crate CPU -- Bill Lee2 CPU Motorola Power PC Running VxWorks 5.3d EPICS Does not communicate with TCC.
1 Device Controller I/O units typically consist of A mechanical component: the device itself An electronic component: the device controller or adapter.
20 April 2002Bill Lee APS 1 The D0 Silicon Track Trigger Bill Lee Florida State University.
WINLAB Open Cognitive Radio Platform Architecture v1.0 WINLAB – Rutgers University Date : July 27th 2009 Authors : Prasanthi Maddala,
Calliope-Louisa Sotiropoulou FTK: E RROR D ETECTION AND M ONITORING Aristotle University of Thessaloniki FTK WORKSHOP, ALEXANDROUPOLI: 10/03/2014.
Grzegorz Kasprowicz1 Level 1 trigger sorter implemented in hardware.
Firmware development for the AM Board
IAPP - FTK workshop – Pisa march, 2013
Department of Computer Science and Engineering
PROGRAMMABLE PERIPHERAL INTERFACE -8255
Chapter 13: I/O Systems Modified by Dr. Neerja Mhaskar for CS 3SH3.
OLD LOGIC AMBSlim5.
* Initialization (power-up, run)
Presented By: Navneet Kaur Randhawa Lect. I.T. Deptt. GPC,Amritsar
Operating Systems (CS 340 D)
1 Input-Output Organization Computer Organization Computer Architectures Lab Peripheral Devices Input-Output Interface Asynchronous Data Transfer Modes.
PROGRAMMABLE PERIPHERAL INTERFACE -8255
Computer System Overview
L1FW: towers, tracks, correlations
Communication & Control
Created by Vivi Sahfitri
Idle Setup Run Startup Process Wait Event Event Wait Answer Send
Multi Chip Module (MCM) The ALICE Silicon Pixel Detector (SPD)
Chapter 13: I/O Systems.
G. Steinbrück STT meeting
Chapter 13: I/O Systems “The two main jobs of a computer are I/O and [CPU] processing. In many cases, the main job is I/O, and the [CPU] processing is.
Presentation transcript:

FNAL STT Meeting  H.Evans 8/9/99 Communication & Control H.EvansColumbia U. Overview of FRC Functions:  Road Info STCs,TFCs –Device Independent Data Format  SCL STCs,TFCs,ZVC(c.f. MBT) –L1 Info: to other boards –L2 Info: to Buffer Control –SCL Init  L3 Buffers All(c.f. VRB) –Define Standard L3 Buffer Unit –Buffer Protocol  Status/Mon. All –Init / Busy / Error –Monitoring Registers(c.f. MBT)

FNAL STT Meeting  H.Evans 8/9/99 Roads + L1-SCL Init / Busy / Error G-Link Conv (CFT) FRC (road) SCL Mezz FRC (scl) FRC (buff-ctrl) SMT Fiber G-Link Conv (SMT) STC (clus) STC (assoc) 16 evt TFC (fit) TFC (format) TFC (xmit) L3 STC Clus-Buff (r-phi) L3 STC Clus-Buff (z) ZVC L3 STC Assoc- Buff L3 TFC Fit-Buff L3 FRC Road-Buff 1 evt L1CTT SCL Hub L2CTT MBT L1 Info L1 / L2 Buffer Control FRC (cntrl) Status STC (cntrl) Status TFC (cntrl) Status 16 evt

FNAL STT Meeting  H.Evans 8/9/99 Road Data Format  Control Info Required with each word –Valid Data –End of Event –CLK  3 Extra Bits for each word transferred

FNAL STT Meeting  H.Evans 8/9/99 L1CTT Data Format See M.Martin:

FNAL STT Meeting  H.Evans 8/9/99 L1CTT Glossary (Abridged)  Header –P/NSome Trks w/ Pos/Neg Pt –No. PtxNo. of Trks in Pt Bin x  Data –SSign of Trk –Pt BinPt Bin Number (0-3) –Ext. PtBin-1 (1.5-3 GeV)A-Offset Bin-2 (3-5 GeV)A-Offset Bin-3 (5-10 GeV)Pt-Info Bin-4 (10- GeV)Pt-Info –H/LTrk assoc w/ Hi/Lo PS Clust –ErrTransmission Errors –RPS Clust assoc in adjacent sect –PSC RARel. Addr of PS Clust –Rel  H-Layer Fiber Number –IsIsolated Track –eIIsolated Electron –Trk AdrAddress of 4.5 o wedge of Trk

FNAL STT Meeting  H.Evans 8/9/99 Serial Command Link  Steal as much as possible from MBT –see MBT TDR (ver /24/99)  L1 Accept –L1_TURN, L1_BX, L1_QUAL sent to:  STCs, TFCs, ZVC(?) as 1st element of Road Data  FRC Buffer Control to request next Buffer  L2 Accept –L1_TURN, L1_BX, L3_TRAN_NO sent to:  FRC Buffer Control to initiate Buffer Transfer

FNAL STT Meeting  H.Evans 8/9/99 SCL (cont.)  SCL Init Sequence Command Implementation 1) FRCRec Init from Hubmezzanine 2) FRCSend Init to all CardUser pin 3) FRCINIT_ACK to Hubmezzanine 4) FRC Clear L1/L2_ERRORmezzanine 5) AllReceive Init from FRCUser pin 6) AllRaise Local BusyVME stat reg 7) AllStart Init Sequence wait until all Inputs are clear send Init Done signal 8) FRCPoll all Local Stat RegsVME orWait for local init_ack’sUser pin 9) FRC Clear INIT_ACKmezzanine  Have to be ready for SCL Init on any 132 ns SCL word !

FNAL STT Meeting  H.Evans 8/9/99 Buffers and Control  Steal from VRB / VRBC –see ESE-SVX (7/1/99) Possible System:  FRC(buff) acts as Buffer Manager for all L3 Buffer Units in system –sends same control signals to all Units  basically:Write to Buffer iL1 Acc Read from Buffer jL2 Acc –All buffer number management at FRC –control signals derived from L1/L2 SCL  decouples SCL from rest of system (aside from road data)  Use same L3 Buffer Unit on all cards –simplifies I/O –use L3 Buffer Unit on FRC ?  Control Protocol = a subset of VRBC

FNAL STT Meeting  H.Evans 8/9/99 L3 Buffer Unit Buffer (MPM)  Cmd/Addr Decode RW Status Format/Xmit Route & Count Data Source Buffer Controller Output FIFO 16 evtInput FIFO Route & Count VME VBD Enable/Reset/Busy/Error Addr Error FIFO full Data Message Data Count/Ovfl C/OData Pointer Count / Status Busy/Error

FNAL STT Meeting  H.Evans 8/9/99 VRB Buffer Protocol  Messages: –12+2(?) bit Field on Ext Ctrl Port –Bits11..8Type 7..0Value –Control1..0Valid,CLK

FNAL STT Meeting  H.Evans 8/9/99 Buffer Protocol (cont.)  Status –in VRB: open collector TTL on J5/6 –OR of all modules

FNAL STT Meeting  H.Evans 8/9/99 STT Control / Status  Fast StatusUser pins –Event-by-Event Comm. w/ Trigger –Lines to FRC are OR of all boards –SCL Init / Restartfrom FRC –Busy / Error / Init Ackto FRC –Each board must define  Actions for Init / Restart (w/in guidelines of SCL Init Sequence)  conditions for Busy / Error  MonitoringVME Regs –Steal from MBT (?) –Use Standard Monitoring Registers  same memory maps

FNAL STT Meeting  H.Evans 8/9/99 FRC To Do List (from BU) 4Check for Truncation Scheme Biases 4Define Road Info Data Format 6Decide Where Reformatting of L1CTT Info will be Done èDecide on Communications Medium 4Identify SCL Info Needed èDefine Data to L3 4Define Buffer Control Protocol èDefine Monitoring Data / Monitoring Control  Long List of Internal FRC Decisions… 6Done 4First Pass èStill Pending