= Tests =
== Revisions ==
||= Date     =||= Machine  =||= OS =||= Firmware =||= pcitool =||= ipecamera =||= ufodecode =||= libuca =||= !PyTango =||= Concert =|| = Tests = ||
|| 10/04/2015 || ipecamera4 || SuSE 13.1/3.11.10 ||  xxx       || [source:/test/pcitool@pcitool,244 r244] || xxx || xxx || [https://github.com/ufo-kit/libuca/commit/7bf17ba4d76b07680a19c1a44fe9c0be5b736dd8 7bf17ba] || 8.1.6 || 0.11.0dev || [wiki:UfoCameraTest150422 22.04.2015] ||

== Beam Tests ==
 * [wiki:test_beam Test Beam at November 2011]

== 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
}}}

= UFO Documentation =
 * [raw-attachment:BANK_REG_UFO_HEB_DMA.2.xls UFO Camera and HEB registers] (update from 27.07.2015 by Lorenzo) 
 * [wiki:camera_fpga_registers UFO Camera: List of FPGA Registers and debug LEDs ]
 * [wiki:UfoCameraOperation UFO Camera operation instructions, required timeouts, etc. ]
 * [wiki:UfoCameraDataFormat Short description of UFO Camera data format ]
 * [raw-attachment:WP4_20MPixel.pdf New header format for UFO cameras (slides)]
 * git clone !git@ufo.kit.edu:ufo-camera-manual

= FPGA and Sensor Documentation = 
 * [raw-attachment:"CMV2000 v2.pdf" CMOSIS CMV2000 Datasheet]
 * [raw-attachment:"datasheet_CMV20000 v2 1.pdf" CMOSIS CMV20000 Datasheet]
 * [raw-attachment:ml605.pdf Xilinx Virtex-6 ML605 Evaluation Kit]
 * [raw-attachment:ug379.pdf Virtex-6 DMA Engine Reference Design]

= Licenses = 
 * [raw-attachment:KIT_PN2002_V6_x8_Gen2_1_00_11262013.zip​ North-West Logic DMA (x8, gen2) IP Core for Virtex-6] and [raw-attachment:core_licenses_full.zip​ the license]