Filter
Top Products
468 AMD Geode™ LX Processors Data Book
Video Input Port
33234H
Figure 6-41. 525 line, 60 Hz Digital Vertical Timing
Line 1 (V = 1)
Line 20(V = 0)
Line 264 (V = 1)
Line 283 (V = 0)
Line 525 (V = 0)
Blanking
Field 1
Active Video
Blanking
Field 2
Active Video
Line 4
Line 266
Line 3
Field 1
(F = 0)
Odd
Field 2
(F = 1)
Even
H = 1
EAV
H = 0
SAV
Line
Number F V
H
(EAV)
H
(SAV)
1-3 1 1 1 0
4-19 0 1 1 0
20-263 0 0 1 0
264-265 0 1 1 0
266-282 1 1 1 0
283-525 1 0 1 0
(VBI Data)
(VBI Data)
In VIP 1.1 mode, the T,F,V video flags are only captured from the EAV code. In VIP 2.X modes, these flags are captured from
both the SAV and the EAV codes. (The H bit is always captured to distinguish between and SAV and EAV code). Note that for VIP
1.1 mode, there must be a minimum of one SAV/EAV scan line during vertical blanking in order for the VBlank flag to transition
from 0->1->0.
An End-of-Frame event is detected the same in VIP 1.1 and VIP 2.0 modes. (A 0->1 transition of VBlank when F = 1 causes an
End-of-Frame event during interlaced video, A 0->1 transition of V-Blank causes an End-of-Frame event during progressive scan
video) An End-of-Frame event is used for starting/stopping capture and for updating buffer addresses. Line #1 of a frame does not
necessarily coincide with the End-of-Frame event. Line #1 is specified differently with respect to VBlank depending on the frame
type (resolution/interlaced/...). When line#1 is defined other then on the falling transition of VBlank, VBI data received after the V-
Blank transition will be stored in updated buffer address. VBI data is generally not sent during this time.