Status of GbE Peripheral Crate Controller

Slides:



Advertisements
Similar presentations
(Systems Analysis INTerface Board)
Advertisements

PROGRAMMABLE PERIPHERAL INTERFACE -8255
PC To GT Program Load Shachar Rosenberg Alex Normatov Technion - Digital Lab.
1 MICE Tracker Readout Update, Preparation for Cosmic Ray Tests Introduction/Overview AFE-IIt firmware development VLSB firmware development Hardware progress.
DMX512 Programmable Theater Lighting Controller Jeff Sand and Kris Kopel Advisor: Dr. Don Schertz May 8, 2001.
OUTLINE WHAT ? HOW ? WHY ? BLUEPOST Poster and Message Content Specified by the User Displaying the Poster Content on a Monitor Sending Messages to.
A Framework for Patient Monitoring A. L. Praveen Aroul, William Walker, Dinesh Bhatia Department of Electrical Engineering University of Texas at Dallas.
WANs and Routers Routers. Router Description Specialized computer Like a general purpose PC, a router has:  CPU  Memory  System Bus Connecting Internal.
Operating Systems.
Hardware Overview Net+ARM – Well Suited for Embedded Ethernet
Khaled A. Al-Utaibi  Intel Peripheral Controller Chips  Basic Description of the 8255  Pin Configuration of the 8255  Block Diagram.
3/11/2002CSE Input/Output Input/Output Control Datapath Memory Processor Input Output Memory Input Output Network Control Datapath Processor.
Remote Control of a Furby Toy with Bluetooth
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.
I NTRODUCTION P IN CONFIGARATION O PERATING MODE.
1-1 Embedded Network Interface (ENI) API Concepts Shared RAM vs. FIFO modes ENI API’s.
Top Level View of Computer Function and Interconnection.
Done By: Amnon Balanov & Yosef Solomon Supervisor: Boaz Mizrachi Project ID: d02310.
Instrumentation DepartmentCCLRC Rutherford Appleton Laboratory28 March 2003 FED Project Plan 2003 FED Project aiming to satisfy 2 demands/timescales: Module.
1 Presented By: Eyal Enav and Tal Rath Eyal Enav and Tal Rath Supervisor: Mike Sumszyk Mike Sumszyk.
Embedded Network Interface (ENI). What is ENI? Embedded Network Interface Originally called DPO (Digital Product Option) card Printer without network.
Author George Peck EVLA Hardware Monitor & Control PDR March 13, MIB FUNCTIONALITY.
US Status of GbE Peripheral Crate Controller Ben Bylsma EMU meeting Fermilab, October 21, 2005 Section 1: Hardware Section 2: Firmware Development.
Stan Durkin EMU Meeting, Purdue Univ. Oct. 6, VCC Hardware Production Status Firmware compile issues delayed testing and burn-in. Last 15 boards.
June 17th, 2002Gustaaf Brooijmans - All Experimenter's Meeting 1 DØ DAQ Status June 17th, 2002 S. Snyder (BNL), D. Chapin, M. Clements, D. Cutts, S. Mattingly.
NS Training Hardware Traffic Flow Note: Traffic direction in the 1284 is classified as either forward or reverse. The forward direction is.
Source Controller software Ianos Schmidt The University of Iowa.
Proposal for an Open Source Flash Failure Analysis Platform (FLAP) By Michael Tomer, Cory Shirts, SzeHsiang Harper, Jake Johns
Input/Output Problems Wide variety of peripherals —Delivering different amounts of data —At different speeds —In different formats All slower than CPU.
DAQMB Status – Onward to Production! S. Durkin, J. Gu, B. Bylsma, J. Gilmore,T.Y. Ling DAQ Motherboard (DMB) Initiates FE digitization and readout Receives.
JRA-1 Meeting, Jan 25th 2007 A. Cotta Ramusino, INFN Ferrara 1 EUDRB: A VME-64x based DAQ card for MAPS sensors. STATUS REPORT.
US Peripheral Crate VMEbus Controller Ben Bylsma EMU – ESR CERN, November 2003.
S. Durkin, CMS EMU Meeting U.C. Davis Feb. 25, DMB Production 8-layer PC Board, 2 Ball-Grid Array FPGA’s, 718 Components/Board 550 Production Boards.
October Test Beam DAQ. Framework sketch Only DAQs subprograms works during spills Each subprogram produces an output each spill Each dependant subprogram.
بسم الله الرحمن الرحيم MEMORY AND I/O.
1 Programming of FPGA in LiCAS ADC for Continuous Data Readout Week 6 Report Wednesday 6 th August 2008 Jack Hickish.
FW and HW Status TDAQ WG 10/6/2015. Hardware MPOD: ◦ HV was NOT floating   Sensibility of current limit to external devices  Particularly for chamber.
XTRP Software Nathan Eddy University of Illinois 2/24/00.
4000 Imaje 4020 – Software Imaje 4020 – Content ■ Content of Chapter Software: 1. Flash Up 2. Netcenter 3. FTP 4. Active X 5. XCL commands 6. Exercise.
Demo system of Belle2link Sun Dehui, Zhao Jingzhou,Liu zhen’an Trigger Lab IHEP.
Eric Hazen1 Ethernet Readout With: E. Kearns, J. Raaf, S.X. Wu, others... Eric Hazen Boston University.
Firmware development for the AM Board
ATLAS Pre-Production ROD Status SCT Version
SMS module HDL-MGSM.431.
Initial check-out of Pulsar prototypes
USB The topics covered, in order, are USB background
Instructor Materials Chapter 5: Ethernet
Production Firmware - status Components TOTFED - status
UNIT – Microcontroller.
Diagram of microprocessor interface with IO devices
Serial Communications
CS 286 Computer Organization and Architecture
Introduction to Computers
PCI BASED READ-OUT RECEIVER CARD IN THE ALICE DAQ SYSTEM
CSCI 315 Operating Systems Design
New Crate Controller Development
8-layer PC Board, 2 Ball-Grid Array FPGA’s, 718 Components/Board
AT91RM9200 Boot strategies This training module describes the boot strategies on the AT91RM9200 including the internal Boot ROM and the U-Boot program.
8-layer PC Board, 2 Ball-Grid Array FPGA’s, 718 Components/Board
Parallel communication interface 8255
2 Ball-Grid Array FPGA’s
VCC Hardware Production Status
LHCb Online Meeting November 15th, 2000
Module 3 Configuring a Router.
Chapter 13: I/O Systems.
The Programmable Peripheral Interface (8255A)
FED Design and EMU-to-DAQ Test
NS Training Hardware.
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:

Status of GbE Peripheral Crate Controller Ben Bylsma EMU meeting Fermilab, October 29, 2004

Hardware Status Nov. 6, 2003 (ESR) Hardware Development Oct. 29, 2004 Non-Restrictive board design. Sent to PC house last week. Most parts are on hand. Board Stuffing to take place next week. Oct. 29, 2004 2 stuffed boards (p4, & p7) Testing hardware as firmware is developed. Only minor problems found that will be corrected on the next version. Hardware Development Non-Restrictive board design. Even though we may not utilize or implement some VME64x capabilities, the board is designed to be compatible with almost all VME64x functionality. Sent to PC house last week. Most parts are on hand. Board Stuffing to take place next week. Firmware Development Will be developed in stages. RocketIOTM implementation has been previously tried and tested. Start with rudimentary A24 D16 VME master. This means unpacking GbE, buffering to the FIFO, transfer from FIFO to VME port, conform to timing requirements, fill a buffer with any read data, create packet, and send to GbE. Add other functionality, flexibility, configuration control, and robustness as progress is made. This includes other transfer modes, define command structure or custom protocol structure for local and VME commands, add mechanism for setting and saving particular configurations, saving a default configuration, develop handshaking to deal with reset or full buffers, add status and monitoring and error reporting, add modules for system timer, arbiter, interrupt handler, etc. B. Bylsma EMU Meeting, Fermilab Oct. 29, 2004

Firmware Status Nov. 6, 2003 (ESR) Firmware Development Oct. 29, 2004 Will be developed in stages. RocketIOTM implementation has been previously tried and tested. Start with rudimentary A24 D16 VME master. Add other functionality, flexibility, configuration control, and robustness as progress is made. Oct. 29, 2004 GbE: Written and tested but not polished. Ext. FIFO: Written and tested and possibly final version VME: Mostly written but untested. Flash RAM: Unwritten. Hardware Development Non-Restrictive board design. Even though we may not utilize or implement some VME64x capabilities, the board is designed to be compatible with almost all VME64x functionality. Sent to PC house last week. Most parts are on hand. Board Stuffing to take place next week. Firmware Development Will be developed in stages. RocketIOTM implementation has been previously tried and tested. Start with rudimentary A24 D16 VME master. This means unpacking GbE, buffering to the FIFO, transfer from FIFO to VME port, conform to timing requirements, fill a buffer with any read data, create packet, and send to GbE. Add other functionality, flexibility, configuration control, and robustness as progress is made. This includes other transfer modes, define command structure or custom protocol structure for local and VME commands, add mechanism for setting and saving particular configurations, saving a default configuration, develop handshaking to deal with reset or full buffers, add status and monitoring and error reporting, add modules for system timer, arbiter, interrupt handler, etc. B. Bylsma EMU Meeting, Fermilab Oct. 29, 2004

Firmware Development Gigabit Ethernet Interface: Fifo interface: Written and extensively tested. Have transferred billions of bytes of data and millions of packets error free using random size jumbo packets. Rate is limited by the server/driver. Had to throttle back the packet sending. But short burst of smaller packets work fine. Handling of MAC addresses is working fine, but currently it’s own MAC address is “hard-wired”. Fifo interface: Current functionality gives control for all potential uses of the FIFO. Probably is the final version. B. Bylsma EMU Meeting, Fermilab Oct. 29, 2004

Firmware Development VME Interface: Has 13 sub-modules (2 are upper level sub-modules). The low level modules enforce all the VME timing rules. Either written or not currently necessary. Close to final version. Upper level sub-modules are written but not supporting all features yet. Flash Memory Interface (Storing configurations): Have not started yet. B. Bylsma EMU Meeting, Fermilab Oct. 29, 2004