GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Instrument Configuration James Swain Stanford Linear.

Slides:



Advertisements
Similar presentations
What's inside a router? We have yet to consider the switching function of a router - the actual transfer of datagrams from a router's incoming links to.
Advertisements

GLAST LAT Project I&T Integration Kickoff Meeting 03/09/04 Online 1 GLAST Large Area Telescope: I&T Integration Kickoff Meeting EGSE Hardware March 9th,
Tower Electronics Module and Tower Power Supply EM Tower Electronics Module (TEM) before coating/staking TEM & TPS assembly Close to 60 TEM & TPS assemblies.
GLAST LAT ProjectI&T/Online Workshop October 29 to November 1, 2002 R. Claus1 EM1 EGSE Configuration VME/cPCI Chassis LAT-COMM Electronics/OnlineSubsystem/simulator.
1 Version 3 Module 8 Ethernet Switching. 2 Version 3 Ethernet Switching Ethernet is a shared media –One node can transmit data at a time More nodes increases.
GLAST LAT ProjectOnline Peer Review – July 21, Integration and Test J. Panetta 1 Gamma-ray Large Area Space Telescope GLAST Large Area Telescope:
GLAST LAT ProjectGLAST Flight Software IDT, October 16, 2001 JJRussell1 October 16, 2001 What’s Covered Activity –Monitoring FSW defines this as activity.
GLAST LAT Project Quarterly Review, Aug. 14, 2001 Gunther Haller1 GLAST Large Area Telescope: Electronics, DAQ & Flight Software Gunther Haller Stanford.
GLAST LAT Project4.1.7 July 17, 03 LAT Meeting G. Haller V41 GLAST Large Area Telescope: Electronics, Data Acquisition & Flight Software W.B.S LAT.
GLAST LAT Project28 March 2005 LAT System EngineeringLAT Test Planning Meeting GLAST LAT GLAST LAT System Engineering Gamma-ray Large Area Space Telescope.
ISOC Peer Review - March 2, 2004 Section GLAST Large Area Telescope ISOC Peer Review Test Bed Terry Schalk GLAST Flight Software
GLAST Large Area Telescope Engineering Meeting 23 November 2004 Charge Injection Calibration James Swain Stanford Linear Accelerator Center
GLAST LAT ProjectNovember 18, 2004 I&T Two Tower IRR 1 GLAST Large Area Telescope: Integration and Test One and Two Tower Integration Readiness Review.
GLAST LAT ProjectOnline Peer Review – July 21, Integration and Test L. Miller 1 GLAST Large Area Telescope: I&T Integration Readiness Review.
Copyright Arshi Khan1 System Programming Instructor Arshi Khan.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
GLAST LAT ProjectPDU/GASU MRR, February 3, DAQ & FSWV1 1 GLAST Large Area Telescope: B. Estey, G. Haller SLAC xxxx LAT Quality Engineer
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Telecommand and Telemetry Data Dictionary Services Sergio.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Network Architecture and Protocol Concepts. Network Architectures (1) The network provides one or more communication services to applications –A service.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR Current Status Sergio Maldonado FSW Test Team Lead Stanford Linear Accelerator Center.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
COMPUTER ORGANIZATIONS CSNB123 NSMS2013 Ver.1Systems and Networking1.
Interrupts and DMA CSCI The Role of the Operating System in Performing I/O Two main jobs of a computer are: –Processing –Performing I/O manage and.
1 Lecture 20: I/O n I/O hardware n I/O structure n communication with controllers n device interrupts n device drivers n streams.
CHAPTER 3 TOP LEVEL VIEW OF COMPUTER FUNCTION AND INTERCONNECTION
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Network Services Networking for Home and Small Businesses – Chapter 6.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 LAT Housekeeping Sergio Maldonado Stanford Linear Accelerator.
GLAST LAT ProjectIntegration and Test CDR Peer Review, March 28, 2003 Document: LAT-PR Section 6 - Page 1 GLAST Large Area Telescope: I & T Peer.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Primary Boot Code (PBC) D. Wood Naval Research Laboratory.
GLAST LAT ProjectDelta PDR/Baseline Review July 29-August 1, 2002 Section 7.3 AntiCoincidnce Detector Technical Status 1 GLAST Large Area Telescope: AntiCoincidence.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Diagnostics Framework James Swain Stanford Linear Accelerator.
GLAST LAT ProjectEGSE Peer Design Review, August 17, S. WilliamsEGSE Overview Electrical Ground Support Equipment Overview Scott Williams Stanford.
CE Operating Systems Lecture 3 Overview of OS functions and structure.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Software Watchdog Steve Mazzoni Stanford Linear Accelerator.
GLAST LAT ProjectDOE/NASA Peer Review, March 19-20, 2003 GLAST Large Area Telescope: Electronics, Data Acquisition & Instrument Flight Software Flight.
Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.
DAQ Development P. Roger Williamson Hansen Experimental Physics Laboratory Stanford University GLAST Collaboration Meeting GSFC February 10, 1999.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Thermal Control System Steve Mazzoni Stanford Linear.
L/O/G/O Input Output Chapter 4 CS.216 Computer Architecture and Organization.
1 Pertemuan 5 Networking Models. Discussion Topics Using layers to analyze problems in a flow of materials Using layers to describe data communication.
GLAST LAT ProjectI&T Face-to-Face Online Presentation – May 30, 2002 R. Claus1 I&T Online Status and Plans Ric Claus.
GLAST LAT Project LAT System Engineering 1 GLAST Large Area Telescope: LAT System Engineering Pat Hascall SLAC System Engineering Manager
GLAST Large Area Telescope LAT Flight Software System Checkout TRR Systems Engineering Mike DeKlotz GSFC Stanford Linear Accelerator Center Gamma-ray Large.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR Test Suites (Backup) Stanford Linear Accelerator Center Gamma-ray Large Area Space Telescope.
Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower than CPU.
Computer operation is of how the different parts of a computer system work together to perform a task.
GLAST LAT ProjectISOC CDR, 4 August 2004 Document: LAT-PR-04500Section 3.21 GLAST Large Area Telescope: Instrument Science Operations Center CDR Section.
GLAST LAT ProjectCDR/CD-3 Review May 12-16, 2003 Document: LAT-PR Section 5 IOC Subsystem 1 GLAST Large Area Telescope: IOC Subsystems WBS: 4.1.B.
1 Device Controller I/O units typically consist of A mechanical component: the device itself An electronic component: the device controller or adapter.
GLAST LAT ProjectFace to Face, 14 April 2004 LAT System Engineering 1 GLAST Large Area Telescope: EGSE and Interface Verification Pat Hascall SLAC System.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR FSW Overview Sergio Maldonado FSW Test Team Lead Stanford Linear Accelerator Center.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR Test Environment Sergio Maldonado FSW Test Team Lead Stanford Linear Accelerator Center.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Secondary Boot Code (SBC) D.Wood Naval Research Laboratory.
GLAST LAT ProjectDOE/NASA Peer Critical Design Review, March 19-20, 2003 D. Nelson 1 GLAST Large Area Telescope: Electronics, Data Acquisition & Instrument.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Instrument Configuration by File James Swain Stanford.
1 Chapter 1 Basic Structures Of Computers. Computer : Introduction A computer is an electronic machine,devised for performing calculations and controlling.
GLAST LAT ProjectSLAC Internal Review, April 16-18, 2002 LAT-PR Electronics and Flight Software WBS GLAST Large Area Telescope: Electronics,
GLAST Large Area Telescope:
Operating Systems (CS 340 D)
CS703 - Advanced Operating Systems
GLAST Large Area Telescope: I & T Peer Review EGSE/Online System
GLAST Large Area Telescope:
GLAST Large Area Telescope
GLAST Large Area Telescope:
Presentation transcript:

GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Instrument Configuration James Swain Stanford Linear Accelerator Center Gamma-ray Large Area Space Telescope

16 September 2004 Flight Unit Peer Review - Instrument Configuration 2 Instrument Configuration: Requirements Flight Software General Requirements: –Configuration of Subsystems ( ) Upon command, the SIU FSW shall configure the LAT power distribution subsystem and the CAL, TKR, ACD, and T&DF subsystems by writing to the T&DF-provided configuration registers. –Configuration by File ( ) Upon command, the SIU FSW shall configure the LAT power distribution subsystem and the CAL, TKR, ACD, and T&DF subsystems by writing to the T&DF-provided configuration registers specified in a configuration file that identifies the registers to be written and the corresponding value of the registers. –Readback of Subsystems ( ) Upon command, the SIU FSW shall read back and record the configuration of the LAT power distribution subsystem and the CAL, TKR, ACD, and T&DF subsystems by reading back the T&DF-provided configuration registers.

16 September 2004 Flight Unit Peer Review - Instrument Configuration 3 Instrument Configuration: Overview As one can see from the previous slide, the SRS describes instrument configuration in 2 ways: –As the configuration and readback of individual registers on LAT subsystems –As the configuration of large collections of registers using configuration files. Correspondingly, this presentation is divided into two pieces: –“Instrument Configuration”, which covers configuration of individual registers using the LEM package –“Instrument Configuration by File”, which addresses file- based configuration using LATC

16 September 2004 Flight Unit Peer Review - Instrument Configuration 4 Instrument Configuration: Functional Components Functional Inputs –FSW receives different inputs for its write and read operations: Write: –Addressing data that identifies registers of LAT subsystems (TKR, CAL, ACD, TEM, CRU, EBM, GEM, and PDU) –Data to write to the register Read: –Addressing data Functional Processing –FSW produces bit streams that are sent to the registers of subsystems on the LAT –FSW decodes responses received from registers of subsystems on the LAT –FSW validates responses by checking parity Functional Outputs –FSW outputs values read from registers on the LAT (TKR, CAL, ACD, TEM, AEM, CRU, EBM, GEM, and PDU) –FSW outputs I/O completion status and time stamps

16 September 2004 Flight Unit Peer Review - Instrument Configuration 5 Instrument Configuration: Overview Purpose –To place and maintain the instrument in a known configuration –To report the configuration Knowledge of instrument configuration is essential to a successful physics analysis The instrument appears to flight software as a collection of registers –A large collection Subsystem / BlockChip / Sub-blockNumber in InstrumentRegister CountRegister documentation TKRGTFE LAT-SS GTRC LAT-SS CALGCFE LAT-TD GCRC LAT-SS ACDGAFE LAT-SS GARC12528 TEMGTCC128768LAT-TD GCCC64448 GTIC16272 Common16112 GASUAEM1 (primary and redundant)6LAT-TD CRU1 (primary and redundant)4LAT-TD EBM1 (primary and redundant)31LAT-TD GEM1 (primary and redundant)59LAT-SS PDU7LAT-SS

16 September 2004 Flight Unit Peer Review - Instrument Configuration 6 Instrument Configuration: Communications Architecture Communications with registers on the CAL, TKR, ACD, T&DF and LAT power supply subsystems occur over a network fabric using the LATp communications protocol: –Certain nodes (SIUs) are commanders. Other nodes (EPUs, Tower Electronics Modules, ACD Electronics Modules, Global Triggers) are responders. GEM AEM CRU TEM 1 TEM 15 EBM PDU 0 PDU 1 SIU commander TEM 0 LAT Comm. Board

16 September 2004 Flight Unit Peer Review - Instrument Configuration 7 Instrument Configuration: Communications Architecture (cont’d) –The LATp protocol provides a type of communication packet called a command packet. Command packets are used to send read and write commands to registers on the LAT. –LATp command packets are 128 bits long. They are broken down into a header of 16 bits, followed by 112 node-specific bits. HeaderPayload parity (1) source address (6) protocol (2) destination address (6) response (1)

16 September 2004 Flight Unit Peer Review - Instrument Configuration 8 Instrument Configuration: Reaching the Registers –The registers in a LATp node (e.g., a TEM) are arranged in a hierarchy of function blocks (e.g., a TEM CAL cable controller), each block containing registers and possibly more function blocks. –To access the registers of a function block, one specifies the hierarchical path to the register.

16 September 2004 Flight Unit Peer Review - Instrument Configuration 9 Instrument Configuration: Reaching the Registers (cont’d) For instance, to write a register in the CAL front-end ASIC, one specifies the path through the hierarchy, indicating: –Which of the 16 TEMs (LATp nodes) to address –Which of the 4 GCCCs (TEM board ASICs) to address –Which of the 4 GCRCs (off-board CAL layer readout controller ASICs) to address –Which of the 12 GCFEs (off-board CAL front-end ASICs) to address –Which of the 7 registers on that GCFE to write to The next slide illustrates the packet structure used to write to a register on the CAL front-end ASIC.

16 September 2004 Flight Unit Peer Review - Instrument Configuration 10 Instrument Configuration: Reaching the Registers (cont’d) HeaderPayload type(2) broadcast(1) GCCC number(2) GCRC number(2) external(1) parity(1) fixed prefix(4) GCRC number(4) GCFE target(1) GCFE number(4) function(2) register(3) parity(1) data parity(1) register data(16) 0000 … 0

16 September 2004 Flight Unit Peer Review - Instrument Configuration 11 Instrument Configuration: Reaching the Registers (cont’d) The same messaging and addressing system is used to write and read registers on all subsystems. Subsystem / BlockChip / Sub-blockNumber in InstrumentRegister CountRegister documentation TKRGTFE LAT-SS GTRC LAT-SS CALGCFE LAT-TD GCRC LAT-SS ACDGAFE LAT-SS GARC12528 TEMGTCC128768LAT-TD GCCC64448 GTIC16272 Common16112 GASUAEM1 (primary and redundant)6LAT-TD CRU1 (primary and redundant)4LAT-TD EBM1 (primary and redundant)31LAT-TD GEM1 (primary and redundant)59LAT-SS PDU7LAT-SS

16 September 2004 Flight Unit Peer Review - Instrument Configuration 12 Instrument Configuration: Sending Multiple Commands To speed up configuration, multiple commands and responses can be bundled into DMA transfer operations between a flight CPU (e.g., an SIU) and the LAT Communications Board (LCB): –Multiple command items in a “command list” are DMA’d to the LCB. There the command items are sent one by one to LAT subsystems. The command list can be up to 4 KB long, enough space to hold 150 register write commands. –Multiple responses are assembled into a “results list.” All result items have a timestamp and a status word. For command items that expect a response, the result item also contains the data read back from the instrument subsystem. The results list can also be up to 4 KB long. –A one-to-one relationship between items on the command and results lists is maintained. –The results list is DMA’d back to the flight CPU, and LCB raises an interrupt to signal the transfer is complete.

16 September 2004 Flight Unit Peer Review - Instrument Configuration 13 Instrument Configuration: Sending Multiple Commands (cont’d) cmd rslt command list 1 PCI DMA from flight CPU to LCB result list 1 PCI DMA from LCB to flight CPU

16 September 2004 Flight Unit Peer Review - Instrument Configuration 14 Instrument Configuration: Software Implementation Communications via LATp and transmission of bit strings carrying register settings are handled by two FSW packages: –The LCBD package controls the LAT Communications Board (PCI register access) and handles LATp communications LCBD is covered in more detail by JJ Russell and Ed Bacho. –The LEM package constructs bit strings bound for registers on all LAT subsystems: CRU, EBM, GEM, PDU, ACD, CAL, & TKR, as well as the TEM and AEM

16 September 2004 Flight Unit Peer Review - Instrument Configuration 15 LEM Package Components lem –This constituent defines the structures of all the Command/Response LATp command items. The structures are joined together in a typedef'd union called LEM_ci and are public. This allows application developers to construct LATp commands by hand by setting the various bit fields. –Various macros are also defined that perform the bit packing and determine the various parity bits. –A functional interface, which is just a wrapper around the macros, is also provided. Developers are able to use whichever interface seems sensible. –The constituent also defines structures describing the various responses to a read command along with functions to break apart result item payloads into more user-friendly forms. –This constituent is complete and tested. cli –This constituent provides the command line interface allowing interaction with the LAT from the VxWorks command line. Functions in this constituent break up the payload (if necessary) and copy it into user supplied memory locations. bci –This constituent is a wrapper around the command line interface intended to provide run-time and compile time backwards compatibility for preexisiting software that is required for testing. It will be used temporarily to give developers breathing space as hardware is upgraded.

16 September 2004 Flight Unit Peer Review - Instrument Configuration 16 LEM Software Package Organization Shareables (flight) –liblem – main LEM library Shareables (testing and ground support) –liblem_cli – command-line interface libraries –liblem_bci – interface libraries (for backwards compatibility) –libt_lem – LEM unit test library LEM directly uses the following packages/constituents: –CMXCMX –LCBDLCBD –MSGMSG The dependency tree, constituent list, command and telemetry list, and other configuration management information related to LSW are published dynamically on the FSW Web site at