Version 36 (modified by 9 years ago) (diff) | ,
---|
Repositories
Tests
Revisions
Date | Machine | OS | Firmware | pcitool | ipecamera | ufodecode | uca-ufo | PyTango | Concert | = Tests = |
---|---|---|---|---|---|---|---|---|---|---|
10/04/2015 | ipecamera4 | SuSE 13.1/3.11.10 | xxx | r244 | xxx | xxx | 7bf17ba | 8.1.6 | 0.11.0dev | 22.04.2015 |
02/03/2016 | ipecamera4 | SuSE 13.1/3.11.10 | 26/02/2016 by Uros | 01/09/2015 r302 | 21/08/2015 r275 | f3c6e08fe4 | cc8f325 | xxx | xxx | #243 + #244 |
02/03/2016 | ipecamera4 | SuSE 13.1/3.11.10 | 26/02/2016 by Uros | 02/03/2016 r356 | 04/02/2016 r276 | f3c6e08fe4 | cc8f325 | xxx | xxx | #243 + #244 |
Beam Tests
Expected Performance
- 2MP-10b: 330 fps, 4MP-10b: 148 fps, 4MP-12b: 37 fps, 20MP-12b: 30 fps
Hardware & Software Requirements
- Hardware IODMA enabled in BIOS and in the kernel. Linux SWIOTLB does not guarantee 4K aligned addresses which are required by the current hardware.
- In BIOS, Intel VT-d or AMD-Vi (AMD IOMMU) virtualization technologies have to be enabled.
- The Linux support of Intel VT-d is enabled with "intel_iommu=on" kernel parameter (alternative is to build kernel with CONFIG_INTEL_IOMMU_DEFAULT_ON).
- To check if hardware IOMMU is used run
dmesg | grep -e IOMMU -e DMAR -e PCI-DMA
- Following output indicates enabled hardware IOMMU (good)
[ 0.000000] Intel-IOMMU: enabled [ 0.124951] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020df [ 0.125044] IOAPIC id 0 under DRHD base 0xfbffc000 IOMMU 0 [ 0.125045] IOAPIC id 2 under DRHD base 0xfbffc000 IOMMU 0 [ 0.836366] IOMMU 0 0xfbffc000: using Queued invalidation [ 0.836370] IOMMU: Setting RMRR: [ 0.836377] IOMMU: Setting identity map for device 0000:00:1d.0 [0x7ccd2000 - 0x7ccf6fff] [ 0.836387] IOMMU: Setting identity map for device 0000:00:1a.0 [0x7ccd2000 - 0x7ccf6fff] [ 0.836390] IOMMU: Prepare 0-16MiB unity mapping for LPC [ 0.836394] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff] [ 0.836400] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
- And the following output will be produced if software SWIOTLB is actually used (bad)
[ 1.169614] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.169618] Placing 64MB software IO TLB between ffff8800bb766000 - ffff8800bf766000 [ 1.169620] software IO TLB at phys 0xbb766000 - 0xbf766000
- Following output indicates enabled hardware IOMMU (good)
Software Documentation
Hardware Documentation
- KIT DMA3 git tree and documentation
- UFO Camera and HEB registers (update from 27.07.2015 by Lorenzo)
- UFO Camera: List of FPGA Registers and debug LEDs
- UFO Camera operation instructions, required timeouts, etc.
- Short description of UFO Camera data format
- New header format for UFO cameras (slides)
- git clone git@ufo.kit.edu:ufo-camera-manual
FPGA and Sensor Documentation
- CMOSIS CMV2000 Datasheet
- CMOSIS CMV20000 Datasheet
- Xilinx Virtex-6 ML605 Evaluation Kit
- Virtex-6 DMA Engine Reference Design
Licenses
Software
Attachments (12)
- CMV2000 v2.pdf (1.0 MB) - added by 13 years ago.
- ml605.pdf (9.0 MB) - added by 13 years ago.
- ug379.pdf (7.6 MB) - added by 13 years ago.
- Data Format UFO 5.pdf (619.7 KB) - added by 12 years ago.
- Control_reg.xlsx (33.2 KB) - added by 12 years ago.
- KIT_PN2002_V6_x8_Gen2_1_00_11262013.zip (3.5 MB) - added by 11 years ago.
- core_licenses_full.zip (1.5 KB) - added by 11 years ago.
- BANK_REG_UFO_HEB_DMA.xls (29.0 KB) - added by 10 years ago.
- BANK_REG_UFO_HEB_DMA.2.xls (34.0 KB) - added by 10 years ago.
- datasheet_CMV20000 v2 1.pdf (1.6 MB) - added by 10 years ago.
- WP4_20MPixel.pdf (1.1 MB) - added by 9 years ago.
- BANK_REG_UFO_HEB_DMA.3.xls (34.5 KB) - added by 9 years ago.
Download all attachments as: .zip