AT-TPC Wiki

User Tools

Site Tools

Trace: • gmc_jitter • archive
cobo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
cobo [2013/12/09 12:21] – [Quick Start] abunimehcobo [2017/09/29 12:23] (current) – bazin
Line 1: Line 1:
 ===== Introduction ===== ===== Introduction =====
-CoBo: **Co**ncentration **Bo**ard for the GET (General electronics for TPC) electronics to reduce high data throughput of Time Projection Chamber detectors.+CoBo: **Co**ncentration **Bo**ard, is a custom printed circuit board (PCB), firmware, and embedded software for the GET (General Electronics for time projection chamber (TPC)) project. CoBo, intelligently, reads, reduces, and concentrates the high data throughput of TPC detectors.
  
 CoBo interfaces with three major components: CoBo interfaces with three major components:
-  - Asad (ASIC-ADC) board via 68-pin VHDCI cables. Asad hosts the AGET chip.+  - Asad (ASIC-ADC) board via 68-pin VHDCI cables. Asad hosts upto 4 AGET chips.
   - Mutant (MUltiplicity Trigger ANd Time) board via MicroTCA backplane: CLK2, CLK3, PORT1, and PORTS<8:11>.   - Mutant (MUltiplicity Trigger ANd Time) board via MicroTCA backplane: CLK2, CLK3, PORT1, and PORTS<8:11>.
   - Controller and storage farm via GbE connections.   - Controller and storage farm via GbE connections.
  
-CoBo is μTCA compatible. i.e. PICMG® AMC.0 R1.0. and is hosted in MicroTCA chassis (VadaTech [[http://www.vadatech.com/products/?show=product&product=195|VT893]]). The chassis is capable of hosting 11 CoBo cards. However, in AT-TPC we will only utilize 10 cards. Each CoBo card is connected to 4 Asad boards and each Asad board is connected to 256 (channels) sensors in the detector. Therefore, the entire system is capable of processing **10240** channels. +CoBo is μTCA compatible. i.e. PICMG® AMC.0 R1.0. and is hosted in MicroTCA chassis (VadaTech [[http://www.vadatech.com/products/?show=product&product=195|VT893]]). The chassis is capable of hosting 11 CoBo cards. In the AT-TPC project, we will only utilize 10 cards and a single MicroTCA chassis. Each CoBo card is connected to 4 Asad boards and each Asad board is connected to 256 (channels) sensors in the detector (MicroMegas). The entire AT-TPC system is capable of processing **10240** channels.
- +
- +
- +
  
 +TPC analog signals are passed to AGET chips (designed at CAE) where they are conditioned and compared, then they are converted to the digital domain using the ADCs (Analog-to-Digital-Convert) on the Asad board (designed at CENBG) and communicated to CoBo. Multiple CoBo board are orchestrated by the Mutant (Multiplicity and Trigger board designed at GANIL) via the MicroTCA backplane to concentrate and readout the data.
  
 +===== Purchasing CoBo =====
 +The design, hardware, firmware and/or software are copyright protected and are proprietary property of Michigan State University ©2013. (TEC2011-0083).
 +  * [[Purchasing CoBo]]
 +  * [[Pending Orders]]
 +===== List of CoBo Boards =====
 +[[cobo list|List]] of all fabricated CoBo boards to date.
  
 ===== Development Tiers ===== ===== Development Tiers =====
 {{ :tiers.png?160|CoBo Development Tiers}} {{ :tiers.png?160|CoBo Development Tiers}}
  
-CoBo hardware, firmware, and software is developed at NSCL. The generic embedded software for AGET chip is developed by IRFU (CEA) and is used on Mutant, CoBo, and PC farm.+CoBo hardware, firmware, and software is developed at NSCL. The generic embedded software for AGET chip is developed by IRFU (CEA) and is used on Mutant, CoBo, and PC farm. See [[daq_setup|DAQ Setup]] for details.
  
 Responsibilities: Responsibilities:
   * NSCL:   * NSCL:
   - Xilinx ML507 test platform and daughter board for CoBo (Nathan Usher)   - Xilinx ML507 test platform and daughter board for CoBo (Nathan Usher)
-  - [[CoBo PCB]] design, implementation, and testing (Faisal T. Abu-Nimeh) +  - [[cobo_pcb|CoBo Hardware]] design, implementation, and testing (Faisal T. Abu-Nimeh) 
-  - Firmware: +  - [[cobo_firmware|CoBo Firmware]]
-      * CoBo_Control and CoBo_Data IPs (Nathan Usher) +
-      * PLL IP (Faisal T. Abu-Nimeh) +
-      * [[System Architecture]] (CPU, Memory, Ethernet, etc) (Faisal T. Abu-Nimeh)+
   - [[Embedded Software]]: development and testing (Faisal T. Abu-Nimeh)   - [[Embedded Software]]: development and testing (Faisal T. Abu-Nimeh)
   - [[MicroTCA development]] (based on VT028) (Faisal T. Abu-Nimeh)   - [[MicroTCA development]] (based on VT028) (Faisal T. Abu-Nimeh)
Line 38: Line 38:
 A simplified depiction of the GET system is shown in the figure. A time project chamber hosting a 10240-pad MicroMega is connected to a smart protection board then fed to the AGET chips hosted on the Asad board. Every CoBo is then connected to 4 Asad boards using 4 dedicated VHDCI connectors on the front panel. The processed data is passed down to the Mutant as well as sent out using GbE to the storage farm. A simplified depiction of the GET system is shown in the figure. A time project chamber hosting a 10240-pad MicroMega is connected to a smart protection board then fed to the AGET chips hosted on the Asad board. Every CoBo is then connected to 4 Asad boards using 4 dedicated VHDCI connectors on the front panel. The processed data is passed down to the Mutant as well as sent out using GbE to the storage farm.
  
- +===== Reduced CoBo ===== 
-===== Quick Start ===== +The reduced CoBo is implemented on a Xilinx ML507 demonstration board. It can instrument one AsAd card only, via an adapter board designed by NSCL. The latest version of this adapter board (v2.0) connects to the AsAd versions 2.0 and above via a regular VHDCI cable. The firmware corresponding to this latest version can be found {{rcobo:download.pdf|here}}. Please use right-click to download the file from this link (otherwise your browser will try to open it as a PDF file), and change the extension of the file to .bit instead of .pdf after download. The .pdf extension is used because of restrictions on the wiki server.
-  - Locate an empty slot in the MicroTCA crate. +
-  - Remove any other AMC cards in the crate to make sure there is no conflicts on the backplane. +
-  - Make sure that the MCH (UTC002) is plugged in, and the Power Supply (UTC010) is plugged in. +
-  - Connect Xilinx USB JTAG to CoBo +
-  - Insert cobo to any slot you desire. +
-  - Switch on the crate. after a while a green LED should light up on CoBo in the upper right corner i.e. top. Since you are using a socket, Asad status LEDS might come on. you can ignore these for now. +
-  - If the board is ready, the LED on the JTAG connector should be green not amber. If it is amber then the cobo is not powered up. +
-  - Connect the MCH port GbE0 or GbE1 to your network. This has to be a local network. If you are using VadaTech the IP should be 192.168.40.xxx +
-  - You should have a DHCP server and a NFS server running in that subnet. See ([[Cobo_Fedora_Setup|Setup]]) and ([[CoBo_Ubuntu_Setup|Setup]]). +
-  *  +
-    - NFS should be exporting the embedded software that will run on CoBo-VxWorks. e.g. [[https://project-get.cea.fr/Groups/100_todolist/400_wp4_data_acquisi/reduced_cobo_4_aget2878/block_13777674301754/file|getHwServer-release-20130829.out]] +
-    - in ''/mnt/local/export/filesystem'' create a file called ''startup.vxsh'' and insert the getHwServer out file in it e.g. <code>ld < getHwServer-release-20130829.out</code> +
-  - Look at at {{:cobo_fp.pptx|:cobo_fp.pptx}}, you must short L2 and L3 LEMO connectors. This will not be needed in the future. The FPGA sends a sync plus to PLL to allow it to start. +
-  -  L0 connector should be connected to an oscilloscope. +
-  -  Connect a mini-usb cable from your workstation to cobo. on windows you will need a driver. I didn't need one for ubuntu 12.04 nor fedora 19. The driver can be installed from silicon labs the chip is cp21xx, open a terminal using putty or screen with the same settigns you use for ML507 cobo. i.e. 115200 +
-  - On your workstation start xmd. Take a look at [[xmd|XMD setup]] for Linux xmd setup info. +
-  - Once you are in xmd flash the FPGA by typing ''fpga -f system.bit'' +
-  - If the FPGA is flashed successfully a blue LED should light up. this is inside the crate not on the front panel. The led is located above the fpga. <code> +
-$ xmd +
-Xilinx Microprocessor Debugger (XMD) Engine Xilinx EDK 14.5 Build EDK_P.58f Copyright (c) 1995-2012 Xilinx, Inc.  All rights reserved. +
- +
-XMD% +
- +
-JTAG chain configuration +
--------------------------------------------------- +
-Device   ID Code        IR Length    Part Name +
- 1       232d8093          14        XC5VFX100T +
-ERROR: PowerPC405 Version UNKNOWN. The PowerPC405 Config String is NOT Valid +
-                : 0xffffffff +
- +
-XMD% fpga -f system.bit +
-Programming Bitstream -- system.bit +
-Fpga Programming Progress ......10....20....30....40....50....60....70....80....90.....Done +
-Successfully downloaded bit file. +
- +
-JTAG chain configuration +
--------------------------------------------------- +
-Device   ID Code        IR Length    Part Name +
- 1       232d8093          14        XC5VFX100T +
- +
-0 +
-XMD% connect ppc hw +
- +
-JTAG chain configuration +
--------------------------------------------------- +
-Device   ID Code        IR Length    Part Name +
- 1       232d8093          14        XC5VFX100T +
- +
-PowerPC440 Processor Configuration +
-------------------------------------- +
-Version.............................0x7ff21912 +
-User ID.............................0x00f00002 +
-No of PC Breakpoints................4 +
-No of Addr/Data Watchpoints.........2 +
-User Defined Address Map to access Special PowerPC Features using XMD: +
-                I-Cache (Data)........0x70000000 - 0x70007fff +
-                I-Cache (TAG).........0x70008000 - 0x7000ffff +
-                D-Cache               (Data)........0x78000000 - 0x78007fff +
-                D-Cache               (TAG).........0x78008000 - 0x7800ffff +
-                DCR...................0x78020000 - 0x78020fff +
-                TLB...................0x70020000 - 0x70023fff +
- +
-Connected to "ppc" target. id = 32 +
-Starting GDB server for "ppc" target (id = 32) at TCP port no 1234 XMD% +
-</code> +
-  - to run cobo in standalone mode you need to start the clocks. go to xmd and type ''dow coboTest.elf'' +
-  - now type ''run'' +
-  -  cobotest should run on CoBo. Look at putty or screen. You should see a menu. press 5 to load default PLL settings. +
-  - on the oscilliscpe connected to L0 you should see a dirty 100Mhz clock. This is normal. If you don't see a clock then the fpga is not flashed. +
-  - on xmd type ''stop'' +
-  -  now you can download vxworks by typing (in xmd) the following ''dow vx4.elf'' +
-  -  now type ''run'' +
-  - vxworks should load on the console and get an IP thru the MCH thru your DHCP server. +
- +
-===== Quick Test ===== +
-  - Turn on MicroTCA crate +
-  - open USB-Serial terminal e.g. putty +
-  - load FW thru xmd ''fpga -f system.bit'' +
-  - load PLL config thru xmd ''dow coboTest.elf'' then ''run'' +
-  - in usb-serial terminal choose option 5 to load PLL options. take a look at oscilloscope, You should see a clock. +
-  - stop cpu thru xmd ''stop'' +
-  - load vxworks image thru xmd ''dow vx4.elf'' then ''run'' +
-  - take a loko at usb-serial terminal, CoBo should get an IP. Start using GetController+
cobo.1386609706.txt.gz · Last modified: 2013/12/09 12:21 by abunimeh