1. FC Video Controller Performed by: Kapshitz Tsachy Grinkrug Michael Instructor: Alex Gurevich Cooperated with: Elbit Systems Ltd. Technion - Israel institute of technology, department of Electrical Engineering High speed digital systems laboratory

2. Abstract zInput: yFiber Channel Frames that include Audio- Visual containers yController Configuration z Output: yVideo objects in resolution of pixels (pixel per clock) yAncillary objects in resolution of DWords (except the last one) yStatus

3. Top level block diagram

4. Input Unit z Combines input words into Dwords z comma signal is passed together with the comma DWord z Generates clk_low clock: clk_low = rclk/2

5. Frame Controller z Parses Frame Headers z Passes through only legal frames: xSOF xDID xRCTL xTYPE xSEQ xEOF zCRC is calculated by an external unit and the result is compared

6. Container Controller z Parses Container Header xType xIndex xSize z Extracts ancillary and video objects z Outputs the data through separate interfaces

7. FIFO size calculation zFS - video Frame Size (in pixels) zF1 - Fibre Channel frequency zF2 - Aligner frequency (in pixels) zSZ1 - FIFO size in case of 1 byte per pixel resolution zSZ3 - FIFO size in case of 3 byte per pixel resolution zSZ - FIFO size in general case = MAX(SZ1, SZ3) z SZ1 = z SZ3 = z The typical video frame rate is 30 fps => overall byte throughput is: 30xFS 14.5 MHz z Thus, synthesizing for clk_high higher than this value and choosing a sufficient FIFO size, the Controller will manage to process the protocol.

8. Example zLet's take some typical values: yFS = 910 x 525 = 477750 480KB yF1 = 53 MHz yF2 = 25 MHz zSZ = MAX(365074, 419159) = 419159 ~ 420KB z For Apex20KE-1X: yFS = 480KB yF1 = 53 MHz yF2 = 41 MHz z SZ ~ 290KB

9. FIFO size vs. clk_high frequency

10. ‘Real life’ solution zIn order to implement the above using the conventional FPGA’s, external FIFO can be used y5 parallel 9x128KB y2 pipelined 80x64KB zManufactures: yCypress yIDT FC - below FIFO FC - above FIFO External FIFO

11. Testing Process 1 2 333 4 4 0

12. SW zAV containers are generated using a SW program, randomizing size and other parameters zThe containers are divided into FC frames, randomizing their size and adding frame headers zExpected output files are generated for ancillary and video data separately zThis methodology enabled sufficient test case coverage