Hardware Documentation and Howto's: Difference between revisions
No edit summary |
No edit summary |
||
Line 63: | Line 63: | ||
* [[:Media:2019_11_05.zip | 2019 November 5 ]] | * [[:Media:2019_11_05.zip | 2019 November 5 ]] | ||
=== Production Test Box (PTB) === | |||
* [[:Media:PTB-v1.0_schematic.pdf | PTB-v1.0 Schematic]] | |||
=== FPGA Mezzanine Card (FMC) === | |||
* [[:Media:FMC-v1.0_schematic.pdf | FMC-v1.0 Schematic]] | |||
=== mTower === | === mTower === | ||
* [[:Media:mTower_schematic.pdf | mTower Schematic]] | * [[:Media:mTower_schematic.pdf | mTower Schematic]] |
Revision as of 10:59, 12 January 2020
Getting Started
Documentation
pRU
- pRU Control Interface
- pRU Address Map
- pRU Ethernet Configurations
- pCT Data Transfer Protocol
- pRU Data Format
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))