Download presentation
Presentation is loading. Please wait.
Published bySabina Blair Modified over 8 years ago
1
ODE Workshop, LIP, 08/04/05 Irakli.MANDJAVIDZE@cea.fr SRP: Current Status Irakli MANDJAVIDZE DAPNIA, CEA Saclay, 91191 Gif-sur-Yvette, France
2
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/052 Overview Hardware Firmware Plans
3
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/053 Hardware Schematic capture in progress Already done → VME → JTAG → TTCrx & QPLL → Parallel optic modules To be done → Clock circuitry → Configuration Flash PROMs → TTS interface → External Memory → Ethernet and RS232 console → Power circuitry
4
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/054 Targeted AB Test-bed Debugging and testing of ABs with ABs TTC OUT TCC RX DCC T X AB RX AB TX sTTS IN sTTS OUT TTC IN AB under test DCC RX TCC TX AB RX AB TX sTTS IN sTTS OUT TTC IN AB tester TTC EX Attenuator TTC VI CC S B S 6 2 0 Control PC Linux HAL XDAQ DAQKit DCC emulator up to 6 chan. TCC emulator up to 12 chan.
5
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/055 Firmware Architecture System-on-chip design → Embedded PowerPC processor for control and monitoring → Facilitates debugging and testing → Currently standalone “C” application PPC 100 MHz On-chip memory Bridge Processor Local Bus: 50 MHz On-chip Peripheral Bus RS232 Console Slave Interface User Logic Ethernet Arbiter VME Application e.g. AB or AB Tester Local Bus
6
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/056 Firmware Debugging Firmware is tested on 3 Virtex-2 Pro development boards → TCS emulation : with 2VP7 device → AB Tester : with 2VP30 device 8 RocketIOs → AB: with 2VP50 device 8 RocketIOs TCS Emulator (2vp7) AB Tester (2VP30) AB (2VP50) N TCC and DCC links M AB links Flat ribbon cable for TCS signals
7
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/057 TCS Emulator Firmware Generates and distributes TTC signals → Clock40 → L1Accept → BGo commands Receives and combines sTTS signals → From AB and AB Tester Implements TCS state machine → As in CMS NOTE 2002/033 → Allows to start/stop run from console At any state changes fill a Spy buffer → Monitoring and debugging Signals follow closely TTCrx pin-out → AB and AB tester feel like getting data from TTCrx
8
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/058 TCS Emulator Screen Dump
9
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/059 AB Tester Firmware Sender module → Memory with pre-loaded data to be sent at L1 Accept TCC: TT classification flags AB: Frontier TT classification flags Receiver module → Memory with pre-loaded data to be received DCC: SR flags AB: Frontier TT classification flags → Memory to store erroneous events Wrong sender, event ID or data Parity or transmission error Communication channels → DCC/TCC: 80 MHz – 1.6 Gbit/s → AB: up to 100 MHz – 2.0 Gbit/s Variable number of TCC/DCC and AB/AB instances → Usually running with 4 DCC/TCC and with 4 AB/AB
10
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0510 AB Tester Firmware (cont.) TCS module → Receives 40 MHz TTC Clock → Receives and interprets BGo commands → Receives and buffers L1 Accepts → Transmits sTTS signals AB Tester State Machine → L1_Enb, L1_Wait, Arm_Time_Out, Wait_for_data, Disarm_Time_Out, Error Run Control State Machine → On, Init, Idle, Running, Out_of_Sync, Error Spy Memory → At any STATUS register changes VME interface: to be done Same firmware to test barrel and endcap ABs
11
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0511 AB Tester Screen Dump General status and TTC module statistics
12
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0512 AB Tester Screen Dump Sender and Receiver module statistics Communication channels statistics (Forced) data content errors
13
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0513 AB Tester Screen Dump Spy memory
14
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0514 Algorithm Board Firmware Under development Shares many modules with AB Tester → TCS → Run Control state machine → Clock management → Communication channels → VME Interface → SoC Modules developed for the system R&D work to be reused → e.g. Multi-port memory Two types of firmware → for barrel AB → for endcap AB
15
Irakli.MANDJAVIDZE@cea.frODE Workshop, LIP, 08/04/0515 Plans Two AB prototypes in September Standalone debugging and testing until December System-wide tests starting from 2006 Production, installation, integration, commissioning in 2006 → At least for barrel
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.