Hardware Documentation and Howto's: Difference between revisions
From pCT
No edit summary |
mNo edit summary |
||
Line 81: | Line 81: | ||
* [[:Media:mTower_schematic.pdf | mTower Schematic]] | * [[:Media:mTower_schematic.pdf | mTower Schematic]] | ||
=== Cooling Laboratory Setup === | |||
LAUDA Ultracool UC 4 is used for water cooling in the laboratory now ([https://www.lauda.de/pim/datasheet/LAUDA_UC4_E6004411_en_20211220_135424.pdf data sheet] and [https://cdn.accentuate.io/6800432890013/1624628180288/DMI-0210-01_UC_2-4__EN_.pdf?v=0 manual]). |
Revision as of 13:33, 10 January 2022
Main Page -> Hardware Documentation and Howto's
Getting Started
Documentation
pRU
- pRU Clock Network
- pRU Address Map
- DCS and Data Offload Ethernet Configurations
- pCT Data Transfer Protocol
- pRU Data Format
- FPGA and ALPIDE radiation calculations
- pRU Control Interface [Deprecated, only in use on PTB. Replaced with IPBus on VCU118 + all other boards in the future.]
pRU Registers and Bus System
The pRU bus system is connecting the various modules on the FPGA to a common master, the Microblaze Subsystem. Each of the modules is associated with a given BASE-ADDRESS specified in the pRU Control Interface Document. Note that several instances do exist for certain modules. E.g. there are one alpide_data instance for each ALPIDE chip connected to the pRU. To communicate with a specific instance one needs to add an offset of 0x1000 times the instance number to the module base address.
E.g. if you want to communicate with the
- 1st instance: <ALPIDE_DATA_BASEADDR>
- 2nd instance: <ALPIDE_DATA_BASEADDR> + (0x1000 * (2-1))
- 16th instance: <ALPIDE_DATA_BASEADDR> + (0x1000 * (16-1))
Module Registers
PTB-specific Module Registers
Transition Card (TC)
ALPIDE Chip
ALPIDE Bonding and Mounting
Chip Cable
9 Chip String
Production Test Box (PTB)
FPGA Mezzanine Card (FMC)
mTower
Cooling Laboratory Setup
LAUDA Ultracool UC 4 is used for water cooling in the laboratory now (data sheet and manual).