Hardware Documentation and Howto's: Difference between revisions
| Line 8: | Line 8: | ||
=== pRU === | === pRU === | ||
* [[:Media:Control Interface.pdf | pRU Control Interface]] | * [[:Media:Control Interface.pdf | pRU Control Interface]] [Deprecated, only in use on PTB. Replaced with IPBus on VCU118 + all other boards in the future.] | ||
* [[:Media:PRU Address Map.pdf | pRU Address Map]] | * [[:Media:PRU Address Map.pdf | pRU Address Map]] | ||
* [[:Media:PRU Ethernet Configurations.pdf | pRU Ethernet Configurations]] | * [[:Media:PRU Ethernet Configurations.pdf | pRU Ethernet Configurations]] | ||
Revision as of 12:23, 23 June 2020
Getting Started
Documentation
pRU
- pRU Control Interface [Deprecated, only in use on PTB. Replaced with IPBus on VCU118 + all other boards in the future.]
- pRU Address Map
- pRU Ethernet Configurations
- pCT Data Transfer Protocol
- pRU Data Format
- FPGA and ALPIDE radiation calculations
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))